Preparing for the on-premises gateway deployment


Perform the following tasks before deploying the BMC Helix Intelligent Integrations on-premises gateway:

TaskActionReference
1. Review system requirements.System requirements for the on-premises gateway
2.Obtain the container images and utility files for deploying the on-premises gateway:
Docker and podman containersObtaining container images and utility files for deployment on Docker and Podman containers
On-premises Kubernetes and OpenShift clustersObtaining container images and utility files for deployment in on-premises Kubernetes and OpenShift clusters
3.

(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 can 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 during the BMC Helix ITOM on-premises deployment, services only for the listed capabilities are deployed. For information on deploying BMC Helix ITOM, see Deploying BMC Helix IT Operations Management.
    To access the full functionality of BMC Helix Intelligent Integrations, you must also deploy BMC Helix Intelligent Integrations in a standalone environment (referred to as on-premises gateway).

-
4.

(For BMC Helix IT Operations Management (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.

Setting up authentication for the on-premises gateway.
5.

(For BMC Helix IT Operations Management (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>
-
4.(For deployments on on-premises Kubernetes and OpenShift clusters) Create a namespace.

Where to go from here

 

 

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

BMC Helix Intelligent Integrations 26.1