Upgrading Remedy SSO in the standalone mode using the Remedy installer wizard

Where you are in the Upgrade process

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

The topic provides information and instructions for upgrading Remedy Single Sign-On (Remedy SSO) from an earlier version using the Remedy installer wizard.

Remedy SSO upgrade process

The following table describes in detail the Remedy SSO upgrade process.

UpgradeWhat occurs during the upgrade
Remedy SSO application
  • Remedy SSO server binaries (<Tomcat>\webapps\rsso\) and database schema are upgraded.
  • Configuration files are unchanged or updated.
HA environment with Remedy SSO
  • After you upgrade the first node, the underlying database is upgraded as well.
  • Until you upgrade all of the cluster server nodes, those nodes would continue to work as the earlier version with the underlying database updated to the current version.

Planning to upgrade to Remedy SSO version 18.11 or later

If you have installed and configured TrueSight installer for Remedy SSO (consolidated installer) version 11.0 or 11.3.01, upgrading the Remedy SSO to 18.11 or later fails with upgrade exceptions. Do the following to avoid this issue:

  1. Log in to your existing Remedy SSO server and navigate to the <RemedySSO_INSTALL_DIR>/rsso/conf directory.
  2. Open the rssoproperties.conf file.
  3. Set the db.prepackage.type property to false.
  4. Upgrade the Remedy SSO to version 18.11 or later.
  5. After a successful upgrade, reset the db.prepackage.type property to true.

Plan for system downtime before upgrading Remedy SSO

If you are using SAML authentication in your Remedy SSO environment, before you upgrade, decide whether you want to plan for the system downtime or not. Based on your plan, choose between these two options: 

To upgrade Remedy SSO using the wizard-based Remedy installer


The web container (Tomcat server) in which BMC Remedy SSO server integrations are running will be restarted during an upgrade of Tomcat. 

  1. Run the installation program based on your operating system.

    • For Microsoft Windows, run setup.exe.
    • For Linux, run sh setup.sh.
  2. In the lower-right corner of the Welcome panel, click Next.
  3. Review the license agreement, click I agree to the terms of license agreement, and then click Next.
  4. Select the Upgrade BMC Remedy SSO <version1> to <version2> option, and then click Next.
  5. In the Installation Preview window, click Install.
  6. In the Installation Summary window, click Done.

Postupgrade tasks 

Do the following:

  1. If you had modified the web.xml file during the upgrade, ensure that you reapply the changes after the upgrade.
  2. If you have upgraded from TrueSight Remedy SSO to Remedy SSO version 18.11 or later, open the <RemedySSO_INSTALL_DIR>/rsso/conf/rssoproperties.conf file and reset the db.prepackage.type property to true.
  3. (Optional) If you have configured your Remedy SSO with SAML authentication, reconfigure using these steps:

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


    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.

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