Preparing for upgrade

Perform the following tasks before upgrading BMC Helix IT Operations Management (BMC Helix ITOM):

 

TaskActionReference
1

Make sure you have created the URLs required to access BMC Helix ITOM applications.

2

Upgrade to the latest version of  BMC Discovery 24.3.x.

Important: BMC Discovery is not mandatory if you only use BMC Helix Continuous Optimization.

To install BMC Discovery, see Installingin the BMC Discovery documentation.

To upgrade to BMC Discovery, see Upgrading in the BMC Discovery documentation.

3

Back up all the PersistentVolumeClaim (PVC) data. 

Important: We do not have a specific best practice for this step. However, we recommend using your preferred method to back up the PVC data based on the type of PVC.

 

4

Back up your customizations in the deployment manager and the cluster.

 

For example:

If you are using a self-signed or custom-signed certificate, back up the certificates (custom_cacert.pem, cacerts, or any other certificates on which you have set up an LDAP) from helix-on-prem-deployment-manager/commons/certs/. 

5

Create a new workspace directory on the system from where you will run the BMC Helix ITOM deployment script.
This directory will be your new working directory (For example, working_directory).

 

6

Download the deployment manager to the working_directory.

7

Download the latest container images required to perform the upgrade.

8

Use the upgrade configuration utility.

The utility picks the values from the latest successful deployment of BMC Helix ITOM to configure the infra.config, deployment.config, and secrets.txt files. 

 

For more information, see Using the upgrade configuration utility.

9

(Optional) Define a password for the user,

Applications will use a non-default user for Elasticsearch connections for Log Elasticsearch (Log ES), which you can define in the secrets.txt file.

10

If you changed the default passwords for BMC Helix Single Sign-on (HSSO) and Elasticsearch during the installation of BMC Helix ITOM (for more information, see Preparing for password encryption), you must set the same password before upgrading BMC Helix ITOM. 

To set the passwords:

  1. Navigate to commons/certs/default/
  2. Open the default.password file.
  3. Set the values of the following parameters:
    • RSSO_NEW_PASSWORD
    • RSSO_PASSWORD
    • LOCAL_PASSWORD

To use a non-default user, go to the secrets.txt file and change the default value of the LOG_ES_PASSWD parameter.

The password must meet the following requirements:

  • Must have a minimum of 8 characters.
  • Must contain at least one uppercase letter [A–Z] and one lowercase letter [a–z].
  • Must contain at least one digit [0–9].
  • Must contain at least one special character.
  • Must not end with a #.
  • Must not contain 'admin' and 'bmcuser'.
11

Save the certificates (custom_cacert.pem or public_cacert.pem) in the <working _directory>/commons/certs/ directory. 

Important: If you set the value of the parameters CUSTOM_CA_SIGNED_CERT_IN_USE to false and MONITOR to yes, you must name the public CA certificate file (full chain) as public_cacert.pem and copy it to the commons/certs directory; that is, commons/certs/public_cacert.pem.

 

12

Backup RSSO audit logs

If you have deployed ITOM 24.1 or ealier, you can backup the data related to RSSO audit log into MinIO.

  1. Ensure that you have run the Upgrade Configuration Utility to populate the configuration files.
  2.  Ensure that you have copied custom certificates into common/certs/custom_cacert.pem.
  3. Navigate to helix-on-prem-deployment-manager/utilities/migration/postgres 
  4. Run the ./export_rssoaudit_old.sh command.
    After sometime, you see the export-rssoaudit-old completed successfully message.
  5. Verify the data in Minio:
    1. Go to the Minio console, for example: minio.apps.ocp415.bmc.com.
    2. Login with your credentials.
    3. On the object browser, you see the rssoaudit on the table.

    4. Click the file and download the data, which you can view locally.

13

(Optional) Upgrade your container orchestration platform (Kubernetes and Openshift) to a supported version.

Important: If you are using Rancher on Kubernetes, you must upgrade Rancher and then upgrade Kubernetes.

14

Upgrade the NGINX Ingress Controller (nginx-ingress-controller) based on your Kubernetes and OpenShift versions. 

Important: You might experience downtime while upgrading the Nginx Ingress Controller.

15

Upgrade Helm to a supported version based on your Kubernetes and OpenShift versions. 

16Migrate data from PostgreSQL database to 17.xMigrating data from PostgreSQL database 15.x to 17.x

Where to go from here

If you have completed all the upgrade prerequisite tasks, proceed with the upgrade:

 

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