×
 
 
  •  
$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.
BMC Cloud Lifecycle Management 4.6 Upgrading

Reviewing the upgrade sequence

When you launch the BMC Cloud Lifecycle Management installer to upgrade the products in the solution, host names are displayed for each product. The upgrade sequence defined by the install planner includes products from both the Control Tier and Workload Tier. In an upgrade scenario, the emphasis is more on the upgrade order instead of on available products within a tier.

Note

  • When you run upgrades from 3.0 or 3.1 to 4.1, out-of-the-box the installer does not upgrade BMC Remedy IT Service Management, Atrium Integrator, and SLM. In the installer, these nodes will not be queued for upgrade. If you must upgrade BMC Remedy IT Service Management and Atrium Integrator, use the following command to launch the installer:
    setup.cmd/sh -J skip_itsm=false
  • Select only one product at at time to upgrade, based on the upgrade sequences in the following sections.

Before you start upgrading the products, make sure that you review the upgrade prerequisites in the attached Microsoft Excel spreadsheet. Because not all products are available in each of the deployment types, the upgrade order that you must follow depends on the deployment type that you chose.

Upgrade sequence for POC deployments

The proof of concept (POC) deployment model found in the 3.x version of the product is no longer supported in version 4.x. POC is replaced by the single VM Compact Deployment model. To upgrade your 3.x POC deployment, follow the upgrade sequence for small and medium deployments.

Upgrade sequence for Small and Medium deployments (3.x to 4.1)

The upgrade order listed in the following table applies to the Small and Medium deployment types. To learn more about which deployment type works best for your requirements, see deployment architecture.

Note

When upgrading from 2.1.x and 3.x to 4.1, you upgrade 2 AR System servers to 2 AR System servers.

SequenceProductOrder of tasks for upgrade
1BMC Server Automation – File ServerNo manual tasks required for this product. Directly upgrade to 4.x using the installer planner.
2BMC Server Automation – Application Server & Console
  1. When prompted by the installer, stop the PXE server, BMC Server Automation – Multiple Application Server (MAS), and BMC Server Automation – Advanced Repeater services, if available. 
  2. Upgrade BMC Server Automation Application Server
  3. Manually perform BMC Server Automation database migration.
  4. Manually start the appserver.
  5. Upgrade BMC Server Automation Console.
  6. Complete the BMC Server Automation post-upgrade configuration in the installer.
  7. Manually upgrade the Virtual Center (VC) agent.
  8. Manually upgrade the BMC RSCD Agent on the source VM Template. 
    After upgrading the RSCD Agent, ensure that the Exports file mappings are appropriately configured.
3BMC Server Automation – Multiple Application Server (MAS)
  1. Upgrade BMC Server Automation – Application Server.
  2. Perform post-upgrade configuration tasks after the upgrade.
4(Optional) BMC Server Automation – Advanced Repeater No manual tasks required for this product. Directly upgrade to 4.x using the installer planner.
Note: PXE server upgrade is not supported through the Install Planner. Therefore, skip inputs for the PXE server. You can upgrade it after the BMC Cloud Lifecycle Management upgrade is complete. See Upgrading the BladeLogic PXE server for instructions.
5BMC Atrium Orchestrator – Configuration Distribution Peer

Perform the following steps for BMC Atrium Orchestrator – Configuration Distribution Peer:

  1. Stop the HACDP service before you start the upgrade on BMC Atrium Orchestrator – Configuration Distribution Peer.
  2. Upgrade the following components in this order using the installer planner:
    1. Access Manager and Repository
    2. Configuration Distribution Peer
    3. Atrium Orchestrator Content
    4. BMC Server Automation Console
    5. BMC Atrium Orchestrator Post Installation Configuration
  3. Manually activate the BMC Atrium Orchestrator adapters.
6Atrium Orchestrator – Configuration Distribution Peer for High Availability (HA) 
  1. Upgrade the BMC Server Automation Console.
  2. Upgrade the Configuration Distribution Peer.
