Unsupported content This version of the product is in limited support. However, the documentation is available for your convenience. You will not be able to leave comments.

Upgrading

The topic provides information and instructions for upgrading Remedy Single Sign-On from an earlier version.

Best practices for upgrading Remedy SSO

Consider the following best practices for upgrading Remedy SSO.

  • BMC recommends that you export the existing configurations prior to an upgrade or prior to making significant changes. If Remedy SSO upgrade is rolled back, the old configurations can be re-applied.
  • Upgrade in this sequence:
    1. Upgrade the Remedy SSO servers.
    2. Upgrade the Remedy SSO integration with Remedy AR System, Remedy MidTier, BMC MyIT or SmartIT, and BMC Analytics.
  • Keep Remedy SSO servers and integrations at the same version.
  • 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.

Post upgrade configurations

  • If your system had realms configured for SAML authentication, you must reconfigure the SAML authentication settings after the upgrade. For more information on reconfiguring the SAML authentication settings, see Configuring SAML authentication settings after you upgrade.
  • If you had modified the web.xml, then ensure that after the upgrade you reapply the changes.
  • Configure new Remedy SSO logger by using rsso-log.cfg file or the corresponding java options.

Remedy SSO upgrade overview

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 kept 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 with the database updated to the current version until you upgrade the rest of the cluster servers.

Remedy AR System, BMC Remedy MidTier

  • Remedy SSO server binaries (<Tomcat>\webapps\rsso\) and the database schema are upgraded.
  • Configuration files are kept or updated.

Before you begin

If you have not already done so, review the System requirements.

To upgrade Remedy SSO

Perform the steps given in this section to upgrade Remedy SSO.

Note

The web container (Tomcat server) in which Remedy SSO server integrations are running will be restarted during an upgrade of Tomcat. 

  1. Run the installation program based on your operating system.
    • For Microsoft Windows, run setup.exe.
    • For Linux, run sh setup.sh.
  2. In the lower-right corner of the Welcome panel, click Next.
  3. Review the license agreement, click I agree to the terms of license agreement, and then click Next.
  4. Select the Upgrade BMC Remedy SSO <version1> to <version2> option, and then click Next.
  5. In the Installation Preview window, click Install.
  6. In the Installation Summary window, click Done.

Configuring SAML authentication settings after you upgrade

Based on whether or not you plan to shut down for the upgrade, proceed as follows:

For planned downtime

    • ===
  1. Upgrade all Remedy SSO server nodes to the required version.
  2. Log in to Remedy SSO Admin Console.
  3. For each realm that is configured for SAML authentication, perform the following steps:
    1. 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.
    2. Save the details.

For no planned downtime

  1. Remove a Remedy SSO server node from the cluster.
  2. Upgrade the removed server node to the required version.
  3. Log in to the Admin console of Remedy SSO after the upgrade is complete.
  4. For each realm that is configured for SAML authentication, perform the following steps:
    1. 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.
    2. Save the details.
  5. Bring the server node back to the cluster.

Repeat Steps 1 to 5 for the remaining nodes in the cluster.

Upgrading Remedy SSO using the silent mode

A silent upgrade is used to upgrade Remedy SSO in multiple systems. You need to generate an options file containing the following details to perform a silent upgrade.

To upgrade Remedy SSO servers

-P installLocation=<path where product info will be located> example: C:\SSO\RemedySSO
-A productRemedySSO
-J INSTALL_TYPE=true
-J DB_TYPE=<MS SQL | Oracle>

To upgrade Remedy SSO integrations

-A featureRemedySSO
-P installLocation=<path_to_rsso_app>