BMC Helix Client Gateway connectivity

BMC requires that you use the BMC Helix Client Gateway, a non-VPN solution, to securely connect to your BMC Helix services when using certain integration methods. You must install a small client at your site to facilitate this connection.

For FedRAMP Impact Level 4 customers in the United States, your connection is via the Government NIPRNet, instead of through the internet.

Reminder:

BMC Helix Client Gateway is a prerequisite to ITSM customers, including BMC Helix ITSM, BMC Helix Digital Workplace, BMC Helix Knowledge Management by ComAround, BMC Helix Innovation Suite Apps (Business Workflows, Virtual Agent, Communication Service Providers, Multi-Cloud Broker, etc.). If you have a subscription with BMC Helix Operations Management, BMC Helix Discovery, BMC Helix Continuous Optimization and other ITOM services, BMC Helix Client Gateway does not apply to your subscription.

To review which integration types require use of the BMC Client Gateway, see Integrations.

This topic provides the following information:

Getting started

You will need to configure the BMC Helix Client Gateway if you are performing any of the following activities:

Using BMC Developer Studio for customization development
Using the LDAP protocol, commonly used for people data loads
Integrating to/from third-party systems that do not communicate via HTTPS

Start by downloading the BMC Helix Client Gateway Installation Guide and the BMC Helix Client Gateway request form. The installation guide provides you with step-by-step instructions for downloading and installing the gateway software on your network. The input form is where you will document your inbound integration points coming from your premises so that BMC can complete the configuration file that we need to finalize the setup. BMC will also provide you with the Kaazing license file. Once BMC has provided you with these two files and you have completed the client software installation, we will work with you to perform a connectivity test.

You may request a separate gateway for each of your environments if they are on separate networks, or you may use just one gateway for all environments. You may also configure the gateway client on your premises in a highly available configuration if desired. Work with your internal network team to configure the primary and failover servers.

Support for transporting TCP connections using WebSocket technology

Cloud to on-premises integrations can pose a substantial challenge when the integration architecture requires the use of a low-level network connection. This connection, over the TCP protocol, normally requires a full site-to-site VPN connection between a customer and the BMC service locations. The BMC Helix Client Gateway solves this challenge by transporting TCP connections using internet-friendly WebSocket technology.

Support for secure bidirectional data flows

With BMC Helix Client Gateway, BMC delivers sophisticated server-to-server integrations, avoiding the complexity, cost, and time penalties associated with VPN architectures. The resulting deployment handles bidirectional data flows in a secure, SSL-encrypted connection. Even for those connections that are logically initiated from the BMC data center, the Helix Client Gateway architecture allows the transport layer to be physically initiated from the on-premises end toward BMC. This approach remains firewall friendly (no special firewall rules are required at the customer end), and all traffic transits the public internet over HTTPS using TLSv1.2 and TLSv1.3. The connections from the Helix Client Gateway can traverse proxies and firewalls without special rules or opened ports.

Diagram of sample BMC Discovery to BMC Helix ITSM integration

For example, a customer may have the following separate integration requirements:

LDAP pull of employee data for population in BMC Helix ITSM
BMC Discovery-BMC Atrium Configuration Management Database (CMDB) integration for asset discovery

22.2 BMC Helix Discovery

22.2 and later versions of BMC Discovery can use a REST API to sync with CMDB outside of BMC Helix Client Gateway.

The LDAP connection is logically initiated from BMC toward the on-premises LDAP environment. To build this integration using VPN, a site-to-site VPN tunnel is used, often with network address translation (NAT) on both sides, and direct dependencies are created on the network addresses used. The BMC Discovery connection is initiated from on-premises, but it also utilizes a VPN to carry the low-level AR System API traffic.

The BMC Helix Client Gateway handles both requirements with ease. BMC Helix services maintain a server gateway to receive requests in each BMC service location; you simply deploy the BMC Helix Client Gateway client on a server in your environment. The gateway connects to the server gateway using HTTPS, and when connected, allows bidirectional traffic flows.

Unpublished Web services

In the event you have an integration that calls an unpublished web API, you may require the traffic to route through the BMC Client Gateway. If you require SSL certificates to enable an encrypted connection, you must provide these certificates to BMC (one is required for each environment). The customer remains responsible for obtaining and renewing these certificates, as well as managing any re-direction configuration on their network. List any related requirements on the BMC Helix Client Gateway request form, and provide the certificates to BMC via a change request. BMC SaaS Operations will then assist you with certificate loading and testing.

Support for development and disaster recovery

