Skip to Content
Important This documentation space contains information about the on-premises version of Automation Console. If you are using the SaaS version of Automation Console, see BMC Helix Automation Console.

 

Deploying TrueSight Automation Console

Error

BMC has removed the capability to deploy TrueSight Automation Console on Kubernetes clusters starting with the 24.3 release cycle. The recommended deployment option is Deployment-by-using-Stack-Manager.

BMC will continue to support existing customers who have deployed on Kubernetes clusters.

BMC is working on an alternate method to deploy TrueSight Automation Console on Kubernetes clusters. Place a watch on this space to learn about it when released.

Information
Important

You can use different components and combinations to deploy TrueSight Automation Console on Kubernetes. The documentation, however, mentions the configurations used by BMC to certify the deployment. There are many combinations of components and options available in the market, but this documentation does not cover them all.


Use the BMC Deployment Manager script to deploy TrueSight Automation Console into your Kubernetes cluster: 

Related topic

System-requirements-for-the-Kubernetes-deployment

Preparing-for-deployment

Preparing-for-BMC-Helix-logging

Troubleshooting


Before you begin


Warning

Important

Only the root user is supported for deployment.

  1. Create a namespace.

    Expand to see the steps:

    1. Run the following command. The namespace must be a DNS-1123 label. That is, it must consist of lowercase alphanumeric characters or '-', and must start and end with an alphanumeric character.

      kubectl create ns <namespace>
    2. Verify that nothing is installed in the namespace in which you plan to deploy the product. Perform the following steps:

      1. Run the following command:

        kubectl get all -n <namespace_created_earlier_in_this_procedure>

      2. Make sure that the following message is displayed:

        No resources found.
    Information
    For EFK logging

    Create a namespace called bmc-helix-logging by using the following command:

    kubectl create ns bmc-helix-logging

    The Elasticsearch, FluentD, and Kibana services are installed in this namespace. These services are required to access logs from the pods that are running on BMC Helix Platform.

  2. Configure the ingress controller.

    Expand to see the steps:

    1. Identify the configmap name by running the following command:

      kubectl get all -n <ingress_nginx_namespace>

    2. Change the configmap name to use the configmap in your environment by running the following command:

      kubectl edit cm <ingress_nginx_configmap> -n  <ingress_nginx_namespace>

      data:
        enable-underscores-in-headers: "true"
        proxy-body-size: 250m
        server-name-hash-bucket-size: "1024"
        ssl-redirect: "false"
        use-forwarded-headers: "true"
       worker-processes: "40"
      Warning

      Note

      The configurations shown above are mandatory. Apart from these, you can retain any other configurations as per your requirement.


To deploy TrueSight Automation Console

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

  2. From the EPD, select TSAC-DEPLOYMENT-MANAGER-<release_version>.zip and click Download.
    The file will be downloaded.

  3. Perform the following steps:

    1. Unzip the file by running the following command
    2. unzip TSAC-DEPLOYMENT-MANAGER-24.3.00.zip

      After you unzip the file, the following folder is created -  tsac-deployment-manager


  4. Configure the properties in the  tsac-deployment-manager/config/infra.config and  tsac-deployment-manager/config/deployment.config and  tsac-deployment-manager/config/endpoint.config files.
    For more information, see the following topic:

  5. To install the product, run the following command:

    ./deployment-manager.sh

  6. When prompted for password, enter the expected password on console. All the passwords are stored in secrets. User need to enter password for following parameters on the run time when the deployment manager script is triggered.

    1. Harbor registry password
    2. Postgres database password
    3. TSSA Service user password
    4. TSNA Service user password
    5. Harbor registry password for logging purpose

After the installation, you can see the Elasticsearch, Fluentd, and Kibana pods in the bmc-helix-logging namespace. You can access Kibana with the following URL:

http://<masternodeio>:5601/ 

All installation logs are located in the following directory:

tsac-deployment-manager/logs

To configure the timeout setting

By default, a session is terminated automatically if the logged-in user remains idle for 15 minutes. To increase the timeout interval, an administrator must configure the timeout setting.

For instructions, see Configuring-the-timeout-setting 

 

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

TrueSight Automation Console 24.3