Configuring high availability for on-premises connectors

Setting up on-premises connectors in a high-availability deployment ensures that your connection with the automation tool is maintained in case of failure. Automation policies run even if a single connector instance is available and remediation actions are not impacted.

As an automation engineer, you configure the on-premises connector to connect with an automation tool supported by BMC Helix Intelligent Automation.

To achieve high-availability deployment, we recommend that you configure the connector on two hosts. In such a scenario, both connectors remain active. The process to configure any of the supported on-premises connectors is the same.

Single-server deployment

In a single-server deployment, a single instance of the on-premises connector is configured. If the connector fails, the automation policies created by using the connector also fail.

Non HA deployment_243.png

High-availability deployment

In a high-availability deployment, one more instance of an on-premises connector is configured on a separate host. If one of the connectors fails, the automation policies run by using the second instance. When you configure the connector on another host, the creds.json file and the credentials for the second connector should be the same.

HA deployment_243.png

To configure an on-premises connector for high availability

Before configuring a connector for high availability, make sure that you have one instance of the connector up and running.

On the host where the connector is configured and running, perform the following steps:
1. Navigate to the remote-restapi-plugin location and copy the entire folder.
2. Navigate to the following location and copy the ia_remote_plugins folder:
  OS
  Default location on host 1
  Microsoft Windows
  C:\ProgramData\BMC\ia_remote_plugins
  Linux
  /var/lib/bmc/ia_remote_plugins
On the second host, perform the following steps:
1. Paste the remote-restapi-plugin folder at the same location where it existed on the first host.
  For example, C:/remote-restapi-plugin.
2. Paste the ia_remote_plugins folder at the same location where it existed on the first host:
  OS
  Default location host 2
  Microsoft Windows
  C:\ProgramData\BMC\ia_remote_plugins
  Linux
  /var/lib/bmc/ia_remote_plugins
Run the following command to install and run the connector as a service:
- Microsoft Windows: install.bat install
- Linux: ./install.sh install
Verify whether the service is running successfully.
To verify the connector status, perform the following steps:
1. Log on to the BMC Helix Intelligent Automation console and click Connectors.
2. On the Configured Connectors page, click the (Info) icon to view the status.
  The status of both connectors is displayed. Expand the host to view the host name, the plugin's IP address, and the last poll time. Even if one connector is configured, the status of the connector is shown as Connected.
  This Plugin information helps diagnose the issue and restart the plugin in case of connection failure.

OS	Default location on host 1
Microsoft Windows	C:\ProgramData\BMC\ia_remote_plugins
Linux	/var/lib/bmc/ia_remote_plugins

OS	Default location host 2
Microsoft Windows	C:\ProgramData\BMC\ia_remote_plugins
Linux	/var/lib/bmc/ia_remote_plugins

Where to go from here

The steps to configure any of the supported on-premises connectors are the same. To configure on-premises connectors for high availability based on your requirements, see: