The following figure shows a deployment of the server-requestor example with a "shared-state" Broker configuration (several server applications are shown in the figure). In a shared-state configuration, multiple clients share a single Broker message queue, with the Broker managing the cursor of the message queue relative to each of the clients.

In a configuration such as the one shown, a single server must process a complete topic from the requestor application, because a shared state configuration does not support the parts of a multipart message being processed by different servers. However, in this scenario, it is possible to realize the gain in efficiency from processing several different messages in parallel.

For more information about the Broker shared state feature, see Administering webMethods Broker.