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

TroubleshootingThe BMC Helix Operations Management documentation

Before you begin

  • Download the deployment manager.
    For more information, see Downloading-the-deployment-manager.
  • Perform all the steps listed in the Preparing-for-deployment topic.
  • (For BMC Helix Operations Management only) To make sure the notification policy sends email notifications, perform the following steps:
    1. Go to helix-on-prem-deployment-manager/products/monitor.
    2. Open the monitor.json file.

    3. Under the notification-service section, add the following name-value pair: 
      "envMap.env.SMTP_MAIL_FROM_ADDRESS": "__smtp_from_email__",For example: 

      "notification-service": {
      "predeploy": {},
      "deploy": {
      "override_param": {
      "namespace": "__namespace__",
      "registryhost": "__image_registry_host__",                                 
                     "envMap.env.SMTP_MAIL_FROM_ADDRESS": "__smtp_from_email__",

    4. Save the file. 

      Important

      After performing the steps do not apply the workaround for the issue DRTOM-30211. 

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*