Integrations - APClient.bin communication failure

Using APClient.bin utility to inject events into an APAgent instance configured with non-default HTTP port values causes a communication failure.

Issue Details

Using APClient.bin utility to inject events into an APAgent instance configured with non-default HTTP port values causes a communication failure. This issue is caused when the APClient.bin utility is executed to communicate and map event data to an APAgent server instance configured with a non-default HTTP port. Example execution:

APClient.bin --map-data <domain> <arg1> <arg2> .... <argn>  

Impact:

Communication Failure between the APClient.bin utility and the APAgent. Command Line output:

<?xml version="1.0"?>  
 <transaction id="0">  
  <header>  
  <method>Agent</method>  
  <subclass>ERROR</subclass>  
  </header>  
  <data>  
    <errorcode>COMMUNICATIONS_FAILURE</errorcode>  
    <errortext>Failed to perform communication request.</errortext>  
    <errordetail>No server is listening at the remote address.</errordetail>  
  </data>  
 </transaction>  

Resolution:

When executing the APClient.bin utility, supply it with HTTP connection parameters:

APClient.bin --http-get http://localhost:<port>/  --map data <domain> <arg1> <arg2> .... <argn> 

NOTE: If the APClient.bin utility is not being called from the same machine where the APAgent is hosted, replace localhost with the IP Address or the hostname of the APAgent installation instance.

xMatters Reference

JDN-1198 Originally created by Don Clark

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk