Deploying BMC Helix IT Operations Management

The deployment of BMC Helix IT Operations Management (BMC Helix ITOM) involves the deployment of BMC Helix Platform Common Services, and the applications.

Use the deployment manager script (infra.config and deployment.config) to deploy BMC Helix Platform Common Services, BMC Helix Logging, and any of the following applications into your Kubernetes cluster:

  • BMC Helix Operations Management
  • BMC Helix Continuous Optimization
  • BMC Helix AIOps
  • BMC Helix Log Analytics
  • BMC Helix Intelligent Automation
  • BMC Helix Developer Tools

    Based on your product license, you can install these applications either individually or in combination. 

Related topic

System-requirements

Preparing-for-deployment

License-entitlements

Troubleshooting

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

  1. Log in to the controller or bastion machine from where the Kubernetes cluster is accessible.

  2. 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:

  3. To deploy BMC Helix ITOM, run the following command:

    ./deployment-manager.sh

    Important

    The passwords that you entered in the commons/certs/secrets.txt file are encrypted. The deployment manager does not pause to ask for the encryption or decryption of a password. The deployment manager generates a random password to encrypt or decrypt all passwords added to the secrets.txt file.

    The 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

  • The zombie process generation issue on redis-haproxy-monitor pods and Kafka Zookeeper pods is fixed in the

    Some content is unavailable due to permissions.

     OnPrem v24.4.00.001 hotfix, which addresses the following issues:
    • DRRE3-7571
    • DRRE3-7638

Perform the following steps to apply the hotfix.

  1. If you are using a local repository for pulling images, then ensure that the local image repository has images mentioned in file all_images_24.4.txt:
    • containers.bmc.com/bmc/lp0lz:24400001-v103-ade-infra-clients-alpine
    • containers.bmc.com/bmc/lp0lz:24400001-v102-bitnami-zookeeper-3.9.1-alpine-jdk11
  2. Extract the hotfix-24.4.00.001-7-Post.tar.gz file to the 24.4.00 workspace folder.tar -xvf hotfix-24.4.00.001-7-Post.tar.gz

  3. Run the hf_script.sh hotfix script file providing the full path of the 24.4.00 deployment manager directory.

    bash hf_script.sh </path/to/directory/24.4.00>/helix-on-prem-deployment-manager

    For example: bash hf_script.sh /data/24.4.00/helix-on-prem-deployment-manager

If you are using NGINX Ingress Controller version 1.11.2, the Probable Cause Analysis (PCA) API failing issue is fixed in the 

Some content is unavailable due to permissions.

 OnPrem v24.4.00.003 hotfix, which addresses the DR0F3-18869 defect.

Perform the following steps to apply the hotfix.

  1. If you are using a local repository for pulling images, then add the following image to the local local all_images_24.4.txt image file:
    containers.bmc.com/bmc/la0cz:pca-api-service-7019013-2
  2. Extract the hotfix-24.4.00.003-1-Post.tar.gz file to the 24.4.00 workspace folder.tar -xvf hotfix-24.4.00.003-1-Post.tar.gz

  3. Run the hf_script.sh hotfix script file providing the full path of the 24.4.00 deployment manager directory.

    bash hf_script.sh </path/to/directory/24.4.00>/helix-on-prem-deployment-manager

    For example: bash hf_script.sh /data/24.4.00/helix-on-prem-deployment-manager

Important

  • This command creates a new directory named /data/24.4.00/helix-on-prem-deployment-manager_HF1.YYYYMMDDHHMMSS, which is a copy of deployment manager directory.
  • No changes are made to the earlier deployment manager directory that was passed as the parameter.

 

 

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