Deploying BMC Helix IT Operations Management
Before you begin
- Download the deployment manager.
For more information, see Downloading-the-deployment-manager. - Download the BMC Helix IT Operations Management hotfixes:
- OnPrem v24.4.00.001 hotfix
- OnPrem v24.4.00.003 hotfix
For more information, see Downloading-the-deployment-manager.
- Perform all the steps listed in the Preparing-for-deployment topic.
- Make sure you update the operating system version of the controller machine.
For more information about supported operating system versions, see System-requirements.
To deploy BMC Helix IT Operations Management
- Log in to the controller or bastion machine from where the Kubernetes cluster is accessible.
Configure the properties in the helix-on-prem-deployment-manager/configs/infra.config and helix-on-prem-deployment-manager/configs/deployment.config files.
For more information, see Configuration-file-settings.You can also refer to the following topics for application-specific configurations:
To deploy BMC Helix ITOM, run the following command:
./deployment-manager.shThe deployment manager generates a new secret.config and secretkey.json files in the common/certs directory.
The secrets.txt file is deleted.
The deployment manager will now use the secret.config and secretkey.json files for deploying all products.
After the deployment is successful, you will get two emails:
- The first email will ask you to activate your BMC Helix Portal account.
It will contain the BMC Helix Portal URL and the user name, which is your service account name. - The second email will confirm that your License Account is activated.
To apply the hotfixes
| Perform the following steps to apply the hotfix.
|
If you are using NGINX Ingress Controller version 1.11.2, the Probable Cause Analysis (PCA) API failing issue is fixed in the OnPrem v24.4.00.003 hotfix, which addresses the DR0F3-18869 defect. | Perform the following steps to apply the hotfix.
|