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

Unsupported content

 

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.
BMC Atrium Orchestrator Platform 7.9 ... Upgrading Upgrading from BAO 7.6.03 versions to 7.9.01 with RSSO

Preparing for upgrades from 7.6.03

This section describes how to prepare for an upgrade of the BMC Atrium Orchestrator Platform product:

Before upgrading

  • Review supported upgrade paths in Upgrading
  • When you upgrade from 7.6.03 to 7.9.x, the Access Manager component is replaced by BMC Remedy Single Sign-On. A migration utility/tool is provided, which exports all authentication data from Access Manager and then allows you to import the data in Grid Manager. 
    To successfully transport the data, you must run the migration tool before you start with the upgrade. For more information, see Migrating authentication and authorization data from Access Manager. 
  • 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 your BMC Atrium Orchestrator environment will use HTTPS, ensure that your environment supports TLS secure transport protocol before upgrading to BMC Atrium Orchestrator Platform.
  • For more information about configuring BMC Atrium Orchestrator with Remedy Single Sign-On, see Basic deployment scenarios using Remedy Single Sign-On.

Recommendation

In platform versions earlier than 7.7, BMC Atrium Orchestrator supported the installation or combination of certain edge components, such as BMC Atrium Orchestrator Operator Control Panel with a graphing server. However, this combination cannot be upgraded in 7.7 or later.

During an upgrade, when you point to the home directory of such an installation, the following message is displayed, indicating that a component or combination is no longer supported:

Cannot upgrade the installed feature/combination of features. Please refer to the user documentation section Preparing for upgrade for supported features.

BMC recommends that you review the following list of available components and combinations, and within your existing license counts, decide whether the current server should be retired or be replaced by an alternate component or combination.

  • Repository
  • Configuration distribution peer
    • BMC Atrium Orchestrator Operator Control Panel
  • Activity peer
  • Lightweight activity peer
  • BMC Atrium Orchestrator Operator Control Panel
  • BMC Development Studio
  • Dashboard

 

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.6.03

Upgrade sequence

Note

Before upgrading, stop the BMC Atrium Orchestrator 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. BMC Atrium Orchestrator Development Studio

You can upgrade BMC Atrium Orchestrator 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.

Note

After the upgrade, ensure that you complete the procedures in Configuring after upgrade. For example, you must complete the setup for a fail-safe service bus and other configurations for your environment.

Where to go from here

Performing upgrades from 7.6.03
Upgrading silently from 7.6.03

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.

Last modified by Dorothy Poole on Feb 24, 2017
upgrading planning concept related_topics paths roadmap best_practices recomm worksheets

Comments

Log in or register to comment.

Using a role mapping file to import default roles
Installing an authentication service before BAO 7.6.03 upgrades
© Copyright 2016-2017 BMC Software, Inc.
© Copyright 2016-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.