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

Before you begin

Download the deployment manager, the hotfix itom-drs-predeploy-hotfix-23.2.02.002-2, or the hotfix itom-predeploy-hotfix-23.2.02.002-6.
For more information, see Downloading-the-deployment-manager.

Perform all the steps listed in the Preparing-for-deployment topic.

To apply the hotfix

The following table lists the prerequisites to apply the hotfixes:

Supported Kubernetes versions

Supported Helm version

Hotfix

Description

1.23.x – 1.25.x

3.11

itom-drs-predeploy-hotfix-23.2.02.002-2

Download and apply the hotfix itom-drs-predeploy-hotfix-23.2.02.002-2 to prevent the certificate issue caused when OpenSSL fails to pull the client root certificate.

1.24.x – 1.26.x

3.12

itom-predeploy-hotfix-23.2.02.002-6

itom-predeploy-hotfix-23.2.02.002-6 is a cumulative hotfix.
Download and apply this hotfix if you want to use Kubernetes version 1.26 and
prevent the certificate issue caused when OpenSSL fails to pull the client root certificate.

  1. Back up the following files:
    • helix-on-prem-deployment-manager directory/deployment-manager.sh
    • commons/preinstall-checker.sh
    • helix-on-prem-deployment-manager directory/configs/infra.config
    • (Only if you are applying the hotfix itom-predeploy-hotfix-23.2.02.002-6) configs/helix-chart-version.config
  2. Copy the hotfix to your workspace directory.
  3. To extract the contents of the hotfix to the workspace directory, run the following command:
    • To extract the contents of the  itom-drs-predeploy-hotfix-23.2.02.002-2.tar.gz file to the workspace directory, run the following command:

      tar -xvf itom-drs-predeploy-hotfix-23.2.02.002-2.tar.gz
    • To extract the contents of the itom-predeploy-hotfix-23.2.02.002-6.tar.gz file to the workspace directory, run the following command:

      tar -xvf itom-predeploy-hotfix-23.2.02.002-6.tar.gz

      The deployment-manager.sh, preinstall-checker.sh and infra.config files are replaced.
      You can now run the deployment manager. 

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. Install the product by running 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.

How do I change the encryption or decryption password?

Perform these steps if you forget the encryption password or if you need to change it:

  1. Delete the common/certs/secret.config and common/certs/secretkey.json files.
  2. Create the secrets.txt file.
  3. Run the deployment manager again.
    Important
    If you do not delete the secret.config file and create a new secrets.txt file, the deployment manager deletes the new secrets.txt file and proceeds with the deployment. Therefore, make sure that you delete the secret.config and secretkey.json files.

 

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