Skip to Content

Creating options files for an upgrade from 7.8.x and 7.9 with ASSO to 8.2 with RSSO

You must create an options file for each platform upgrade that you need to perform. This section provides an overview of the steps to perform when creating options files for server components and 

WarningSome content is unavailable due to permissions.

Development Studio upgrades.

Success

Tip

  • When upgrading from earlier

    WarningSome content is unavailable due to permissions.

    versions, you can quickly create options files by copying the options files that were created during the previous product installation and updating them. Before you can use these files for the upgrade, you must change the install type property from install_new to upgrade_new. The install type property name varies for the platform component and Development Studio as follows:
    • For platform components: AO_INSTALL_TYPE
    • For Development Studio: DEVSTUDIO_INSTALL_TYPE
Warning

The upgrade procedures also involve the following:

  • BMC Atrium Single Sign-On is not supported in 7.9.01 and later and is replaced with Remedy Single Sign-On. When upgrading the repository or CDP, you must delete any references to Atrium Single Sign-On and specify the Remedy Single Sign-On details in the options files.
  • Since Atrium Single Sign-On will be removed, you must create an options file that upgrades only the repository.

Before you begin

Review the upgrade worksheets and modify any of the properties that you need to change for the upgrade.

To create options files for a platform component upgrade

In these instructions, AO_HOME represents the directory in which you installed the

WarningSome content is unavailable due to permissions.

component on a server.

  1. Open a text editor to create a new options file.
  2. Copy the sample content from Sample-platform-upgrade-options-file-templates-for-upgrades-from-7-8-x-and-7-9-with-ASSO-to-8-2-with-RSSO into the new file. 

  3. In the new file, modify the installLocation property and specify an existing directory in which to install the component. You can leave the default path if it is correct for your installation.

    Information-P installLocation=c:\Program Files\BMC Software\BAO\<component>In this example, <component> will be replaced with a component name, such as CDP or REPO.

  4. For the AO_INSTALL_TYPE property, specify upgrade_new as the silent installation type.
    -J AO_INSTALL_TYPE=upgrade_new

  5. If using external Remedy SSO, specify the version in the -J AO_RSSO_VERSION property. 
    If your external Remedy SSO version is 9.1.03.x, specify -J AO_RSSO_VERSION=9.1.03.x. For earlier versions, specify -J AO_RSSO_VERSION=9.1.02.

    Warning

    Note

    Specify the -J AO_RSSO_VERSION property for the repository, CDP, HA-CDP, CDP (along with the OCP), stand-alone OCP and AP components only.

  6. Modify the remaining properties for the

    WarningSome content is unavailable due to permissions.

    component upgrade.
  7. Save the file with a name that indicates the purpose of the file. 
    For example, you could name the file bao_upgrade.options.
  8. Repeat this process to create an options file for each component you are upgrading (using a different file name for each component).

To create option files for

WarningSome content is unavailable due to permissions.

Development Studio upgrade

  1. Open a text editor to create a new options file.
  2. Copy the sample content from Sample-platform-upgrade-options-file-templates-for-upgrades-from-7-8-x-and-7-9-with-ASSO-to-8-2-with-RSSO into the new file. 

  3. In the new file, modify the installLocation property and specify an existing directory in which to install the component. You can leave the default path if it is correct for your installation.

    Information-P installLocation=c:\Program Files\BMC Software\BAO\Studio

  4. For the DEVSTUDIO_INSTALL_TYPE property, specify upgrade_new as the silent installation type.
    -J DEVSTUDIO_INSTALL_TYPE=upgrade_new 
  5. Modify the remaining properties for the

    WarningSome content is unavailable due to permissions.

    Development Studio upgrade.
  6. Save the file with a name that indicates the purpose of the file.
    For example, you could name the file bao_studio_upgrade.options.

Where to go from here

Use the procedure in Executing-a-silent-upgrade-from-7-8-x-and-7-9-with-ASSO-to-8-2-with-RSSO to upgrade the platform. 

 

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

TrueSight Orchestration Platform 8.2