Preparing to upgrade Remedy Single Sign-On
This section describes how to upgrade Remedy Single Sign-On to the current version by using the interactive installation wizard or in silent (or unattended) mode.
Follow the Remedy SSO upgrade instructions in this section only if you plan to upgrade the Remedy SSO from the following versions to the current version:
- If you have installed and configured Remedy SSO for TrueSight 11.0 and want to upgrade to Remedy SSO for TrueSight 11.3.01.
- If you have installed and configured Remedy SSO 9.1.03.001 or later and want to upgrade to any supported Remedy SSO server version.
Skip the Remedy SSO upgrade instructions in this section if you plan to do one of the following scenarios:
- If you plan to configure an existing supported version of Remedy SSO server in your environment and do not plan to upgrade the Remedy SSO server.
- If you are new to the Presentation Server. For more information, see Remedy-Single-Sign-On-at-a-glance.
Review the following sections before you proceed to upgrade:
Best practice before upgrading Remedy SSO
- Export the existing configurations prior to upgrading or making significant changes. If Remedy SSO 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 SSO 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.
- If you are monitoring any BMC product by using the PATROL for Web URL or PATROL for Internet Servers KM, ensure that the value of the redirect-mode property is set to true in the rsso-agent.properties file after upgrade.
- Before you upgrade to Remedy SSO version 18.11 or later, ensure that you create a backup of the following:
- Only the ProductRegistry.xml file on Windows from C:\Windows\ProductRegistry.xml
- The entire{{code language="none"}}
/opt/bmc
{{/code}} folder in Linux. The ProductRegistry.xml file is part of the /opt/bmc folder in Linux. - The rsso-agent.properties file.
Database upgrade recommendation
Perform this mandatory step if you plan to upgrade the Remedy SSO in the following scenario:
Scenario
You have used the TrueSight installer for Remedy SSO version 11.3.01 to install Remedy SSO and want to upgrade to a later supported Remedy SSO version.
Recommendation
BMC recommends that after you upgrade the Remedy SSO, you must upgrade the database to a latest supported version. This is to ensure that you have all the latest security updates included in your environment. Contact your DBA to update it to a supported version of the Remedy SSO database. For more information on the supported versions, see System requirements for Remedy SSO 18.05 or to any of the latest supported versions as per your requirement.
Remedy SSO installer types for upgrading
You can deploy Remedy SSO in one of the following ways:
- By using the TrueSight installer for Remedy SSO - This is a consolidated installer that contains all the prerequisite software for Remedy SSO, and can be used for a unified install experience. This installer has the following limitations:
- Works only with PostgreSQL database.
- Can be used only if you are upgrading from the TrueSight Presentation Server version 10.7 or 11.0 to 11.3.01.
- By using the Remedy SSO installer - This contains only the Remedy SSO Server and doesn't contain any prerequisite software, such as JRE and Tomcat. It works with MS SQLServer, Oracle, and PostgreSQL databases.
Next step in the upgrade process
Based on the choice of the Remedy SSO installer type, proceed to one of the Remedy SSO topics to upgrade.