Upgrading a solution with two AR System servers

The BMC Cloud Lifecycle Management installer enables you to upgrade BMC products that use two AR System servers (Enterprise-AR and Cloud-AR) in your cloud environment.

Note

The previous 2.1.x and 3.1.x releases used two AR System servers (Enterprise-AR and Cloud-AR) to run BMC Cloud Lifecycle Management. The 4.x release introduced the single AR System server architecture for all new installations of BMC Cloud Lifecycle Management.

Use the procedure explained in this section to upgrade BMC Cloud Lifecycle Management from 2.1.x or 3.x to 4.1.00.

Before you begin
To upgrade BMC Cloud Lifecycle Management to 4.x
Upgrading products in a High Availability environment
Where to go from here

The installer guides you step-by-step through the upgrade process, including the configuration of dependent products. You can upgrade one or more products at a time, based on the best practice upgrade sequence that BMC recommends. Because certain products are dependent on other products, you cannot upgrade all products at the same time.

Before you begin

Note

Update the customer range field IDs before you start upgrading. Otherwise, the upgrade will likely fail.
Do not run the installer on the same VM where you install the products; use a separate VM. You can recover this VM later, after you finish the cloud installation.
If you used this VM to install earlier versions of BMC Cloud Lifecycle Management, perform the following tasks before you run the 4.1 upgrade.
1. Uninstall the install planner.
2. Back up or delete the C:\Windows\ProductRegistry.xml file.
3. Delete %temp% files.
Accept the default values in the installer unless you have a good reason to change them.
Do not mix IP addresses and hostnames during product select in the Host Information panel. Enter all IP addresses or all hostnames, but do not combine them.
Some special characters create problems during installation. For more information, see Restricting the use of certain characters in passwords.
- For BMC Network Automation, do not use special characters except _.
- For BMC Server Automation, do not use #.

To upgrade BMC Cloud Lifecycle Management to 4.x

Download the BMC Cloud Lifecycle Management installation files from the EPD site.
Start the installer:
- On Microsoft Windows, double-click the setup.cmd file.
- On Linux, launch the installer by using Xmanager.
  With Xmanager, X applications installed on remote UNIX based computers run seamlessly with Windows applications side by side.
  You can also use VConsole to launch the installer.
In the lower right corner of the Welcome page, click Next.
Review the license agreement, click I agree to the terms of the license agreement, and then click Next.
On the Installation Prerequisites panel, review all the prerequisites that you must complete before you start the upgrade.
Select the I have read the prerequisites check box and click Next.
(optional) Select the Do not display this panel for subsequent installations check box if you do not want to view the prerequisites again during other product upgrades.
If you have not completed any of the prerequisites listed on the Installation Prerequisites panel, exit the installer and complete the steps first.
On the Directory Selection panel, navigate to the location on the host where you want to install the planner and click Next.
The default location is C:\Program Files\BMC Software\Planner.
On the Installation Preview panel, review the information and click Install.
If NSH is not installed, the system prompts you to install it.
The default location is C:\Program Files\BMC Software\NSH.
In the Select Installation Type panel, select Upgrade and then click Next.
In the Integrate Disclaimer Information panel, review the guidance.
Make sure that upgrading does not impact your customizations or your system performance.
Click I agree to the terms of the disclaimer, and then click Next.
On the BMC Installation Registry panel, select if you have a backup registry to use or if you are integrating from scratch, and then click Next.
The backup registry lists the target hosts and which products were installed on them. This example does not have an registry available to simplify the upgrade process. If you do not have a registry, you must compile your own list of target hosts.

For more information, see deployment template for other types to implement.
In the BMC AR System Configuration panel, the installer prompts you if you use only one AR System server in your environment.
Select No (I have an Enterprise-AR and a Cloud-AR server), and then click Next.
In the Select Deployment Template panel, select the template that matches your requirements.
For example, Small Deployment.
Click Next. The Deployment Tier Selection panel appears. You can upgrade products in the Control Tier, products in the Workload Tier, or products in both tiers.
Select Control Tier, and then click Next.
The default is Both, but this example only upgrades products in the Control Tier.

