Upgrading Remedy SSO in the high-availability mode using the Remedy installer silently

Where you are in the Upgrade process

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

Remedy Single Sign-On high-availability (HA) environment is implemented as a redundant system with session failover. In this model, if a node fails, the single sign-on load is transitioned to the remaining servers with minimal interruption.

Remedy SSO upgrade process

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

Upgrade	What 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 or later) until you upgrade the rest of the cluster servers.

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:

If you plan for the system downtime, do the following:
1. Upgrade Remedy SSO.
2. Re-configure SAML authentication.
If you do not want to plan for the system downtime, do the following:
1. Remove a node from the Remedy SSO server cluster.
2. Upgrade Remedy SSO on that node.
3. Re-configure SAML authentication.
4. Add the node back to the Remedy SSO server cluster.
5. Repeat the steps 1 to 4 for all other nodes.

To upgrade Remedy SSO in a HA environment using the Remedy installer silently

Note

The Remedy SSO Admin UI requires sticky session/Session Persistence in an HA environment. Usually, this is accomplished by enabling sticky session/Session Persistence on the load balancer. Different load balancers have different configurations to enable a sticky session/Session Persistence. Refer to the specific load balancer documentation or ask the vendor for details about the configuration.

Note that when sticky session/Session Persistence is not enabled for the Remedy SSO Admin UI, the admin user behind the firewall can use a specific Remedy SSO server hostname to access admin UI instead of using the load balancer URL.

You need to perform the following tasks to upgrade Remedy SSO using the options file silently in the high-availability mode:

Ensure that Remedy SSO is upgraded successfully on the primary node as outlined in upgrading Remedy SSO silently.
Unzip the Remedy SSO files on the additional node.
Upgrade Remedy SSO on the additional node as outlined in upgrading Remedy SSO silently.
Complete the rest of the installation steps.
(Optional) Reconfigure the SAML authentication.

To configure the SAML authentication settings after you upgrade

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

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

Postupgrade tasks

If you had modified the web.xml file during the upgrade, ensure that you reapply the changes after the upgrade.

Next step in the Upgrade process

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