Performing the post deployment procedures


After the BMC Helix IT Operations Management deployment is complete, perform the following tasks:

  • Activate your BMC Helix IT Operations Management account. 
  • Import users or groups created by using an external identity provider (IdP).
  • Increase the log ingestion limit for your tenants if you are using BMC Helix Log Analytics.


To activate the BMC Helix IT Operations Management account

After the BMC Helix IT Operations Management deployment is complete, as a tenant administrator, you are the first user who logs on to BMC Helix IT Operations Management . Perform the following steps:  

  1. Set the tenant administrator password:
    1. From the email that you received, click the activation link. 
      The activation link is valid for 72 hours.
    2. Log on to the product by using the tenant administrator user name and the product URL.
  2. On your product tile, click Launch to start using the product.


To import users or groups created by using an external IdP

For instructions about importing users or groups created by using an external IdP into BMC Helix Portal, see the External IdP user access section in User identities.


(Optional) To update the SMTP details

If you want to change the SMTP details; for example, host, port, password, or username, perform the following steps:

  1. Update the SMTP ConfigMap:
    1. To edit the SMTP ConfigMap on a cluster, run the following command:

      kubectl edit cm smtp-credentials -n <mamespace>
    2. Update the required SMTP details; for example, SMTP_HOST or SMTP_PORT:

      apiVersion: v1
      data:
      SMTP_AUTH: "true"
      SMTP_HOST: mailhost.bmc.com
      SMTP_PORT: "25"
      kind: ConfigMap
    3. Save the file.

  2. Update the SMTP Secrets:
    1. To edit the SMTP secrets file, run the following command:

      kubectl edit secret smtp-credentials -n <namespace>

      The SMTP secrets file is displayed, as shown in the following code block:

      apiVersion: v1
      data:
      SMTP_PASSWORD: IiI=
      SMTP_USERNAME: BMC
      kind: Secret
    2. You can change the username, password, and other details in the secrets file. 
      To change the username or password, you must encode it into the Base64 format and then add it to the secrets file.
      • To encode the username in Base64 format, run the following command:

        echo <username> | base64

        Copy the encoded username that gets generated. 

      • To encode the password in Base64 format, run the following command:

        echo <password> | base64

        Copy the encoded password that gets generated. 

    1. Add the encoded username and password to the secrets file and save it.


(For BMC Helix Log Analytics) To change the log ingestion limit of your tenants

By default,  BMC Helix Log Analyticscan ingest a maximum of 1 GB logs on a tenant. As a tenant administrator, you can change the log ingestion limit by performing the following steps:

  1. From the controller box of your Kubernetes cluster, run the following command to get the name of the pod that runs the log-mgmt service:

    kubectl get pod -n <namespace> | grep log-mgmt-service
  2. Run the following command to increase the log ingestion limit:

    kubectl exec -it <log management pod name> -- bash -c "curl --location --request PUT 'http://log-mgmt-service:8093/logs-service/ingestion/control/api/v1.0/metadata/<tennant name>?idType=name' --header 'Content-Type: application/json' --data '{\"log_limit\" : <log ingestion limit>}'"

    For example, run the following command to increase the log limit to 2 GB:

    kubectl exec -it log-mgmt-service-67b7c65fdb-76nwc -- bash -c "curl --location --request PUT 'http://log-mgmt-service:8093/logs-service/ingestion/control/api/v1.0/metadata/acme?idType=name' --header 'Content-Type: application/json' --data '{\"log_limit\" : 2}'"

(For BMC Helix Log Analytics ) To disable log ingestion limit

Run the following command as a root user from a CLI service pod to disable the daily ingestion limit:

kubectl exec -it <cli-service pod> -- bash -c "./tcc confutil -s LogIngestionService -o edit -k enable.tenant.log.limit -v false"

For example,

kubectl exec -it cli-service-554489d6b4-69zk7 -- bash -c "./tcc confutil -s LogIngestionService -o edit -k enable.tenant.log.limit -v false"

Important

For any changes beyond the sizing category log limit, make sure that you make corresponding changes to the storage requirements.
For information about the sizing category log limit, see Sizing-and-scalability-considerations.

What to go from here

For information about using the following products, see the appropriate documentation links:




 

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