Broker 10.5 | webMethods Broker Documentation | webMethods Broker Messaging Programmer's Guide | Coding Messaging Client Applications | JMS Request-Reply Application with a Message Selector | Application Configurations | Broker Territory Configuration
 
Broker Territory Configuration
The next configuration shows a variation of the server-requestor application with two Brokers joined in a territory, a configuration where multiple Brokers share information.
The requestor application connects to the primary Broker, in the Western region; however, there is a second server connected to a Broker in the Eastern region. Requests for information for customers in the Eastern region are routed via a message selector to the Broke server servicing that region.
For this type of configuration to work with the sample application, you would need to create a more realistic database setup than the in-memory database used in the chapter example. You would need databases for both the Eastern and Western regions, and the databases would share the same schemas.
For more information about Broker territories, see Administering webMethods Broker .