Installing external Remedy SSO using the wizard
Where you are in the installation process
Step | Task |
---|---|
1. | Preparing for TrueSight Orchestration installation |
2. | Install Remedy SSO (external) (You are here) |
3. | Install the repository |
4. | Install the Configuration Distribution Peer |
5. | Install TrueSight Orchestration Development Studio |
6. | Install TrueSight Orchestration Content |
7. | Install additional peers – Activity Peer |
Install additional peers – Lightweight Activity Peer | |
Install additional peers – High Availability CDP | |
8. | Install the Operator Control Panel |
9. | Install the Health and Value Dashboards |
10. | Complete post-installation configuration tasks |
By default, when you install TrueSight Orchestration components such as the repository, CDP, and so on, embedded Remedy SSO is installed with the component. You can choose to use the embedded Remedy SSO of the repository as an external Remedy SSO while installing the CDP and the the rest of the components. You can also choose to install external Remedy SSO. In this scenario, you must install external Remedy SSO before installing any other components.
To install Remedy SSO
- Unzip the Remedy SSO installation zip folder.
Run the installation program based on your operating system.
- For Microsoft Windows, run setup.exe.
- For Linux, run sh setup.sh.
- In the lower-right corner of the Welcome panel, click Next.
- Review the license agreement, click I agree to the terms of license agreement, and then click Next.
- Accept the default destination directory or browse to select a different directory, and then click Next.
- Select BMC Remedy Single Sign-On <version number>, and then click Next.
- Browse to select the Apache Tomcat directory path where Remedy SSO application will be deployed.
Enter the database settings.
Note
To use Remedy SSO with Platform, choose embedded database or external database (Oracle or MS SQL Server).
Remedy Single Sign-On versions 9.1.01.001 and 9.1.02.001 only support high availability with an embedded database.
Stand-alone Remedy SSO versions 9.1.01.001 and 9.1.02.001 installations do not support HA with embedded DB.
Assign a database user. The details of the user will be used by Remedy SSO to access the details of application configuration and user sessions. You may choose to provide the credentials for an existing database user with permissions to create tables or create a new user.
- Enter a cookie domain, and then click Next.
The domain value of the cookie must be the network domain of Remedy SSO or one of its parent domains. - In the Installation Preview window, click Install.
Log in with default credentials.
- After you log in for the first time, change the password.
To create users, roles, and realm in Remedy SSO
After you have successfully installed Remedy SSO, perform the following post-installation tasks:
- Create a realm.
You require the realm name while installing the repository later.
For more information, see Working with realms. - Create a user in the realm with aoadmin as the username.
You require the username and password while installing the repository later. - Create a role called AoAdmin.
Role name is case-sensitive. Assign the aoadmin user to the AoAdmin role.
For more information, see Creating and managing local users and roles in Remedy Single Sign-On.
Next step in the installation process
To begin with installing Platform components, see Installing the repository using the wizard. To explore more Remedy SSO options for your environment, see Installing Remedy SSO in Remedy SSO documentation.
Comments
This section says RSSO with platform supports only - "choose embedded database or Oracle database." I thought RSSO supported SQL Server as well. is this a documentation Error.
Also if the AO platform is installed with Embedded RSSO, is there a documentation to detail the steps to repoint all AO components (CDP, HACDP, Repo) to External RSSO.
RSSO is indeed supported on External MS SQL Server. As far as converting to External, there should be documentation for migrating an existing Embedded RSSO implementation to an External RSSO implementation. You will need to install and configure an Apache Tomcat server as well as a Java Development Kit or Java Runtime Environment. Refer to the supported versions in the documentation.
Refer to TSO 8.2.0 Enhancements for supported versions of RSSO and Java: https://docs.bmc.com/docs/TrueSightOrchestration/82/8-2-00-enhancements-821041332.html
Support for Java: https://docs.bmc.com/docs/TrueSightOrchestration/82/support-for-java-858716783.html
Changing to an External Remedy Single Sign On implementation: https://docs.bmc.com/docs/TrueSightOrchestration/82/changing-to-an-external-remedy-single-sign-on-instance-after-installation-821041532.html
Hi Guru,
Let me check and get back to you.
Thanks for your comment.
Updated the doc. Thanks!
Log in or register to comment.