Upgrading Remedy SSO in the high-availability mode using the TrueSight installer silently
Where you are in the Upgrade process
|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|
If you have implemented Remedy Single Sign-On in a high-availability (HA) environment as a redundant system with session failover. You must upgrade both the Primary and Secondary nodes.
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:
- If you do not want to plan for the system downtime, do the following:
To upgrade Remedy SSO in a HA environment silently
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.
Upgrade Remedy SSO on the primary node by performing the upgrade silently.
In the options file, the database type specified must be PostgreSQL External. Also, while configuring user accounts for managing PostgreSQL database operations, you need to create a new user.
Upgrade Remedy SSO on the additional node by performing the upgrade silently.
In the options file, the database settings must be the same as the settings used by the primary node. Also, while configuring user accounts for managing PostgreSQL database operations, you need to specify an existing user (Use Existing User option on the installer) and provide details of the user created on the primary node.
To reconfigure the SAML authentication settings
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.
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.