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

Where you are in the Installation process

To install Remedy SSO using the silent 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.

You need to perform the following tasks to install Remedy SSO in a high-availability mode:

Step B: Install Remedy SSO on the secondary computer

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. You will need to type the database administrator and database user passwords in an encrypted form in the tsso_silent.options file in Step 5. You can encrypt these passwords using the TrueSightRSSOMaintenanceTool through the wizard or command line interface:

     Encrypt password using the wizard

   1. Open the TrueSightRSSOMaintenanceTool by navigating to:
      • (Windows) <DownloadLocation>\RSSO\Windows\Disk1\Utility
      • (Linux) <DownloadLocation>/RSSO/Linux/Disk1/Utility 
   2. Run the tool, and click the Encrypt tab.
   3. Type the password, confirm it, and click Encrypt.
   4. Note down the encrypted password (from the Encrypted Password field).
     Encrypt password using the command line interface

   1. Navigate to the following directory:
      • (Windows) <DownloadLocation>\RSSO\Windows\Disk1\Utility
      • (Linux) <DownloadLocation>/RSSO/Linux/Disk1/Utility 

   2. Run the following command:

      • (Windows)

        TrueSightRSSOMaintenanceTool.cmd -silent -encrypt -encrypt -password=<password> -confirm_password=<password>

      • (Linux)

        ./TrueSightRSSOMaintenanceTool.sh -silent -encrypt -encrypt -password=<password> -confirm_password=<password>

        Note

        (Linux) If the password contains special characters, enclose the password using single quotes as shown in the following example:

        ./TrueSightRSSOMaintenanceTool.sh -silent -encrypt -encrypt -password='<password>' -confirm_password='<password>'

   3. Note down the encrypted password.

4. In the extracted folder, locate the tsso_silent.options file:

   • (Windows)<DownloadLocation>\RSSO\Windows\Disk1\

   • (Linux) <DownloadLocation>/RSSO/Linux/Disk1/

5. Open and edit the tsso_silent.options file. You can either retain the default values for the properties or change them, and save the file. The tsso_silent.options is a text file that defines the installation properties in the form of a prefix tag followed by a property name and value pair.

     Property details

   Prefix tags for the silent installation properties:

   • -P: Precedes the directory properties

   • -A: Precedes the application features

   • -J: Precedes the Java properties

   Property name	Description
   Installation location
   -P installLocation	You can retain the following default installation directory path or type a new path: (Windows)C:\Program Files\BMC Software\TrueSightRSSO (Linux) /opt/bmc/TrueSightRSSO Examples:  (Windows) -P installLocation=C:\Program Files\BMC Software\TrueSight\TrueSightRSSO (Linux) -P installLocation=/opt/bmc/TrueSightRSSO
   Installing features
   -A <feature name>	Retain the default feature value.  Default value: featureTrueSightRSSO Example:-A featureTrueSightRSSO
   Database settings
   -J PG_TYPE	Type 1 to indicate that you want to use an existing (or external) PostgreSQL database instance. Example: -J PG_TYPE=1
   Type the database settings of the PostgreSQL database that you used while installing Remedy SSO on the primary node.
   -J DB_HOST	Type the name of the host computer running the PostgreSQL database instance that you plan to use. Example:-J DB_HOST=hostdb.bmc.com
   -J DB_PORT	Type the port number used while installing the existing PostgreSQL database. Example:-J DB_PORT=5438
   -J DB_POSTGRES_DBNAME	Type the name of the existing PostgreSQL database instance that you plan to use. Ensure that the PostgreSQL instance that you plan to use is not shared by the Presentation Server. Example:-J DB_POSTGRES_DBNAME=rssodb
   -J DB_IS_USER_EXIST	Type true to indicate that you want to create a new database user to manage the PostgreSQL database operations. Example:-J DB_IS_USER_EXIST=true
   -J DB_ADMIN	This property value is ignored, as you have set the DB_IS_USER_EXIST value to true to indicate that you want to use an existing user. Default value: postgres
   -J DB_ADMIN_PWD	This property value is ignored, as you have set the DB_IS_USER_EXIST value to true to indicate that you want to use an existing user.
   -J DB_ADMIN_PWD_CNFRM	This property value is ignored, as you have set the DB_IS_USER_EXIST value to true to indicate that you want to use an existing user.
   -J DB_USER	Type the name of the existing database user that you plan to use. Default value: rsso_user Example: -J DB_USER=rsso_user Note: This input is automatically stored in lowercase.
   -J DB_USER_PWD	Type the encrypted database user password that you created in Step 3. Example: -J DB_USER_PWD=DES\:4e14ab9b35c5dffa9d7d64484b0c78fd
   DB_USER_PWD_CNFRM	This property value is ignored, as you have set the DB_IS_USER_EXIST value to true to indicate that you want to use an existing user.
   Tomcat configuration
   TOMCAT_HTTP	Type the HTTP port that you want to use to communicate with Remedy SSO. Default values: (Windows) 88 (Linux) 8088 Example:-J TOMCAT_HTTP_PORT=88
   TOMCAT_HTTPS	Type the HTTPS port that you want to use to communicate with Remedy SSO. By default, the installer configures Remedy Single Sign-On in HTTPS. If you want to use the HTTP, you can manually configure it anytime as a post-installation activity. Default values: (Windows) 448 (Linux) 8048 Example:-J TOMCAT_HTTPS_PORT=448
   Cookie domain
   -J COOKIE_DOMAIN	Type the cookie domain that you want to use to access Remedy SSO. It must be same as the network domain of 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 would be bmc.com Default value: bmc.com Example:-J COOKIE_DOMAIN=bmc.com
   -J SERVER_FQDN	Type the fully qualified domain name of the server on which you plan to install Remedy SSO. Example: -J SERVER_FQDN=host1.bmc.com

