Using remote Integration Servers in a Stateful or Stateless Cluster
An Integration Server can be configured to connect to a remote server for a number of reasons, including:
Allow clients to run services on other
Integration Servers using the
pub.remote:invoke service and the
pub.remote.gd:* services.
Connect publisher and subscriber
Integration Servers to each other for the purpose of package replication.
Facilitate the process of presenting different certificates to different
Integration Servers.
If you want to specify a backup server in case the remote server is not available, specify that backup server as the retry server on the remote server's alias definition.
In a stateful cluster, use the $clusterRetry parameter that is passed to the pub.remote:invoke service to control what happens when an Integration Server tries to connect to the remote server in a stateful cluster. If you want the Integration Server to first try other servers in the cluster when the remote server is not available, and then go to the retry server if no cluster servers are available, set $clusterRetry to true. If you do not want the Integration Server to first try other servers in the cluster but rather to go directly to the retry server, set the parameter to false. For more information about remote servers, see For more information about the pub.remote:invoke service, see the
Stateless clusters do not support the $clusterRetry parameter; in this scenario, the Integration Server will automatically connect to the retry server.