WebSphere Message Brokers
File: aq18630_
Writer: Terry Cowling Task topic This build: July 31, 2007 21:35:42
Deleting brokers
If you have a mixed broker network, you must take particular care
to maintain the integrity of the network if you need to remove
or delete a broker from the network:
When you issue the mqsideletebroker command to delete a WebSphere Message Broker broker,
the WebSphere MQPublish/Subscribe brokers that are neighbors of
this WebSphere Message Broker broker are not automatically
informed of its deletion. Remove the WebSphere Message Broker broker
from the network using the clear commands mqsiclearmqpubsub (at the WebSphere Message Broker broker)
and clrmqbrk (at its WebSphere MQPublish/Subscribe neighbors)
before you delete it.
If you delete a WebSphere Message Broker broker
before you remove it from the network, and it has a parent WebSphere MQPublish/Subscribe broker,
the parent broker continues to attempt to send publication and subscription
messages to it. You can correct this behavior by issuing the clrmqbrk command
at the parent. For example, if you issue:
mqsideletebroker -m WBRK_CHILD_BROKER
while
the WebSphere Message Broker broker is still known to its
parent WebSphere MQPublish/Subscribe broker, you can then issue
the command
When you issue the dltmqbrk command to delete
an WebSphere MQPublish/Subscribe broker that is a child of a WebSphere Message Broker broker, the WebSphere Message Broker broker
receives notification of the deletion.
Therefore you do not
have to issue the mqsiclearmqpubsub command
to remove knowledge of the deleted child at the WebSphere Message Broker parent
broker.
For example, if you want to delete the child
broker MQPS_CHILD_BROKER you must issue the following single command:
dltmqbrk -m MQPS_CHILD_BROKER
You are prevented from deleting a WebSphere MQPublish/Subscribe broker
that is a parent of any broker; the dltmqbrk command fails.