Deploying BMC Helix IT Operations Management

Before you begin

• Download the deployment manager and the hotfix itom-predeploy-hotfix-24.1.00.001-6.tar.gz.
  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.
• (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 key-value pairs: "envMap.env.SMTP_MAIL_FROM_ADDRESS": "__smtp_from_email__",
     Example: 

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

  4. Under the anomaly-service section, add the following key-value pairs: "containers.container1.tag": "6f35ee1d-3",
     Example: 
     

      "anomaly-service": {
                    "predeploy": {},
                    "deploy": {
                            "override_param": {
                                    "namespace": "__namespace__",
                                    "containers.container1.tag": "6f35ee1d-3",
                                    "registryhost": "__image_registry_host__",
                                    "imagePullSecrets.name": "__image_registry_secret__",
                                    "ingress.hostname": "__lb_host__",
                                    "ingress.annotations.kubernetes\\\\.io\\\\/ingress\\\\.class": "__ingress_class__",
                                    "containers.container1.org": "__image_registry_project__/__bhom_image_registry_org__:",
  5. Save the file. 

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:

   • Example-configuration-files-for-BMC-Helix-Operations-Management
   • Example-configuration-files-for-BMC-Helix-Intelligent-Automation
   • Example-configuration-files-for-BMC-Helix-Continuous-Optimization

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, along with the username, which is your service account name.
• The second email will confirm that your License Account has been activated.