WebSphere MQ client links [Collection]

WebSphere MQ client links [Collection]

A WebSphere MQ client link presents the messaging engine, and therefore the bus, as a WebSphere MQ queue manager to which WebSphere MQ clients can attach. This behavior enables WebSphere Application Server Version 5 JMS clients to use messaging resources on the bus.

To view this page in the console, click the following path:
Service integration -> Buses -> bus_name -> [Topology] Messaging engines -> engine_name -> [Additional Properties] WebSphere MQ client links.
To browse or change the properties of a listed item, select its name in the list.
To act on one or more of the listed items, select the check boxes next to the names of the items to act on, use the buttons provided.
To change which entries are listed, or to change the level of detail that is displayed for those entries, use the Filter settings.
If WebSphere MQ functionality has been disabled at any scope, an informational message indicating that WebSphere MQ has been disabled is displayed. In a single server environment this informational message is only displayed when the server is restarted after WebSphere MQ functionality has been disabled. In a network deployment environment the informational message is displayed immediately. For more information see Disable WebSphere MQ functionality in WebSphere Application Server.

Name

The name of the WebSphere MQ client link.

Description

An optional description for the WebSphere MQ client link, for administrative purposes.

MQ channel name

The name of the channel for the WebSphere MQ client link, used to flow messages between WebSphere MQ clients and the bus.

Queue manager name

The name of the WebSphere MQ queue manager on which the WebSphere MQ sender channel, that is connected to this MQ link receiver channel connection instance, is running.

Default queue manager

Whether or not this is the default queue manager for the WebSphere MQ clients.

Status

The runtime status of the WebSphere MQ client link.

Buttons

Information Value
New Create a new administrative object of this type.
Delete Delete the selected items.
Start Start selected items.
This button does not work if the selected WebSphere MQ client link is running on an application server on which WebSphere MQ has been disabled. For more information see Disable WebSphere MQ functionality in WebSphere Application Server.

information about the target states and the corresponding stop mode behavior. There are two target states such as inactive and stopped, and there are two stop modes such as quiesce and force. The two rows in the table represent the two target states, and the two columns
Target state Quiesce stop mode Force stop mode
Inactive The sender channel becomes inactive either when it has finished processing its current batch, or when it reaches a heartbeat interval. The sender channel immediately becomes inactive.
Stopped The sender channel becomes stopped either when it has finished processing its current batch, or when it reaches a heartbeat interval. The sender channel immediately becomes stopped.

This button does not work if the selected WebSphere MQ client link is running on an application server on which WebSphere MQ has been disabled. For more information see Disable WebSphere MQ functionality in WebSphere Application Server.

Related information:

Administrative console buttons
Administrative console preference settings Reference topic

Information	Value
New	Create a new administrative object of this type.
Delete	Delete the selected items.
Start	Start selected items. This button does not work if the selected WebSphere MQ client link is running on an application server on which WebSphere MQ has been disabled. For more information see Disable WebSphere MQ functionality in WebSphere Application Server.

Target state	Quiesce stop mode	Force stop mode
Inactive	The sender channel becomes inactive either when it has finished processing its current batch, or when it reaches a heartbeat interval.	The sender channel immediately becomes inactive.
Stopped	The sender channel becomes stopped either when it has finished processing its current batch, or when it reaches a heartbeat interval.	The sender channel immediately becomes stopped.