Upgrading BMC Helix IT Operations Management from version 24.3 to 25.1
Before you begin
Make sure you have performed all the steps listed in the Preparing for upgrade topic.
To upgrade BMC Helix IT Operations Management
Set the values of the following services to yes.
- _INFRA
- _PTPOSTGRES
- _KAFKA
- _REDIS
- _RSSO
- _VICTORIAMETRICS
- _ELASTICSEARCH
- _MINIO
For all the BMC Helix ITOM applications for which you are licensed, set the value to yes; for all other services, set the value to no.
For example, if you are only licensed to use BMC Helix Operations Management and BMC Helix Continuous Optimization:- To use BMC Helix Operations Management, set value of MONITOR to yes.
Optionally,- If you want to use AIOps, set AIOPS_SERVICES to yes.
- If you want to use Log Analytics, set INTELLI_INT_SERVICES to yes.
To use BMC Helix Continuous Optimization, set the value of OPTIMIZE to yes.
From the new working directory (working_directory), run the deployment manager to upgrade BMC Helix IT Operations Management:
./deployment-manager.shAfter the upgrade, you will get the following message:
Completed Helix On-prem Installation.
(Optional) To view the logs during the upgrade, run the following command:
tail -f logs/deployment.log- If you have deployed BMC Helix IT Operations Management in a multitenant environment, perform the steps to restore the smart-graph-tenant-config configmap and its content:
- Copy the contents from the smart-graph-tenant-config configmap file that you backed up before the upgrade.
To open the smart-graph-tenant-config configmap, run the command:
kubectl -n <namespace> edit cm smart-graph-tenant-config- Paste the contents that you copied from the backed-up smart-graph-tenant-config configmap file in the new smart-graph-tenant-config configmap and save it.
To restart the smart graph controller pod, run the following command:
kubectl rollout restart deploy/smart-graph-controller -n <namepsace>
Applying Hotfixes
BMC Helix IT Operations Management OnPrem v25.1.00 includes the mandatory hotfixes 25.1.00.004 and 25.1.00.002 that must be applied. For details and application steps, see Applying Hotfixes.
Where to go from here