Installing Remedy SSO in the high-availability mode using the TrueSight installer wizard

Where you are in the  Installation process

To install Remedy SSO using the wizard-based TrueSight installer in the high-availability mode

Remedy Single Sign-On high-availability environment is implemented as a redundant system with session failover. If the primary node fails, the load is transitioned to the secondary node with minimal interruption. 

In a high-availability (HA) environment, multiple instances of the Remedy Single Sign-On (Remedy SSO) web application are deployed to form a cluster. Usually, a load balancer is used as a front end to the cluster, giving the external applications the appearance of a single server. The load balancer distributes requests among Remedy SSO nodes. However, there is no requirement for a sticky session, because requests can be handled by any instance.

Step B: Install Remedy SSO on the secondary computer

Do the following:

1. Log in to the host computer on which you want to install Remedy SSO, and delete all the files from the temporary directory:

   • (Windows) %temp%

   • (Linux) /tmp
     

   .

2. Extract the downloaded zip files (the installer) to a temporary location outside the following location to avoid any file sharing conflicts:

   • (Windows)C:\Program Files

   • (Linux) /opt

   .

3. Run the installer:

   • (Windows) As an administrator or as a non-administrator user, run setup.exe from Windows\Disk1

   • (Linux) As a non-root user, run ./setup.bin from Linux/Disk1

   .
4. (Linux) Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately:
   export DISPLAY=<IP address of the host computer>:0.0.
5. Review the welcome page, and click Next..
6. Read the license agreement, agree to the terms, and click Next..

7. Review disk space requirements. If required, you can change the default installation directory, and click Next:

   • (Windows) C:\Program Files\BMC Software\TrueSightRSSO

   • (Linux) /opt/bmc/TrueSightRSSO

   .

8. Select PostgreSQL - External database type to use an existing PostgreSQL database instance. 

   • Ensure that the PostgreSQL database is installed on a separate host computer that is different from the host computers on which you plan to install the primary and secondary Remedy SSO servers.
   • Primary and secondary Remedy SSO servers must be able to access the host computer on which the PostgreSQL database is installed.

   
   

9. Type the database details such as host name, database name, and port number of the existing PostgreSQL database that you used while installing on the primary node, and click Next. 

10. Select Use Existing User to use an existing database user to manage Remedy SSO operations. 
11. Type the database user name and password that you created while installing Remedy SSO on the primary node, and click Next.
    

12. Type the Tomcat port details that you want to use to communicate with Remedy SSO. You can retain the following default port values or type new values. Click Next:

    • (Windows)  HTTP: 88 and HTTPS: 448
    • (Linux)  HTTP: 8088 and HTTPS: 8048

    By default, the installer configures Remedy Single Sign-On in HTTPS. If you want to use HTTP, you must manually configure it anytime as a post-installation activity .
    

    .

13. Configure the cookie domain and Server FQDN details, and click Next.

    This is the cookie domain that you want to use to access Remedy SSO. It must be same as the network domain of host computer on which you are installing Remedy SSO or one of its parent domains. For example: If the host computer on which you want to install Remedy SSO belongs to apps.bmc.com, then your cookie domain must be bmc.com.

    

    .
14. Preview the details, and verify the configurations..
15. Click Install to start the installation. A local installation may take up to 15 minutes.
    After the installation is complete, the Installation Summary page is displayed..
16. Click View log to view the installation log details on the screen. From the log view, you can expand and view the log messages..
17. Click Done to exit the installation program..

18. Verify that the following environment variable points to the Remedy SSO installation path:

    • (Windows) %TRUESIGHTRSSO_HOME%

    • (Linux) $TRUESIGHTRSSO_HOME

    .

19. You can either construct the Remedy SSO URL or locate the URL in the log file:

    • To construct the URL, use the format: http(s)://<rsso_servername_FQDN>:<tomcat_port>/rsso
    • To locate the URL:
      1. Open the truesightrsso_install_log.txt log file from:
         
         • (Windows)<installationDirectory>\rsso\logs\

         • (Linux) <installationDirectory>/rsso/logs

      2. Search for the LOG EVENT that has the product URL as shown in the following example:

         • (Windows) LOG EVENT {Description=[PRODUCT URL],Detail=[product url: https://HostA.bmc.com:448/rsso]}

         • (Linux) LOG EVENT {Description=[PRODUCT URL],Detail=[product url: https://HostA.bmc.com:8048/rsso]}

    .

20. Launch the Remedy SSO URL in a browser, and log in to the Remedy SSO console. The user name and password are case sensitive. Use the following default Admin credentials:

    • User name: Admin

    • Password: RSSO#Admin#

    .
21. Change the password for the Admin user. Click Admin > Change Password..

22. Log out of the Remedy SSO console, and log in with the new Admin credentials.

    Your installation is complete if you are a Windows user.

    .

Step C: Set up and configure the load balancer details

Set up the load balancer on a host computer other than the primary and secondary Remedy SSO host computers. Refer to the specific load balancer documentation or ask the vendor for details about the configuration.

Troubleshooting installation issues

If you face issues during installation, see Troubleshooting the Remedy Single Sign-On server deployment.

Next step in the Installation process

Step 3 Phase B — Now that you have successfully installed Remedy SSO, you must set up the Remedy SSO server.