Broker 10.5 | webMethods Broker Documentation | webMethods Broker Client Java API Programmer's Guide | Load Balancing and Failover for Publish Operations | Understanding Clustering | BrokerClusterPublishers | Monitoring Territory Activity
 
Monitoring Territory Activity
BrokerClusterPublisher always maintains a Broker client connection belonging to the system-defined client group "eventLog" for monitoring purposes. This client is used to discover Brokers in a territory at connection time and to detect territory changes such as Brokers leaving or joining that territory. There can be only one such monitoring client for a given BrokerClusterPublisher solution in the territory at any point of time. This is also referred to as Cluster Monitor Client. Cluster Monitor subscribes to territory change activity events and acts on them when a change occurs. For example, when a Broker leaves the territory and a Broker client connection to that Broker in the Broker cluster publisher pool exists, the cluster monitor will initiate an operation to remove the Broker client connection to that Broker from the pool. Similarly when a Broker joins the territory, the cluster monitor will initiate an operation to create and add a Broker client connection to the newly joining Broker in to the Broker cluster publisher pool.