×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.
(archive) BMC Atrium Orchestrator Platform 7.7 ... Upgrading Upgrading silently

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 earlier installation, use the templates in Sample platform upgrade options file templates.

Access Manager is not supported in releases after 7.6.03 and is replaced with BMC Atrium Single Sign-On. This requires the following upgrade tasks:

  • 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 from 7.6.02.xx, you must specify different properties for the repository and CDP.
    • When upgrading BMC Atrium Orchestrator Development Studio, use the upgrade worksheets to help gather the properties for this component.
  • 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.

  1. Open a text editor to create a new options file.
  2. Copy the sample content from Sample platform upgrade options file templates 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.

    Example

    -P installLocation=c:\Program Files\BMC Software\AO_HOME

  4. For the AO_INSTALL_TYPE property, specify upgrade_new as the silent installation type.
    -J AO_INSTALL_TYPE=upgrade_new
  5. Modify the remaining properties for the BMC Atrium Orchestrator component upgrade.
  6. Save the file with a name that indicates the purpose of the file. 
    For example, you could name the file bao_upgrade.options.

  7. Repeat this process to create an options file for each component you are upgrading (using a different file name for each component). 

Note

Ensure that you have updated Access Manager references to be BMC Atrium Single Sign-On and that you have an options file that upgrades only the repository.

To create option files for BMC Atrium Orchestrator 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 into the new file.

  3. (optional) In the new file, modify the installLocationproperty and specify an existing directory in which to install the component.

    Example

    -P installLocation=c:\Program Files\BMC Software\AO\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 BMC Atrium Orchestrator 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 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.

Was this page helpful? Yes No Submitting... Thank you
Last modified by Dorothy Poole on Mar 10, 2015
upgrading options_files preparing silent

Comments

Log in or register to comment.

Upgrading silently
Sample platform upgrade options file templates
© Copyright 2013-2017 BMC Software, Inc.
© Copyright 2013-2017 BladeLogic, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.