Upgrading

The upgrade methods are similar to the methods for installing a new product. You run the installation program from a graphical user interface (GUI) or from a command line. This section provides an overview of the upgrade process and the procedures for performing platform upgrades with the GUI and command-line options. 

Best practices

Before upgrading any of the platform components, BMC recommends that you stop services for all platform components and not just the one that you want to upgrade. After the upgrade, you can restart the services. For more information, see Starting-and-stopping-product-components-and-services.

Related topics

Troubleshooting-the-installation

Supported upgrade paths

The following figure shows the supported upgrade path for TrueSight Orchestration Platform. Ensure that you are upgrading from one of the versions shown in the figure.

If you want to upgrade to version 22.2.x from a version earlier than 8.2, first upgrade to 8.2, and then upgrade to 22.2.x.  

Warning
  • Do not change the authentication system type while upgrading.
  • You must use the same authentication system (embedded or external) as used in your current platform environment. If your current platform environment uses embedded Remedy Single Sign-On (Remedy SSO), do not switch to an external Remedy SSO or from an external to embedded Remedy SSO.

TSOP 22.2.01 upgrade paths.gif


Important

  • BMC Remedy Single Sign-On (external and embedded) is used as the authentication system.
  • If you want to use an external Remedy SSO, you must first install or upgrade to a supported version before upgrading the TrueSight Orchestration Platform. For more information, see System-requirements.
  • If your current platform environment uses embedded Remedy SSO, when you upgrade to 22.02, the embedded Remedy SSO version is upgraded to 20.02.



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*