Introducing a non-invasive instance synchronization solution on webMethods

Instance Synchronization

Are you a webMethods administrator? How many Integration Server instances are you maintaining? How do you synchronize changing in a cluster, for example an extended setting?

I believe you usually have to make the change manually on all the nodes, and that's definitely boring and risky.

Cluster Dispatcher

I designed and built a tool Cluster Dispatcher to easily synchronize instance status. This is how it works. For specific service that might change instance status we will need to register it as a Service Dispatch task. When that specific service is invoked, Cluster Dispatcher would remote invoke the same service with the same inputs on other nodes. So whatever you did on one instance, you did for all. You could download this package form GitHub,https://github.com/dingago/HxClusterDispatcher. The code is verified on webMethods 9.9.

Features

Non-Invasive

You don't have to do any change for your service, or to invoke any service explicitly. It works if you register it as a Service Dispatch task.

Traceable

You could check the dispatching status by configuring logging service, so you know exactly what happened.

Two Dispatch Modes

Mode Lax will try to dispatch the service invocation on as many nodes as possible. Mode Strict will try to reverse the change if it's failed on any other nodes. 

Rollback

An optional rollback service is supported, which would be invoked on any successful nodes to reverse the change in mode Strict.

Self-Checking

Self-check if Cluster Dispatcher is configured correctly and ready to serve.

Management GUI Included

DSP pages are included to manage Cluster Dispatcher easily.