Use this task to start or stop client connections on a WebSphere
MQ client link, to stop message flows between the default messaging provider
and the Version 5 JMS application using the connections.
Why and when to perform this task
You can start a WebSphere MQ client connection that is not running
(has a runtime status of Inactive) or stop a client connectionthat is running (has a runtime status of Started). Alternatively, you can
start or stop all client connections on the WebSphere MQ client link, as described
in Starting and stopping WebSphere MQ client links.
When stopping a client
connection, you can choose whether to force the client connection to stop
immediately or after any messages currently on its client connections have
been processed. Client connections are always stopped to an inactive state.
To
start or stop one or more WebSphere MQ client connections, use the administrative console to complete the following steps.
- Display the WebSphere MQ client connections collection page. Click [Content Pane] [Additional Properties] .
- Select the check box next to the name of each client connection
that you want to start or stop.
- Click the appropriate button:
Start |
Click this button to start selected items. |
Stop |
Click this button to stop a selected WebSphere MQ client connection.
You must first have selected the connection to be stopped.You can choose
the mode of stop action, but connections are always stopped to an inactive
state: - Stop mode:
- Force
- Stop the connection immediately.
- Quiesce
- Stop the connection after any messages currently on the connection have
been processed.
- Target state:
- Inactive
- Stop the link to an inactive state. If an application tries to use the
link, the link is started again.
|
The status of the client connection changes and a message stating
that the connection has started or stopped is displayed at the top the page.