Often during the development of a new integration, it is necessary to connect an on-premises application to any of the BMC Helix application environments (development/tailoring, QA, or production). The customer might also have test, sandbox, or development systems similarly for the on-premises applications. The BMC Helix Client Gateway simplifies connection of these various environments. You can:

change the application endpoint on the on-premises side without involving BMC.
maintain multiple gateways connecting to each of the BMC service locations from the same location.

For disaster recovery scenarios, the Helix Client Gateway architecture fails over to alternate BMC data centers just like any other web traffic. In the event of a disaster situation, BMC re-routes the published hostnames (URLs) by modifying DNS entries, re-targeting traffic from existing on-premises gateways to the alternate (backup) locations. This is accomplished without the need to redeploy or reconfigure the gateway.

BMC Helix Client Gateway installation and configuration

The BMC Helix Client Gateway has the following requirements:

A Windows or Linux server with 4 CPUs and 16 GB of memory (virtualized deployments are acceptable)
Provide 50 GB disk space dedicated to BMC Helix Client Gateway
Network connectivity to the internet on standard HTTPS (TCP port 443)
Network connectivity to the on-premises applications and servers used for integration

BMC will assist you with the setup and provide you with a pre-built configuration file and instructions. You will receive a unique private gateway hostname (URL) for connecting to each BMC service facility.

The following table shows the ports that are configured by default for BMC Helix Client Gateway.

Ports used by BMC Client Gateway	Description
46000	The BMC Helix Client Gateway listens at this port for TCP traffic from client applications (for example, BMC Discovery, BMC Developer Studio, BMC TrueSight, and Pentaho Spoon client) and proxies it to the Helix development environment through a WebSocket connection.
47000	The BMC Helix Client Gateway listens at this port for TCP traffic from client applications (for example, BMC Discovery and BMC TrueSight) and proxies it to the Helix QA environment through a WebSocket connection.
48000	The BMC Helix Client Gateway listens in this port for TCP traffic from client applications (for example, BMC Discovery and BMC TrueSight) and proxies it to the Helix production environment through a WebSocket connection.
8000	This port is used by the BMC Helix Client Gateway for the management console. BMC uses this port to monitor the gateway's health that resides on the customer's premises.
443	This is the outbound port used by the BMC Helix Client Gateway to connect to the Helix services' endpoint.

For LDAP authentication, you specify the port and the LDAP server name in the BMC Helix Client Gateway. The default port is TCP 389.

Ports open to the internet from the agent must be TCP 443. You must ensure that any proxy servers or firewalls allow outbound connections on this port. If a proxy is used to bypass the traffic towards BMC, you must disable authentication.

After the BMC Helix Client Gateway installation finishes, you should see a message in the Installation Summary window for the installer, stating that the installation has been completed successfully. You can also verify that the BMC Helix Client Gateway has been installed correctly by:

Checking the services and ensuring that the BMC WebSocket Gateway – JMS Edition 4.0 service is running.

Reviewing the error.log file (in the Log directory in which BMC Helix Client Gateway is installed) for any error messages.

The BMC SaaS Operations team is available for technical support and assistance with the install.

How to add a proxy to the BMC Helix Client Gateway configuration

Open My computer properties.
Go to Advanced System settings.
Select the Environment Variables option.
Click System variables > New.

The New System Variable dialog box is displayed.
Add the following values in the fields:
- Windows:
  - Variable name: GATEWAY_OPTS
  - Variable value: -Xmx1024m -Dhttp.proxyHost=Hostname -Dhttp.proxyPort=Port
    Example:
    -Xmx1024m -Dhttp.proxyHost=10.10.10.10 -Dhttp.proxyPort=8080
    Where
    proxyHost is the hostname or IP
    proxyPort is the port number
- Linux:
  1. Edit kwic.start from bin directory.
  2. Add proxy setting after the following line in kwic.start:
    # The following line is used by KWIC. Do not remove.
    GATEWAY_OPTS="$GATEWAY_OPTS -DGATEWAY_CONFIG=$GW_HOME/conf/kwic-config.xml -Dcom.kaazing.kwic.logging=on" -Xmx1024m -Dhttp.proxyHost=10.10.10.10 -Dhttp.proxyPort=8080
Apply these settings and restart the Kaazing service.
Important
- Proxies with authentication are not supported by the BMC Helix Client Gateway.
- Usage of a wildcard, for example, *.foo.com is not supported by the BMC Helix Client Gateway and the appropriate method is to use IP address/IP addresses.
- BMC Helix Client gateway supports only point to point connectivity. Any integrations with redirects are not supported.