Upgrading BMC Helix Service Management in a secondary cluster

Upgrade BMC Helix Service Management to version 25.1.01 in your disaster recovery (secondary) cluster so that it can seamlessly take over if the primary cluster fails. This ensures all components, including BMC Helix Innovation Suite and Service Management applications are up to date.

Before you begin

Make sure that your primary BMC Helix Service Management cluster is upgraded to version 25.1.01.
Make sure that you update the Git repositories in your secondary cluster to the version same as in your primary cluster.

Task 1: To update the deployment pipelines

Important

You must perform the following steps to update the parameters of the existing pipelines. These steps act as a dry run to make sure that the existing pipelines use the updated configuration from the new version repositories.
After you update the parameters, proceed to run the HELIX_ONPREM_DEPLOYMENT pipeline.

Perform the following steps to update the HELIX_ONPREM_DEPLOYMENT pipeline.
1. On the Jenkins server, select the HELIX_ONPREM_DEPLOYMENT pipeline.
2. Start a new Build with Parameters
3. Specify the AGENT value.
4. Click Build.
  After the pipeline is rebuilt, the updated parameters for the pipeline are reflected.
Update the HELIX_GENERATE_CONFIG pipeline so that the updated parameters for the pipeline are reflected.
1. On the Jenkins server, select the HELIX_GENERATE_CONFIG pipeline.
2. In Build History, select the latest build and click Rebuild.
3. Click Rebuild.
  After the pipeline is rebuilt, the updated parameters for the pipeline are reflected.
Update the HELIX_DR pipeline so that the updated parameters for the pipeline are reflected.
1. On the Jenkins server, select the HELIX_DR pipeline.
2. Click Build with Parameter, and then click Build.
  After the pipeline is rebuilt, the updated parameters for the pipeline are reflected.

Task 2: To upgrade BMC Helix Service Management in a secondary cluster

Select the HELIX_ONPREM_DEPLOYMENT pipeline, select the latest successful build, and then click Rebuild.

In the ENVIRONMENT DETAILS section, specify the following parameters:

Parameter	Description
DEPLOYMENT_MODE	Specify the value as FRESH. Important: Make sure you select the Fresh mode. The Helm upgrade is automatically handled through the pipeline, even when Fresh mode is selected.
SOURCE_VERSION	Specify NA for the source version of the Helm repositories.
PLATFORM_HELM_VERSION	Specify 2025101.1.00.00 for the target version of the Helm repositories.
SMARTAPPS_HELM_VERSION	Specify 2025101.1.00.00 for the smart applications version of the Helm repositories.
(Optional) CACERTS_FILE	If you are using a custom CA certificate or self-signed certificate to use HTTPS communication for Service Management applications, click Browse and upload your custom cacerts file.

In the PIPELINES section, select the check boxes for the HELIX_GENERATE_CONFIG, HELIX_DR, and SCALE_DOWN parameters.
Click Rebuild.

After the build is complete, the secondary cluster is upgraded and is in scale down mode.

Where to go from here

Recovering after a disaster