WebSphere Message Brokers
File: af02010_
Writer: John Morris-Smith

Concept topic

This build: July 31, 2007 21:29:13

Publish/subscribe topology deployment

Topology deployment is required only when using publish/subscribe. It informs each broker in the domain of the brokers with which it can share publications and subscriptions.

You can deploy a topology configuration in two ways:

Whatever type of deployment you perform, the Configuration Manager attempts to subscribe to the broker's status messages if it is the first deployment to the broker. However only a complete topology deployment initiates a further subscription.

Complete topology deployment

You can deploy a complete topology. Deploying a complete topology:

When to use
  • If the Configuration Manager is not correctly reporting whether it is in a stopped or started state.
  • If you have moved a Configuration Manager from one queue manager to another.
  • If a broker's publish/subscribe function has become inconsistent. An example of inconsistency would be if one broker is able to share publications with a second broker, but not the other way round.
When not to use
  • If you are adding brokers to the domain and you are not using publish/subscribe. That is, if you are not connecting brokers together so that they can share publications and subscriptions.
  • If you are adding execution groups to a broker.
  • If you have changed the publish/subscribe network. In this case, deploy a delta topology, if possible, so that you deploy only to those brokers affected by the changes you have made.
  • If you have removed a broker from the domain.

Delta topology deployment

Deploying a delta topology sends updated publish/subscribe network information to any broker with a publish/subscribe configuration that the Configuration Manager determines not to be current.

When to use
  • If you have modified a publish/subscribe network.
  • If you are using the workbench to remove a broker from the domain, the Configuration Manager automatically requests the broker component to stop message flows that are running and to tidy up any resources in use. If this operation, you can again request the broker to tidy up. Deploying a delta topology is the most convenient way to deploy only to those brokers affected by the topology changes.
When not to use
  • If you are adding brokers to the domain and you are not using publish/subscribe. That is, if you are not connecting brokers together so that they can share publications and subscriptions.
  • If you are adding or removing execution groups.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:29:13

af02010_ This topic's URL is: