Preparing to upgrade Remedy Single Sign-On

Follow the Remedy Single Sign-On Server upgrade instructions in this section only if you plan to upgrade the Remedy Single Sign-On Server from the following versions to the current version:

• If you have installed and configured Remedy Single Sign-On Server for TrueSight 11.0 and want to upgrade to Remedy Single Sign-On Server for TrueSight 11.3.01.
• If you have installed and configured Remedy Single Sign-On Server 9.1.03.001 and want to upgrade to Remedy Single Sign-On Server 18.02.
  
  

Skip the Remedy Single Sign-On Server upgrade instructions if you plan to do one of the following scenarios:

• If you plan to install, upgrade, and configure any other supported versions (9.1.04) of Remedy Single Sign-On Server, see Installing Remedy SSO 9.1.04.

• If you are upgrading your Presentation Server from a version earlier than 11.0 to the current version. For more information, see Remedy-Single-Sign-On-at-a-glance.
• If you are upgrading TrueSight Capacity Optimization from 11.3.01 to 11.5.

Best practice before upgrading Remedy Single Sign-On Server

• Export the existing configurations prior to upgrading or making significant changes. If Remedy Single Sign-On Server upgrade is rolled back, the old configurations can be re-applied.
• Make a copy of the web.xml file before you start the upgrade.
• To prevent down time in a high-availability environment, perform a rolling upgrade of all Remedy Single Sign-On Servers and integrations. Temporarily exclude the node that is being upgraded from load balancing, upgrade it, make sure it is functioning, and then include it back to balancing.

Where to go from here

Perform the other pre-upgrade tasks listed in Preparing-to-upgrade-TrueSight-Capacity-Optimization.