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.

Note

If you have Remedy SSO agents upgraded to 19.11, you must upgrade the Remedy SSO server to a version later than 18.08.

When you upgrade Remedy SSO integration with BMC TrueSight Presentation Server to version 19.11 on an embedded PostgresSQL database, an error is thrown. For information about the workaround for this issue, see Troubleshooting installation and upgrade issues.

Related topics

Installing

Upgrade process overview

Upgrading Remedy SSO involves the followings tasks:

Upgrade the Remedy SSO server.
Upgrade Remedy SSO with integrated products.

Upgrading the Remedy SSO server

You can upgrade the Remedy SSO server in standalone mode or in 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. Some of the configuration files are kept to prevent custom changes from being overwritten.

To upgrade the Remedy SSO server

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

Upgrade method	Reference
To upgrade Remedy SSO by using the installation wizard	Installing Remedy SSO by using the installation wizard
To upgrade Remedy SSO silently	Installing Remedy SSO by using the silent mode

To upgrade the Remedy SSO server in high availability mode

To upgrade Remedy SSO in high availability mode, perform one of the following tasks based on whether or not you plan to shut down the system for the upgrade:

Upgrade option

Upgrade 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

Remove a server node from the Remedy SSO HA cluster.
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.
Return the server node back to the HA cluster.
Repeat steps 1 to 3 for the remaining nodes in the HA cluster.

Upgrading Remedy SSO with integrated applications

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

The web container (Tomcat server) in which 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.