6. From the command prompt, run the following command to start the installation. Type the complete path to the tsso_silent.options file in the command. If the path includes a blank space, enclose the path within double quotes. However, installation occurs in the background.

   A local installation may take up to 15 minutes.
   Syntax:

   • (Windows)setup.exe -i silent -DOPTIONS_FILE="<path_to_tsso_silent.options_file>"
   • (Linux) ./setup.bin -i silent -DOPTIONS_FILE="<path_to_tsso_silent.options_file>"

   Examples:

   • (Windows - Path without space) setup.exe -i silent -DOPTIONS_FILE=C:\Disk1\tsso_silent.options
   • (Windows - Path with space) setup.exe -i silent -DOPTIONS_FILE="C:\temp folder\Disk1\tsso_silent.options"

   • (Linux - Path without space)./setup.bin -i silent -DOPTIONS_FILE=/opt/Disk1/tsso_silent.options
   • (Linux - Path with space)./setup.bin -i silent -DOPTIONS_FILE="/opt/temp folder/Disk1/tsso_silent.options"

7. You can periodically check the installation status by checking the truesightrsso_install_log.txt file located at: 

   • (Windows)%temp%

   • (Linux)  /tmp

8. Search for the following log message in the truesightrsso_install_log.txt file to ensure that Remedy SSO is installed successfully:
   Remedy Single Sign-On 18.02.00 for TrueSight 11.3.01 install succeeded.

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

   • (Windows) %TRUESIGHTRSSO_HOME%

   • (Linux) $TRUESIGHTRSSO_HOME

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

    • To define 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]}

11. Launch the Remedy SSO URL in a browser and log in to the Remedy SSO console using the default Admin credentials:

    • User name: Admin

    • Password: RSSO#Admin#

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

13. 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.

14. (Linux) Configure the Remedy SSO service to restart automatically each time the Remedy SSO server is restarted:
    1. Log in to the host computer as a root user.

    2. From the command line, go to <installationDirectory>/rsso/bin, and run the following command:
       ./rsso service register <nonRootUserName>

       <nonRootUserName> refers to the name of the non-root user that you used for installing Remedy SSO.

    Your installation is complete.

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.