Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage messaging with the default messaging provider > Enable WAS v5.1 JMS usage of messaging resources in later versions of the product


Start and stop WebSphere MQ client connections

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 JMS application developed for WAS v5.1 that uses the connections.

We can start a WebSphere MQ client connection that is not running (has a runtime status of Inactive) or stop a client connection that 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 Start and stop 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 admin console to complete the following steps.


Procedure


Results

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.
Client connections [Collection]

+

Search Tips   |   Advanced Search