Upgrading Remedy SSO in the standalone mode using the TrueSight installer silently

Where you are in the Upgrade process

StepTask
1Preparing to upgrade TrueSight Operations Management solution
2Upgrade Remedy Single Sign-On (You are here)
3Upgrade TrueSight Presentation Server
4Upgrade TrueSight Infrastructure Management
5Upgrade App Visibility Manager
6Upgrade Real End User Experience Monitoring Software Edition
7Upgrade TrueSight IT Data Analytics

Use this topic to upgrade Remedy SSO to the current version using the silent TrueSight installer. The TrueSight installer for Remedy SSO automatically creates a backup directory during the upgrade process. You can locate the backup files and folders at <TrueSightRSSO_Install_dir>\TrueSightRSSO11.0.00.

To upgrade Remedy SSO using the TrueSight installer silently

Do the following:

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

    • (Windows) %temp%
    • (Linux/tmp

  2. Extract the zipped files (the installer) that you downloaded in Step 2:Prepare for TrueSight Operations Management upgrade to a temporary location outside the following directory location to avoid any file sharing conflicts:

    • (Windows)C:\Program Files

    • (Linux) /opt

  3. Ensure that the Remedy SSO service is up and running. For more information on starting Remedy SSO, see Starting and stopping the TrueSight Operations Management components.

  4. If you have changed the database password of the earlier version of Remedy SSO, do the following:

    1. Encrypt the updated password by using the TrueSightRSSOMainatenanceTool that is available in the <rsso_installer>/utility directory.
    2. If you have changed the database admin password, open the <RSSO_HOME_DIR>/TrueSightRSSOInstalledConfiguration.xml file, and update the password against the DB_ADMIN_PWD and DB_ADMIN_CNFRM properties.
    3. If you have changed the RSSO user password, do the following:

      • Open the <RSSO_HOME_DIR>/TrueSightRSSOInstalledConfiguration.xml file, and update the password against the DB_USER_PWD and DB_PWD_CONFRM properties.

      • Open the <RSSO_HOME_DIR>/ rsso/conf/rssoproperties.conf file, and update the encrypted password.

  5. From the command prompt, run the following command to start the upgrade.
    Syntax:

    • (Windows)setup.exe -i silent
    • (Linux./setup.bin -i silent

    The upgrade may take up to 15 minutes to complete.

  6. After the upgrade is complete, the Installation Summary page is displayed.You can periodically check the upgrade status by checking the truesightrsso_install_log.txt file located at: 

    • (Windows)%temp%
    • (Linux /tmp

  7. 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.
  8. Verify that the following environment variable points to the Remedy SSO installation path:

    • (Windows) %TRUESIGHTRSSO_HOME%

    • (Linux) $TRUESIGHTRSSO_HOME

  9. 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]}

  10. 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#

  11. (Optional) If you have changed the Remedy SSO to the HTTP mode before upgrade, edit the web.xml file.
    1. Navigate to the following directory:
      • (Windows): <installationDirectory>\rsso\tomcat\conf
      • (Linux): <installationDirectory>/rsso/tomcat/conf
    2. Edit the web.xml file, comment the following part, and save the file:

      The commented code lines:

      <!-- 
      <security-constraint>

           <web-resource-collection>

              <web-resource-name>Secure context</web-resource-name>

              <url-pattern>/*</url-pattern>

           </web-resource-collection>

           <user-data-constraint>

               <transport-guarantee>CONFIDENTIAL</transport-guarantee>

           </user-data-constraint>

      </security-constraint>

      -->

  12. (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.

  13. (Optional) If you have configured SAML authentication with your Remedy SSO enviornment, do the following:

     Reconfirgure the SAML authentication steps

    For each realm that is configured for SAML authentication, perform the following steps:

    1. Edit the realm to enter PEM encoded IdP signing certificate data in the IdP Signing Certificate field or import the IdP metadata again. Ensure that the other SAML configuration is same as before except the IdP Signing Certificate field data.
    2. Save the details.

    Important

    When you configure the SAML authentication parameters for the Presentation Server, you must set the User ID Transformation field to RemoveEmailDomain and enable the Force Authentication check box.

  14. Navigate to the <Remedy SSO Installation Directory>\rsso\bin directory, and restart the Remedy SSO server by running the following command:

    • (Windowsrsso.bat server start
    • (Linux) ./rsso server start

Troubleshooting upgrade failure

Do the following steps if the upgrade fails:

  1. Backup the ProductRegistry.xml file.
    • (Windows) C:\Windows\ProductRegistry.xml
    • (Linux) /opt/bmc/ProductRegistry.xml
  2. Navigate to the <TrueSightRSSO_install_dir> and delete the TrueSightRSSO folder.
  3. Rename the TruesightRSSO11.0.00 folder to TruesightRSSO.
  4. Restore the ProductRegistry.xml file.
  5. Start the BMC Remedy SSO service.
  6. Perform the upgrade procedure again.

Next step in the Upgrade process

Now that you have successfully upgraded Remedy SSO, you must proceed to Upgrading the Presentation Server

Was this page helpful? Yes No Submitting... Thank you

Comments