Preparing for the on-premises gateway deployment

(For BMC Helix IT Operations Management (ITOM) on-premises users only)

Review the following capabilities supported by BMC Helix ITOM version 25.4 and later, and decide whether you want to upgrade BMC Helix ITOM:

• II Admin role to allow users to manage the BMC Helix Intelligent Integrations connectors and configurations, improving security and operational flexibility. In earlier versions, only the tenant administrators could perform these tasks. 
• A proxy service for communication between BMC Helix Intelligent Integrations and the BMC Helix ITOM object storage in high-availability deployments for improved reliability.

Important:
When you deploy the BMC Helix Intelligent Integrations services for the on-premises gateway during the BMC Helix ITOM on-premises deployment, services only for the listed capabilities are deployed. To access the full functionality of BMC Helix Intelligent Integrations, you must also deploy the on-premises gateway in a standalone environment. 

For information on deploying BMC Helix ITOM, see Deploying BMC Helix IT Operations Management

(For BMC Helix ITOM on-premises users only)

If you are using BMC Helix ITOM on-premises version 25.4 or later without additional capabilities or a version earlier than 25.4, and you want to enable authentication for the on-premises gateway, register the OAuth client.

Important: Deployment of the on-premises gateway without authentication is not supported in the Kubernetes or OpenShift clusters.

(For BMC Helix ITOM on-premises users only)

If you are using BMC Helix ITOM on-premises version 25.4 or later with additional capabilities, and you want to enable authentication for the on-premises gateway, perform the following tasks:

1. Obtain the SSL certificate (public key) from the BMC Helix platform deployment that the on-premises gateway is part of, and save it in a directory on the host where you want to deploy the on-premises gateway.
2. Set the SSL_CERT_FILE environment variable to the SSL certificate file path:
   export SSL_CERT_FILE=<PathtoSSLCertDir>/<certFileName>

Important: Deployment of the on-premises gateway without authentication is not supported in the Kubernetes or OpenShift clusters.

(For deployments in on-premises Kubernetes and OpenShift clusters)

Create a namespace.

Creating a namespace for the on-premises gateway deployment

(Optional, for deployments in on-premises Kubernetes and OpenShift clusters) 

You can configure the on-premises gateway for high availability either during the deployment or after the deployment. 

Determine the type of object storage you want to use if you want to configure the on-premises gateway for high availability during the deployment:

• BMC Helix object storage—The storage included with the current BMC Helix SaaS or BMC Helix ITOM deployment.
• Private object storage—A storage deployed and managed in your on-premises environment. You can use a standalone S3-compatible storage (for example, MinIO or an Amazon Simple Storage Service (S3)) available in your environment.