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

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

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.
  • The rest of the cluster servers still work as the earlier version (for example 9.1.03) with the database updated to the current version (for example 18.02) until you upgrade the rest of the cluster servers.

To upgrade Remedy SSO using the Remedy installer silently

A silent upgrade is used to upgrade Remedy Single Sign-On (Remedy SSO) in multiple systems. You need to generate an options file containing the following details to perform a silent upgrade.

To upgrade Remedy SSO servers

-P installLocation=<path where product info will be located> example: C:\SSO\RemedySSO
-A productRemedySSO
-J DB_TYPE=<MS SQL | Oracle>

To upgrade Remedy SSO integrations

-A featureRemedySSO
-P installLocation=<path_to_rsso_app>

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