Creating options files for an upgrade from 7.7.x, 7.8.x, and 7.9.00 with ASSO to 8.0 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 Development Studio upgrades.
Tip
- When upgrading from earlier
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
toupgrade_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
- For platform components:
- If you cannot locate the options files from the previous installation, use the templates in Sample platform upgrade options file templates for upgrades from 7.7.x, 7.8.x, and 7.9.00 with ASSO to 8.0 with RSSO. The instructions in this page describe how to create new options files using these templates.
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.
- When upgrading components and Development Studio, use the upgrade worksheets to help gather the properties. See Preparing for upgrades from 7.7.x, 7.8.x, and 7.9.00 with ASSO to 8.0 with RSSO 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 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 for upgrades from 7.7.x, 7.8.x, and 7.9.00 with ASSO to 8.0 with RSSO 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.In this example,
<component>
will be replaced with a component name, such as CDP or REPO.- For the
AO_INSTALL_TYPE
property, specifyupgrade_new
as the silent installation type.-J AO_INSTALL_TYPE=upgrade_new
NEW IN 8.0If 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
.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.- Modify the remaining properties for the 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 Development Studio upgrade
- Open a text editor to create a new options file.
- Copy the sample content from Sample platform upgrade options file templates for upgrades from 7.7.x, 7.8.x, and 7.9.00 with ASSO to 8.0 with RSSO 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.- For the
DEVSTUDIO_INSTALL_TYPE
property, specifyupgrade_new
as the silent installation type.-J DEVSTUDIO_INSTALL_TYPE=upgrade_new
- Modify the remaining properties for the 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 from 7.7.x, 7.8.x, and 7.9.00 with ASSO to 8.0 with RSSO to upgrade the platform.
Related topic
Content upgrades involve multiple steps: first create the options files to install the content (adapters and modules), install the content, then update the content version in the Grid Manager. To create options files for content, use the templates in Sample content options file templates.
Comments
Log in or register to comment.