Preparing for upgrades from 7.8.x and 7.9 with ASSO to 8.2 with RSSO


This section describes how to prepare for an upgrade of the 

Some content is unavailable due to permissions.

Platform product: 

Note

BMC Atrium Single Sign-On is not supported for use with

Some content is unavailable due to permissions.

Platform 7.9.01 and later versions.

Before upgrading

  • Review supported upgrade paths in Upgrading.
  • Make copies of server.xml and broker-config.xml files before upgrading. For more information, see Backing-up-server-xml-and-broker-config-xml-files.
  • If you are upgrading 

    Some content is unavailable due to permissions.

    components on a Linux computer, run the rngd service to ensure that the system has adequate entropy. 

    Click here to see the steps

    Before installing or upgrading TrueSight Orchestration components on a Linux computer, run the rngd service to ensure that the system has adequate entropy.

    1. Verify that rng-tools is installed on your Linux computer. If it is not, install it, working with your system administrator to ensure that you correctly install the rng-tools for your operating system.
    2. At the command line, run the following command:
      rngd -r /dev/urandom

    After installing TrueSight Orchestration, ensure that this command is running at server startup or before starting the TrueSight Orchestration service.

    For more information, see Workaround when a component server startup on Linux hangs.

  • If your

    Some content is unavailable due to permissions.

    environment will use HTTPS, ensure that your environment supports TLS secure transport protocol before upgrading to

    Some content is unavailable due to permissions.

    Platform.
  • For more information about configuring 

    Some content is unavailable due to permissions.

    with Remedy Single Sign-On, see Basic-deployment-scenarios-using-Remedy-Single-Sign-On.

Upgrade sequence

NoteBefore upgrading, stop the Some content is unavailable due to permissions. Platform component services. For example, if you are upgrading CDP, stop the CDP service and then continue with the upgrade.See Starting-and-stopping-product-components-and-services for details.
When upgrading components, you must upgrade them in the following order:
  1. Repository
  2. Configuration distribution peer (CDP)
    The Operator Control Panel can optionally be added with the CDP. 
  3. Additional peers
  4. Operator Control Panel (OCP)
  5. Some content is unavailable due to permissions. Development Studio
You can upgrade Some content is unavailable due to permissions. Content anytime after you upgrade the repository. When you finish upgrading the platform components, you use Grid Manager to update the content on the Grid. For more information about updating content on the grid, see Upgrading-adapters.

Upgrade worksheets

During an upgrade, the installation program displays settings from the previous installation that you can modify during the upgrade. The upgrade worksheets provide space for you to list the property settings that correspond to the text boxes and options that are displayed during the upgrade process.Where applicable, properties affected by upgrade scenarios are noted. If you choose to change these settings, use the worksheets in this section to record the new settings before you start the upgrade. 
You can also use the completed worksheets to edit the values in the options file templates used for silent upgrades.

Worksheets-for-upgrades-from-7-8-x-and-7-9-with-ASSO-to-8-2-with-RSSO

Where to go from here

Performing-upgrades-from-7-8-x-and-7-9-with-ASSO-to-8-2-with-RSSO

Upgrading-silently-from-7-8-x-and-7-9-with-ASSO-to-8-2-with-RSSO

 

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