Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Integration Server Administrator's Guide | Managing webMethods Messaging Triggers | Cluster Synchronization for webMethods Messaging Trigger Management | Monitoring Cluster Synchronization
 
Monitoring Cluster Synchronization
Integration Server Administrator provides a cluster view that you can use to see the trigger synchronization status across all the servers in the cluster. For each server listed in the watt.server.cluster.aliastList property, the cluster view indicates whether the other servers in the cluster (and its triggers) are in sync with current server. The cluster view is located on the Settings > Messaging > webMethods Messaging Trigger Management > Cluster View page.
Note:
The Cluster View page appears only if the current Integration Server belongs to a properly configured cluster and the server is configured to synchronize trigger changes across the cluster.
If a webMethods messaging trigger is not synchronized, the cluster view displays an error message that indicates how the trigger is out of sync with the trigger on the current server. For example, if document processing for a trigger is suspended locally, but active on another server in the cluster, the error message next to trigger name states "Processing State mismatch [local=suspended; remote=active]".
Integration Server considers a trigger on a remote server to be out of sync with the local trigger of the same name if either of the following is true:
*The triggers have different values for trigger queue capacity, refill level, or maximum execution threads.
*The triggers have different document retrieval or document processing states.
Note:
To log on to a remote server in the cluster, click the server alias in the Remote Server Alias column. When connecting, the remote server prompts you for user and password information. If you are connecting to the remote server via HTTPS and the HTTPS port requires certificates, you need to import a trusted certificate into the browser so that it can be presented at connection time. If the trusted certificates are not imported into the browser, when you try to connect to the remote server, you will receive a message informing you that the page is not available. For more information about client authentication and certificates, see Authenticating Clients.