Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage messaging with the default messaging provider > Interoperating with a WebSphere MQ network > Use WebSphere MQ links to connect a bus to a WebSphere MQ network > Administer an existing WebSphere MQ link
Stop a WebSphere MQ link
We can change the state of a WebSphere MQ link from "Started" or "Running" to "Stopped". When you stop a WebSphere MQ link, all communication with the target WebSphere MQ network is stopped for both point-to-point and publication and subscription. Messages waiting for transmission are held on the service integration bus, and the MQ sender channel cannot start. If there is a publish/subscribe bridge on the WebSphere MQ link, its operations are stopped.
Inform the WebSphere MQ administrator that you are about to stop this WebSphere MQ link.
To stop a WebSphere MQ link, use the admin console to complete the following steps. We can also stop either the sender or receiver channel on the WebSphere MQ link, while leaving the link itself running. See Stop the sender channel on a WebSphere MQ link, and Stop the receiver channel on a WebSphere MQ link.
Procedure
- In the navigation pane, click one of the following paths:
- Service integration -> Buses -> bus_name -> [Topology] Foreign bus connections -> foreign_bus_name -> [Related Items] WebSphere MQ links
- Service integration -> Buses -> bus_name -> [Topology] Messaging engines -> engine_name -> [Additional properties] WebSphere MQ links
- In the content pane, select the check box next to the WebSphere MQ link to stop.
- In the Stop mode list, select "Quiesce" or "Force".
- In the Target state list select "Inactive" or "Stopped".
- Click Stop.
Results
The resultant state of the WebSphere MQ link, its sender and receiver channels, and the WebSphere MQ sender channel that is connected to the WebSphere MQ link receiver channel, depends on the options you chose:
- Stop the WebSphere MQ link to target state INACTIVE causes the sender channel to go into state STANDBY and the receiver channel to go into state INACTIVE. The overall WebSphere MQ link status will be RUNNING.
- Stop the WebSphere MQ link to target state STOP causes the sender channel to go into state STOPPED and the receiver channel to go into state STOPPED. The overall WebSphere MQ link status will be STOPPED.
These are the final states that the sender, receiver and WebSphere MQ link transition into. If you specify a mode of QUIESCE for either of the two final states, the channels and link might not transition into their final states immediately. Instead they temporarily transition through other states that are required to reach their final state.
For more details about stopped states of the WebSphere MQ link, see States of the WebSphere MQ link and its channels.
What to do next
We can restart the WebSphere MQ link by selecting the link again and clicking Start.
If the WebSphere MQ link is started and the sender channel is in the stop state, it goes into the standby state. The sender channel goes into negotiation with the partner receiver channel if it is started from the standby state. The sender channel then moves into the running state if the negotiation successful, or into the retry state if the negotiation fails. If messages are present when the WebSphere MQ link is started, the sender channel automatically goes into negotiation with its partner receiver channel and then moves to the running or retry state.
When the WebSphere MQ link is stopped, and not in doubt, you can delete the WebSphere MQ link and any associated publish/subscribe broker profiles and topic mappings as described in Remove a foreign bus connection from a bus.