A WebSphere MQ client link presents the messaging engine, and thereby the bus, as a WebSphere MQ queue manager to which WebSphere MQ clients can attach. This enables WebSphere Application Server Version 5 JMS clients to use messaging resources on the bus.
In the administrative console page, to view this page click bus_name engine_name link_name.
Configuration properties for this object. These property values are preserved even if the runtime environment is stopped then restarted. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.
The universal unique identifier assigned by the system to this WebSphere MQ client link for administrative purposes.
Required | No |
Data type | Text |
An optional description for the WebSphere MQ client link, for administrative purposes.
Required | No |
Data type | Text area |
The name of the channel for the WebSphere MQ client link, used to flow messages between WebSphere MQ clients and the bus.
The name of the WebSphere MQ server connection channel that this client link will use to represent itself to clients. It must exactly match the value specified by the client for a connection to be established. For WebSphere Application Server Version 5 , embedded JMS provider clients a value of "WAS.JMS.SVRCONN" must be specified. You should not define two MQ client links that share both channel name and queue manager name. However , it is possible to have client links with identical channel names if they specify different queue manager names.
.Required | Yes |
Data type | Text |
The queue manager name used to represent the bus as a WebSphere MQ queue manager to WebSphere MQ clients.
The WebSphere MQ link (by default, named Default.MQClientLink) for use by JMS applications on WebSphere Application Server Version 5 has the queue manager name WAS_nodeName_jmsserver. You should not use this name on any other WebSphere MQ link that is assigned to a messaging engine on the same node.
Required | Yes |
Data type | Text |
Whether or not this is the default queue manager for the WebSphere MQ clients.
If a client does not specify the name of the queue manager it wishes to connect to, it will be connected to an MQ client link with a matching channel name that has been marked as being the default, if one matching this criterion can be found.
Required | No |
Data type | Check box |
The maximum message length, in bytes, that can be transmitted on the channel for the WebSphere MQ client link.
Required | No |
Data type | Long |
Default | 4194304 |
Range | -2147483648 through 2147483647 |
The time, in seconds, to wait before checking that a client requesting an operation is still active.
If the sending channel has had a communication from the receiving channel within the batch heartbeat interval, the receiving channel is assumed to be still active, otherwise a "heartbeat" signal is sent to the receiving channel to check.
Required | No |
Data type | Integer |
Default | 300 |
Range | 0 through 999999 A value of 0 (zero) indicates that the heartbeat mechanism is not used. For considerations when choosing the number for the heartbeat interval, see the description of the Heartbeat Interval (HBINT) property in the WebSphere MQ Intercommunication book. |
Whether the WebSphere MQ client link is started or stopped when the associated messaging engine is first started. Until started, the MQ client link is unavailable.
Required | No |
Data type | Selection list |
Default | Started |
Range |
|
Runtime properties for this object. These properties directly affect the current runtime environment, but are not preserved when that environment is stopped. To preserve runtime property values, change the equivalent property values on the Configuration tab. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.
The run-time status of the WebSphere MQ client link.
Required | No |
Data type | Selection list |
Range |
|