Broker 10.5 | webMethods Broker Documentation | webMethods Broker Client Java API Programmer's Guide | Using Broker Clients | Broker Connection Descriptors | Sharing Client State
Sharing Client State
Event Processing with Shared Client State
By-Publisher Event Ordering
Event Processing without Ordering
When is Sharing State Useful?
State Sharing Methods
Calling Sequence for Sharing Client State
webMethods Broker allows Broker clients in different applications to share the same client state. Sharing client state allows several Broker clients, possibly executing on different hosts, to handle events in a parallel, first-come, first-served basis. This provides both parallel processing and load balancing for event handling.
One use for state sharing is load balancing event flows. If you have an application that processes request events (the webMethods Broker dbAdapter is one example), you might want to have several instances of the application available to process these requests.
Broker clients sharing the same client state are treated as one Broker client with regard to the state they are sharing. Any changes to the event subscriptions or event queue, such as clearing the queue, will affect all of the clients sharing the state.