Prepare to remove a foreign bus connection between a service integration bus and a WebSphere MQ network
Before you remove a foreign bus connection between a service integration bus and a WebSphere MQ network, drain as many messages as we can from the link transmitter queue, then manually move or delete any remaining messages.
You must know which foreign bus connection is being prepared for deletion. You should also inform the WebSphere MQ administrator the foreign bus connection is about to be deleted and therefore no longer paired with its WebSphere MQ gateway queue manager or message broker in the WebSphere MQ network. When a foreign bus connection is deleted from the configuration, the next time the hosting messaging engine for a link transmitter is started, it deletes all its messages or moves them to the exception destination. To avoid messages being unintentionally deleted or moved to the exception destination, drain as many messages as possible from the link transmitter queue. Then, before you delete the link configuration, either move any remaining messages to an exception destination or delete them.
If there are publish/subscribe broker profiles defined, you should remove the subscriptions.
- Start the dmgr console.
- Optional: If there are publish/subscribe broker profiles defined on any of the links for this foreign bus connection, remove the subscriptions.
Complete the following substeps for each broker profile:
- Navigate to Service integration -> Buses -> bus_name -> [Topology] Foreign bus connections -> foreign_bus_name -> [Related Items] WebSphere MQ links -> link_name -> [Additional Properties] Publish/subscribe broker profiles -> profile
- 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 indoubt state until the unsubscribe is confirmed when the topic mapping is deleted. After the unsubscribe is confirmed, the topic mapping is no longer shown in the runtime view. You might have to refresh the runtime view for all subscriptions to be shown as removed.
- Prevent new messages from being produced for this foreign bus connection.
- Navigate to Service integration -> Buses -> bus_name -> [Topology] Foreign bus connections -> foreign_bus_name
- Under General properties, clear the Send Allowed check box.
- Click Apply to save the configuration.
- Determine when there are no more messages queued, then stop the link to the foreign bus in a controlled manner.
- Under Related Items, click WebSphere MQ links to display the list of links for this bus.
- Click the Refresh icon of Status to refresh the view of the current outbound messages.
- When there are no current outbound messages, select the check box next to the appropriate link and then select a Stop mode of "Quiesce".
- Select a Target state of "Stopped" so the link can only be started again by administrator action.
- When the status of the link turns to red, the link to the foreign bus has no remaining messages and is stopped.
- The foreign bus can continue to produce messages after the foreign bus connection on the local bus has been deleted. Because the foreign bus is a WebSphere MQ network, refer to the WebSphere MQ Intercommunication guide for details about the safe deletion of channels at Manage WebSphere MQ channels.
- Save changes to the master configuration.
Results
We have removed the subscriptions from any publish/subscribe brokers on the link. We have drained as many messages as possible from the link transmitter queue, and either moved any remaining messages from the transmission queues to an exception destination or deleted them.
You are now ready to remove the foreign bus connection.
Related
Manage pending acknowledgement messages on a deleted WebSphere MQ link
Manage messages in a link transmission queue for a connection to a WebSphere MQ network
Administer an existing WebSphere MQ link
Delete a WebSphere MQ link publish/subscribe broker profile