7BMC AR System & BMC Remedy IT Service Management Suite – Primary (Enterprise-AR)
  1. Install BMC AR System & BMC Remedy IT Service Management Suite – Primary and BMC Remedy AR System Cloud Database – Primary in the same session.
  2. Upgrade the following BMC Remedy AR System & BMC Remedy IT Service Management Suite components in this order using the installer planner:
    1. AR System server
    2. If you are upgrading from 3.0 to 4.x, use BMC Remedy Developer Studio to install the hotfix located at /Applications/AtriumCore/Common/hotfix.
      Follow the Windows and Linux instructions in /Applications/AtriumCore/Common/hotfix/Readme.txt before you upgrade BMC Atrium Core.
    3. BMC Atrium Core
    4. Atrium Integrator
    5. If you launched the installer planner with the setup.cmd/sh -J skip_itsm=false condition to upgrade BMC Remedy IT Service Management, you now see its node. Otherwise, the BMC Remedy IT Service Management node is not displayed by default.
    6. BMC Remedy Service Request Management
    7. AR Post Install Configuration
  3. Modify ar.conf/ar.cfg (by default, located in <AR_Install_Dir>/conf) by setting CMDB-Inline-Normalization to F.
8BMC Remedy AR System Cloud Database – Primary (Cloud-AR)
  1. Upgrade the following BMC Remedy AR System Cloud Database – Primary components in this order using the installer planner:
    1. AR System server
    2. Atrium Core
  2. Upgrade Enterprise-AR DSO mapping using the installer.
  3. Perform the post-upgrade configuration steps for the AR System server using the installer.
  4. Modify ar.conf/ar.cfg (by default, located in <AR_Install_Dir>/conf) by setting CMDB-Inline-Normalization to F.
  5. Perform Cloud-AR DSO mapping using the installer.
9BMC AR System & BMC Remedy IT Service Management Suite – Secondary 
  1. Upgrade the following BMC Remedy AR System & BMC Remedy IT Service Management Suite components in this order using the installer planner:
    1. AR System server
    2. Atrium Core
    3. Atrium Integrator
    4. Upgrading BMC Remedy ITSM is optional. If you must upgrade, use the following command to launch the installer:
      setup.cmd/sh -J skip_itsm=false  
    5. BMC Remedy Service Request Management
  2. Perform the post-upgrade configuration steps for the AR System server using the installer.
  3. Modify ar.conf/ar.cfg (by default, located in <AR_Install_Dir>/conf) by setting CMDB-Inline-Normalization to F.
  4. Use BMC Remedy Developer Studio to perform the hotfix located at <Install_Planner_Dir>/Applications/AtriumCore/Common/hotfix.
    For detailed information about how to apply the hotfix on Windows and Linux, see <Install_Planner_Dir>/Applications/AtriumCore/Common/hotfix/Readme.txt.
10BMC Remedy AR System Cloud Database – Secondary 
  1. Upgrade the following BMC Remedy AR System Cloud Database – Secondary components in this order using the installer planner:
    1. AR System server
    2. Atrium Core
  2. Upgrade Enterprise-AR DSO mapping using the installer.
  3. Perform the post-upgrade configuration steps for the AR System server using the installer.
  4. Modify ar.conf/ar.cfg (by default, located in <AR_Install_Dir>/conf) by setting CMDB-Inline-Normalization to F.
  5. Perform Cloud-AR DSO mapping using the installer.
11BMC Remedy Mid Tier No manual tasks required for this product. Directly upgrade to 4.x using the installer planner.
12BMC Atrium Core – Web Registry ComponentsNo manual tasks required for this product. Directly upgrade to 4.x using the installer planner.
13BMC Network Automation

Note: Upgrading the BMC Network Automation server in an HA environment is not supported by the installer planner. Therefore, you must perform the upgrade using the BMC Network Automation product installer.

  1. Upgrade the BMC Network Automation – Primary server where the cluster and application service is active.
  2. Failover the cluster.
  3. In the silent.ini file, set the SKIP_DB_UPGRADEoption to true. You use this option to skip the database update step on the secondary servers. For more information, see running the installer in silent mode.
  4. Perform the upgrade using the BMC Network Automation product installer; see Performing the upgrade.
14(Optional) BMC Network Automation – Device Agent No manual tasks required for this product. Directly upgrade to 4.x using the installer planner.
15Cloud Database ExtensionsNo manual tasks required for this product. Directly upgrade to 4.x using the installer planner. 
16Cloud Platform ManagerIf you have installed Cloud Platform Manager in an HA environment, you need to upgrade only the Cloud Platform Manager – Primary server. 
17Cloud Portal AR Extensions – Primary

Upgrade the following Cloud Portal AR Extensions components in this order using the installer planner: 

  1. Cloud Portal AR Extensions – Primary.
  2. Using the Cloud Upgrade Migration option in the installer, migrate the BMC Cloud Lifecycle Management data. 
    Note: Make sure that you have your Cloud administrator credentials ready before you begin the Cloud upgrade migration using the installer.