The Host Information for a Small Deployment panel appears for the Control Tier.
Enter all the product hosts in your environment, and then click Next.
The installer validates all the hosts on the Control Tier, to ensure a successful integration. You do not need to enter a host name in every field on this panel, just the product hosts currently used in your environment.
The Host Information panel performs the integration that, in earlier releases, was a pre-upgrade procedure.
When the installer finishes integrating all the products, review the products, versions, and hosts listed in the Integration Summary panel.
Click Next.
The Select Deployment Type panel is displayed, as shown in the following screenshot.
Choose Upgrade to Cloud Lifecycle Management 4.1.00, and then click Next.
All product hosts that you integrated with your BMC Cloud Lifecycle Management solution by running the 4.x installer are now visible in the Host Information panel. If the host name or the product that you chose for upgrade is incorrect, click Previous to correct the information.
The installer lists the products that you must upgrade in the order that you must upgrade them. Products that you need to upgrade are displayed with a blue arrow next to the host name. In this example, upgrade BMC Server Automation - App Server & Console first, Atrium Orchestrator - Configuration Distribution Peer second, and so on.
Clear all the other options except BMC Server Automation - App Server & Console (as shown in the previous screenshot) and then click Next.
Upgrade no more than two products in a session. For example, upgrade only BMC Server Automation - App Server & Console in this first session. Upgrade other products in subsequent sessions.
If the installer prompts you to perform specific integrations before you continue upgrading (as shown), do the following:
1. Click Previous in the installer.
2. Perform the integration tasks.
3. Click Next to continue.
Enter the operating system user credentials and passwords for the target host, and then click Next.
The installer validates the credentials, upgrades the RSCD Agent on the target host, and performs additional upgrade actions.
When the deployment confirmation panel appears, review the summary of the host settings.
(Linux only) In the Remote Staging Directory Information panel, review the directory (by default, /tmp), and then click Next.
Optionally, select Enable sub product remote staging directory option to enter an alternative staging area that you can use for all product installations if the /tmp directory on the remote hosts does not have sufficient space.
Click Next.
The Upgrade Progress panel is displayed, which shows you the overall status of the upgrade progress.
Tip
If you do not see any progress with the status bar, make sure that the product you are upgrading is selected under the Currently Upgrading section on the left navigation pane.
Take a VM snapshot and database backup, as prompted by the installer.
At the prompts, enter the installation inputs for each product from your planning spreadsheet.
Complete the upgrade and exit the installer to finish the session.
Upgrade the next product in order.

Upgrading products in a High Availability environment

This section explains the steps that you must perform for upgrading product hosts on High Availability servers.

To upgrade the Atrium Core Web registry

After you upgrade the Atrium Core Web Registry using the BMC Cloud Lifecycle Management Installer, perform the following steps to prepare for the HA upgrade:

Using a Web browser, log on to the enterprise AR System server through the Midtier.
From the Object List, search for and open the SHARE:Application_Properties form.
Click Search on the tool bar.
You should see 4 entries for the Atrium Core Web Registry product. Note the Version values.
Upgrade the primary Atrium Core Web Registry server using the BMC Cloud Lifecycle Management installer.
Open the SHARE:Application_Properties form.
For each Atrium Core Web Registry entry, revert the Version value to the value you noted before the installation.
Copy the Atrium Core Web Registry installer to the secondary Atrium Core Web Registry server.
Start the upgrade process on the Atrium Core Web Registry – Secondary host.

To upgrade BMC Network Automation

Before you upgrade the secondary server, update the SKIP_DB_UPGRADE parameter value to true in the /opt/bmc/bca-networks/BcanInstalledConfiguration.xml file. For example:

<property>

<name>SKIP_DB_UPGRADE</name>

<value>true</value>

</property>

After you complete the BMC Network Automation – Primary server installation, perform the following steps:

Make a backup of your filesystem (the BCA-Networks and BCA-Network-Data folders) on both the primary and secondary servers.
Upgrade the primary server.
Failover the BMC Network Automation cluster service to the secondary server.
Upgrade the secondary server.

To upgrade the Cloud Platform Manager

Because you only need one installation of Cloud Platform Manager, you only need to upgrade it once.

Make a backup copy of the BMCCloudLifeCycleManagement folder.
Upgrade the Cloud Platform Manager using the BMC Cloud Lifecycle Management installer.
Move the cluster resources to another node.
If you are upgrading from 2.1.x to 4.x, manually create the Quick Start service soft link.
You do not need to perform this step is you are upgrading from 3.x to 4.x – these links are already present.

On Microsoft Windows:
C:\>sc create BMCQuickStart binPath= "\"S:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\QuickStart\quickstart.exe\" -s \"S:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\QuickStart\quickstart.conf\"" DisplayName= "BMC Quickstart"
On Linux:
ln -s /gfs/bmc/BMCCloudLifecycleManagement/Platform_Manager/QuickStart/sh.script.in /etc/init.d/BMCQuickStart

Where to go from here

When you finish upgrading all the BMC Cloud Lifecycle Management products, verify that the upgrade was successful.
Apply the following hotfixes after you install or upgrade version 4.1.00:
- KA414865 – This hotfix is required for all BMC Cloud Lifecycle Management deployment.
- KA414866 – This hotfix applies only if you have BMC Capacity Optimization deployed in your environment.
Perform the post-upgrade configuration tasks.