Configuring Integration Agent primary and secondary registration servers

March 21, 2023 01:25

Don Clark

If you have just finished setting up your Integration Agent, and you go ahead and run an iadmin.sh get status command, you'll probably get back something similar to the following:

xMatters Servers:

URL: http://localhost:8888/api/services/AlarmPointWebService
Connectivity status: PRIMARY_ACCEPTED
Last heartbeat attempt: Sep 30, 2015 8:26:18 PM

URL: http://localhost:8888/api/services/AlarmPointWebService
Connectivity status: UNKNOWN
Last heartbeat attempt: none

And now you're probably wondering what that means, and if there's an error you should be worried about...

The Integration Agent configuration allows you to specify a primary and secondary server that the Integration Agent can connect to. If the primary server becomes unavailable, the secondary server will accept any injected events for configured integrations.

The above response does not indicate an error because, in an On-Demand instance, the secondary server setting is not used. There's only one instance to which you can connect your Integration Agent. If you're hooking up your Integration Agent to a premises (i.e., version 5.1) deployment, you can configure the secondary server to point to the backup or alternate server.

But maybe you want to get rid of that annoying second part of the message so that your iadmin.sh get status command is less worrisome...

If so, open up the <IAHOME>/conf/IAConfig.xml file, and locate the following section:

<primary-servers>
 <!--
 | 0 or more URL elements that specify the primary location of each server's
 | RegisterIntegrationAgent Web Service. The URLs must begin with either http:// or https://
 | and cannot have a query or fragment component. The URLs must be resolvable from this IA.
 +-->
 <url>http://localhost:8888/api/services/AlarmPointWebService</url>
 </primary-servers>

<!--
 | These servers are assumed to be connected to the same database,
 | which can be different than the primary servers' database.
 +-->
 <secondary-servers>
 <!--
 | 0 or more URL elements that specify the secondary location of each Server's
 | RegisterIntegrationAgent Web Service. The URLs must begin with either http:// or https://
 | and cannot have a query or fragment component. The URLs must be resolvable from this IA.
 +-->
 <url>http://localhost:8888/api/services/AlarmPointWebService</url>
 </secondary-servers>

Comment out the URL block inside the secondary-servers tag so it looks something like this:

<secondary-servers>
 <!--
 | 0 or more URL elements that specify the secondary location of each Server's
 | RegisterIntegrationAgent Web Service. The URLs must begin with either http:// or https://
 | and cannot have a query or fragment component. The URLs must be resolvable from this IA.
 <url>http://localhost:8888/api/services/AlarmPointWebService</url>
 +-->
 </secondary-servers>

Comments