Cluster Synchronization at Run Time

At run time, Integration Server uses remote invokes to update the other members of a cluster with trigger management changes. If a remote invoke to a server fails or that server is not available at the time of the remote invoke, the cluster will be out of sync. Integration Server executing the remote invoke displays the following journal log messages to indicate the status of the cluster synchronization attempt.

If synchronization...	Expect this log message...
Succeeds	Integration Server Administrator displays the message: Settings changed successfully.
Succeeds for some servers, but fails for others	Integration Server Administrator displays the message: [ISS.0085.9203] Errors occurred while updating remote aliases (x of y updates failed). See server logs for more details. The server log displays the message for each member of the cluster that was not successfully updated: [ISS.0098.0107E] Error occurred during cluster invoke: Alias = remoteAliasName; Service = serviceName; Exception = exceptionName You can use the Integration Server Administrator to view and change cluster synchronization status for triggers.
Fails because the local update failed	Integration Server Administrator displays the message: [ISS.0085.9204] Local update failed: Exception providing reason for failure. (Note: The cluster synchronization will not run until all local errors are resolved.) If the trigger management change cannot be completed on the local Integration Server, cluster synchronization cannot occur. For example, if you suspend document retrieval for all triggers and one trigger is currently locked, the Integration Server can suspend document retrieval for every trigger except the locked one. Because document retrieval could not be completed locally, the Integration Server cannot synchronize the change with the rest of the cluster.
Fails because it is not configured	The server log displays the following message: [ISS.0033.0156W] Cluster invoke did not complete successfully. Cluster Synchronization feature is not configured. For more information about configuring cluster synchronization for triggers, see Configuring Cluster Synchronization.