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.

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.

Note

  • When you run upgrades from 2.1, 3.0, or 3.1 to 4.0, out-of-the-box the installer does not upgrade BMC Remedy IT Service Management, Atrium Integrator, and SLM. In the 4.0 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.

The sequences in the tables include 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.

Before you begin

Before you start upgrading the products, make sure that you review the upgrade prerequisites attachment (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.

Note

Because you can upgrade to BMC Cloud Lifecycle Management 4.0 from two different paths – 2.1 and 3.x – the products to upgrade and the upgrade steps might differ. Therefore, you must carefully review the information documented in the prerequisites for the upgrade topic.

Unsupported parameter for macro: title Due of this, the macro might have some unexpected results.

Upgrade sequence for Single VM RDS

You can upgrade the Single VM RDS Linux 3.1 SP1 deployment to 4.0. This procedure is fully documented end-to-end at Upgrading-Small-Deployment-In-Place-method.

Upgrade sequence for POC deployments

The POC deployment model is no longer supported in version 4.0; POC is replaced by the single VM Compact Deployment model. To upgrade your 3.x POC deployment, follow the upgrade sequence for small, medium, and large deployments. 

Upgrade sequence for Small, Medium, and Large deployments

The upgrade order listed in the following table applies to the Small, Medium, and Large deployment types. To learn more about which deployment type works best for your requirements, see Deployment architecture. This sequence applies to all upgrade methods: in-place, staged, and staged-lite.

Sequence

Product

Order of tasks for upgrade

1

BMC Server Automation – File Server

No manual tasks required for this product. Directly upgrade to 4.0 using the installer planner.

2

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

3

BMC Server Automation – (MAS)

  1. Upgrade BMC Server Automation – Application Server.
  2. Perform post-installation configuration tasks after the upgrade.

4

(Optional) PXE server

  • Upgrade the PXE server only after you have upgraded all application servers.
  • On Windows, make a backup copy of the TFTP folder, which is located in the <PXE Server Installation directory>. During the 4.0 upgrade, the PXE server uninstalls the existing TFTP folder before installing the latest version.

5

(Optional) BMC Server Automation – Advanced Repeater 

No manual tasks required for this product. Directly upgrade to 4.0 using the installer planner.

6

BMC Atrium Orchestrator – Configuration Distribution Peer

Perform the following steps for BMC Atrium Orchestrator – Configuration Distribution Peer when upgrading BMC Cloud Lifecycle Management:

  1. 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. RCP Client
  2. Manually activate the BMC Atrium Orchestrator adapters.
  3. Stop the HACDP service before you start the upgrade on BMC Atrium Orchestrator – Configuration Distribution Peer.

7

Atrium Orchestrator – Configuration Distribution Peer for High Availability (HA) 

  1. Upgrade the BMC Server Automation Console.
  2. Upgrade the Configuration Distribution Peer.

8

BMC 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.0, use BMC Remedy Developer Studio to install the hotfix located at clm40build/Applications/AtriumCore/Common/hotfix.
      Follow the Windows and Linux instructions in 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.

9

BMC Remedy AR System Cloud Database – Primary (Cloud-AR)
Note: Before you start the upgrade, review Known issues defect QM001764172 for possible issues.

  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.

10

BMC AR System & BMC Remedy IT Service Management Suite – Secondary
Note: Before you start the upgrade, review Known issues defect QM001764172 for possible issues.

  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. BMC Remedy ITSM, if it exists in the 2.1 or 2.1 SPx implementation
      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 on how to apply the hotfix on Windows and Linux, see Readme.txt.

11

BMC Remedy AR System Cloud Database – Secondary
Note: Before you start the upgrade, review Known issues defect QM001764172 for possible issues.

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

12

BMC Remedy Mid Tier 

No manual tasks required for this product. Directly upgrade to 4.0 using the installer planner..

13

BMC Atrium Core – Web Registry Components

No manual tasks required for this product. Directly upgrade to 4.0 using the installer planner..

14

BMC 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 preserving the application server database.

15

(Optional) BMC Network Automation – Device Agent 

No manual tasks required for this product. Directly upgrade to 4.0 using the installer planner.

16

Cloud Database Extensions

No manual tasks required for this product. Directly upgrade to 4.0 using the installer planner. 

17

Cloud Platform Manager

If you have installed Cloud Platform Manager in an HA environment, you need to upgrade only the Cloud Platform Manager – Primary server. 

18

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

19

Cloud Portal AR Extensions – Secondary

No manual tasks required for this product. Directly upgrade to 4.0 using the installer planner. 

 

Where to go next

Product-versions-and-compatibility

Performing-the-upgrade

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*