This describes how you delete a broker profile and all topic mappings
on a WebSphere MQ link, which forms a publish/subscribe bridge between WebSphere
Application Server and a WebSphere MQ network.
Before you begin
Before you start you need to:
- Know the names of the bus, messaging engine, and WebSphere MQ link which
has the broker profile(s) that you intend to delete.
- Consider informing the WebSphere MQ administrator that you are about to
delete the connection to the message broker(s) in the WebSphere MQ network.
Deleting a broker profile is a three-stage operation to ensure both
the WebSphere Application Server and the
WebSphere MQ network and its message brokers are synchronized after the deletion:
- Unsubscribe the topic mappings (see below).
- Once the Runtime view is empty, delete the broker profile.
- Restart the application server.
About this task
To delete a broker profile, use the administrative console to complete the following steps:
Procedure
- In the navigation pane, click bus_name link_name profile_name.
- Remove the subscriptions:
- Click the Runtime tab.
- Click Subscriptions.
- Click Unsubscribe to remove all the subscriptions
listed. When an unsubscribe command is sent to the message broker
in the WebSphere MQ network, the relevant topic mapping is put into an "in
doubt" state until the unsubscribe is confirmed when the topic mapping is
deleted. Once the unsubscribe is confirmed the topic mapping is no longer
shown in the runtime view. You may need to refresh the runtime view for all
subscriptions to be shown as removed.
- To delete the broker profile, return to the Publish/subscribe
broker profiles page.
- Select the check box next to the broker profile you wish to delete.
- Click Delete.
- Save your changes to the master configuration.
- If you plan to delete the WebSphere MQ link do
so now.
- Restart the application server.
What to do next
If, having unsubscribed the topic mappings on the broker profile,
you do not delete the broker profile on the associated WebSphere MQ link,
then the subscriptions will be recreated when the server is restarted (because
they are still present in the static configuration information for the WebSphere
MQ link). These subscriptions are unrelated to the original subscriptions
and this may lead to some messages in a publication flow being missing for
subscribers on the target side of the bridge. For example, any messages published
on an unsubscribed topic between the time the unsubscribe took place and the
application server was restarted will not be republished to the target side
of the WebSphere MQ link.