Creating options files for an upgrade

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 BMC Atrium Orchestrator Development Studio upgrades.

Tip

When upgrading from earlier BMC Atrium Orchestrator 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

If you cannot locate the options files from the previous installation, use the templates in Sample-platform-upgrade-options-file-templates. The instructions in this page describe how to create new options files using these templates.

If you are upgrading from 7.6.03, the upgrade procedures also involve the following:

Access Manager is not supported in releases after 7.6.03 and is replaced with BMC Atrium Single Sign-On; therefore, when upgrading the Access Manager and repository or CDP, you must delete any references to Access Manager and specify the BMC Atrium Single Sign-On details in the options files.
Since Access Manager 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.

When upgrading BMC Atrium Orchestrator components and Development Studio, use the upgrade worksheets to help gather the properties. See Preparing-for-upgrade for the worksheets.
Review Silent-installation-properties to ensure that your options file contains any required properties that might be new for this release.

To create options files for a platform component upgrade

In these instructions, AO_HOME represents the directory in which you installed the BMC Atrium Orchestrator component on a server.

Open a text editor to create a new options file.
Copy the sample content from Sample-platform-upgrade-options-file-templates into the new file.
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.
-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.
For the AO_INSTALL_TYPE property, specify upgrade_new as the silent installation type.
-J AO_INSTALL_TYPE=upgrade_new
Modify the remaining properties for the BMC Atrium Orchestrator component upgrade.
Save the file with a name that indicates the purpose of the file.
For example, you could name the file bao_upgrade.options.
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 BMC Atrium Orchestrator Development Studio upgrade

Open a text editor to create a new options file.
Copy the sample content from Sample-platform-upgrade-options-file-templates into the new file.
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.
Example
-P installLocation=c:\Program Files\BMC Software\BAO\Studio
For the DEVSTUDIO_INSTALL_TYPE property, specify upgrade_new as the silent installation type.
-J DEVSTUDIO_INSTALL_TYPE=upgrade_new
Modify the remaining properties for the BMC Atrium Orchestrator Development Studio upgrade.
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 to upgrade the platform.