Skip to Content

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 with BMC Helix Vulnerability Resolver and BMC HelixGPT​​​​​​
  • BMC Helix Log Analytics
  • BMC Helix Intelligent Automation
  • BMC Helix Developer Tools
  • BMC Helix Automation Console
  • BMC Helix Intelligent Integrations

    Important:

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

Hybrid deployments of BMC Helix Service Management and BMC Helix IT Operations Management are not supported. For example, you cannot deploy BMC Helix Service Management in an on-premises environment while deploying BMC Helix Operations Management and BMC Helix AIOps in a SaaS environment, as this setup might not function properly. Additionally, it is not possible to have one instance of BMC Helix Service Management running on-premises while another instance is deployed in a SaaS environment.

Before you begin

  • Download and extract the deployment manager and the hotfix itom-predeploy-hotfix-26.1.00.001-3.tar.gz.
    The 26.1.00.001 hotfix includes optimized sizing requirements.
    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
    Warning

    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.

     

Information

When the BMC Helix ITOM installer fails in between due to any reason like image pull back or timeout, then rerun of deployment manager starts deployment from the last infra or product.

Example: Failure in installation of a chart in AIOPS product causes failure in deployment. After reviewing and correcting the failure, say image pull issue, rerunning of deployment will skip infra services and other producs deployed prior to AIOPS and deployment start from AIOPS.

This does not mean rerun of deployment will start at the failed service.

 

 

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

BMC Helix IT Operations Management deployment 26.1