18Cloud Portal AR Extensions – SecondaryNo manual tasks required for this product. Directly upgrade to 4.x using the installer planner. 

Upgrade sequence for Small and Medium deployments from 4.x to 4.6.x

Note

When upgrading from 4.x to 4.6.x, first you upgrade 2 AR System server to 1 AR System server, and then upgrade to 4.6.x.
SequenceProductOrder of tasks for upgrade
1BMC Server Automation – File ServerNo manual tasks required for this product. Directly upgrade to 4.x using the installer planner.
2BMC Server Automation – Application Server & Console
  1. When prompted by the installer, stop the PXE server, BMC Server Automation – Multiple Application Server (MAS), and BMC Server Automation – Advanced Repeater services, if available. 
  2. Upgrade BMC Server Automation Application Server
  3. Manually perform BMC Server Automation database migration.
  4. Manually start the appserver.
  5. Upgrade BMC Server Automation Console.
  6. Complete the BMC Server Automation post-upgrade configuration in the installer.
  7. Manually upgrade the Virtual Center (VC) agent.
  8. Manually upgrade the BMC RSCD Agent on the source VM Template. 
    After upgrading the RSCD Agent, ensure that the Exports file mappings are appropriately configured.
3BMC Server Automation – Multiple Application Server (MAS)
  1. Upgrade BMC Server Automation – Application Server.
  2. Perform post-upgrade configuration tasks after the upgrade.
Note: PXE server upgrade is not supported through the Install Planner. Therefore, skip inputs for the PXE server. You can upgrade it after the BMC Cloud Lifecycle Management upgrade is complete. See Upgrading the BladeLogic PXE server for instructions.
4(Optional) BMC Server Automation – Advanced Repeater No manual tasks required for this product. Directly upgrade to 4.x using the installer planner.
5BMC Atrium Orchestrator – Configuration Distribution Peer

Perform the following steps for BMC Atrium Orchestrator – Configuration Distribution Peer:

  1. Stop the HACDP service before you start the upgrade on BMC Atrium Orchestrator – Configuration Distribution Peer.
  2. Upgrade the following components in this order using the installer planner:
    1. Access Manager and Repository
    2. Configuration Distribution Peer
    3. Atrium Orchestrator Content
    4. BMC Server Automation Console
    5. BMC Atrium Orchestrator Post Installation Configuration
  3. Manually activate the BMC Atrium Orchestrator adapters.
6Atrium Orchestrator – Configuration Distribution Peer for High Availability (HA) 
  1. Upgrade the BMC Server Automation Console.
  2. Upgrade the Configuration Distribution Peer.
7BMC Network Automation

Note: Upgrading the BMC Network Automation server in an HA environment is not supported by the installer planner. Therefore, you must perform the upgrade using the BMC Network Automation product installer.

  1. Upgrade the BMC Network Automation – Primary server where the cluster and application service is active.
  2. Failover the cluster.
  3. In the silent.ini file, set the SKIP_DB_UPGRADEoption to true. You use this option to skip the database update step on the secondary servers. For more information, see running the installer in silent mode.
  4. Perform the upgrade using the BMC Network Automation product installer; see Performing the upgrade.
8(Optional) BMC Network Automation – Device Agent No manual tasks required for this product. Directly upgrade to 4.x using the installer planner.
9Cloud Database ExtensionsNo manual tasks required for this product. Directly upgrade to 4.x using the installer planner. 
10Cloud Platform ManagerIf you have installed Cloud Platform Manager in an HA environment, you need to upgrade only the Cloud Platform Manager – Primary server. 
11Cloud Portal AR Extensions – Primary

Upgrade the following Cloud Portal AR Extensions components in this order using the installer planner: 

  1. Cloud Portal AR Extensions – Primary.
  2. Using the Cloud Upgrade Migration option in the installer, migrate the BMC Cloud Lifecycle Management data. 
    Note: Make sure that you have your Cloud administrator credentials ready before you begin the Cloud upgrade migration using the installer.
12Cloud Portal AR Extensions – SecondaryNo manual tasks required for this product. Directly upgrade to 4.x using the installer planner. 

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 Ranu Ganguly on Jan 12, 2018

Comments

Log in or register to comment.

Upgrading
Preparing for upgrades
© Copyright 2013 - 2017 BMC Software, 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.