Specifying the Integration Service path

The following options can be used to initiate the PATROL Agent connection to the Integration Service:

• Command line arguments (example: -integrationservice tcp:houperfms318:3183)
• Pconfig variables (example: "/AgentSetup/integration/integrationServices" = {REPLACE="tcp:houperfms318:3183"},)
• Environment variables (example: set INTEGRATIONSERVICES=tcp:houperfms318:3183)

You can specify multiple Integration Service strings by using comma as a separator between the Integration Service strings. If the PATROL Agent fails to connect to the first Integration Service, then it uses the next one.

You can use the following pconfig variables, to control the behavior of the PATROL Agent - Integration Service connection:

• /AgentSetup/integration/integrationMaxNumRetries
• /AgentSetup/integration/integrationRetryPeriod
• /AgentSetup/integration/integrationConnectTimeout
• /AgentSetup/integration/publishHostName

For more information about these variables, see Integration-variables.

Integration Service precedence

The PATROL Agent can be told to which Integration Service to connect using three different methods: command line argument, configuration variable, and environment variable. If you use more than one method to specify the Integration Service connections, then the PATROL Agent uses the Integration Service connection methods in the following order:

1. Command line argument
2. Configuration variable
3. Environment variable

When a value is undefined, the next value is tried. When a value is defined but has no valid Integration Service in the list (example unparseable syntax or unresolvable hostname), the next value is not tried.