Unsupported content


This version of the product is in limited support. However, the documentation is available for your convenience. You will not be able to leave comments.

Performing the upgrade

You can directly upgrade to the latest version of Remedy Single Sign-On from any prior version. Follow the instructions in this topic to upgrade Remedy SSO to a required version.

Before you begin

Perform all the tasks to prepare for upgrade of Remedy Single Sign-On.


When you upgrade Remedy SSO with BMC TrueSight Presentation Server to version 19.02 on an embedded PostgresSQL database, the upgrade fails with an exception. For more information about the workaround, see Known and corrected issues.

Related topics

Upgrade process overview

You upgrade Remedy Single Sign-On by performing the followings steps:

  1. Upgrade Remedy SSO server
  2. Upgrade Remedy SSO with integrated products.

Upgrading Remedy SSO server

You upgrade Remedy SSO server in a standalone mode or in a high availability mode in the same way as you install Remedy SSO. When you upgrade the Remedy SSO server, the server binaries (<Tomcat>\webapps\rsso\) and the database schema are upgraded. Configuration files are kept or updated.

To upgrade Remedy SSO server

You upgrade Remedy SSO server by using one of the following methods:

Upgrade methodReference
To upgrade RSSO by using the installation wizardInstalling Remedy SSO by using the installation wizard
To upgrade RSSO silentlyInstalling Remedy SSO by using the silent mode

To upgrade Remedy SSO server in high availability mode

If you are upgrading Remedy Single Sign-On in a high availability mode, based on whether or not you plan to shut down the system for the upgrade, perform the upgrade tasks:

Upgrade optionUpgrade tasks
To upgrade Remedy SSO in high availability mode with planned downtime 

Individually upgrade all Remedy SSO server nodes to the required version.

To upgrade Remedy SSO in high availability mode with unplanned downtime
  1. Remove a server node from the RSSO HA cluster.
  2. Upgrade the removed server node to the required version.
    After you upgrade the first node, the underlying database is upgraded as well. The rest of the nodes remain unupgraded and work with the database updated to the current version, until you upgrade the rest of the nodes.
  3. Return the server node back to the HA cluster.

  4. Repeat steps 1 to 3 for the remaining nodes in the HA cluster.

Upgrading Remedy SSO with integrated applications

You upgrade Remedy SSO with integrated applications the same way you install them. For details about how to upgrade Remedy SSO with integrated applications, review the required installation procedure:

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

Where to go from here

When you have completed the upgrade tasks, configure Remedy SSO server after upgrade.

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