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.

(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:

For example,

What to go from here

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

• BMC Helix Operations Management documentation

• BMC Helix Intelligent Automation

• BMC Helix Continuous Optimization documentation