WebSphere MQ client link [Settings]
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 WAS V5 JMS clients to use messaging resources on the bus.
To view this pane in the console...
Service integration > Buses > bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] WebSphere MQ client links > link_name .
Runtime tab
The Runtime tab shows 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.
General Properties
Status
The runtime status of the WebSphere MQ client link.
Required
No Data type
drop-down list Range
- Inactive
- The WebSphere MQ client link is ready and enabled to receive inbound connections from clients, but no client connections have yet been established.
- Stopped
- The WebSphere MQ client link is in a stopped state and cannot process any new requests for inbound connections from clients.
- Starting
- The WebSphere MQ client link has received an inbound connection from a client, and is in the process of starting this connection.
- Binding
- The WebSphere MQ client link is performing channel negotiation and is not yet ready to transfer messages.
- Running
- The WebSphere MQ client link has an active session with a client, and data can be flowing between the client and the WebSphere MQ client link.
- Stopping
- The WebSphere MQ client link, or a connection with that link, is in the process of being stopped.
- Multiple
- The WebSphere MQ client link has established sessions with several clients, and the sessions can be in different states: Starting, Running, Stopping, or Stopped.
Additional Properties
Client connections- The client connections that exist on the WebSphere MQ client link.
Configuration tab
The Configuration tab shows 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.
General Properties
Name
The name of the WebSphere MQ client link.
Required
Yes Data type
Text
UUID
The universal unique identifier assigned by the system to this WebSphere MQ client link for admin purposes.
Required
No Data type
Text
Description
An optional description for the WebSphere MQ client link, for admin purposes.
Required
No Data type
Text area
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.
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 V5 embedded messaging 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
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.
The WebSphere MQ client link for use by JMS applications on WAS V5.1 has the queue manager name WAS_nodeName_jmsserver. You should not use this name on any other WebSphere MQ client link that is assigned to a messaging engine on the same node.
Required
Yes Data type
Text
Default queue manager
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 is 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
Maximum message size
The maximum message length, in bytes, that can be transmitted using the WebSphere MQ client link.
Required
No Data type
Long Range
0 through 104857600
Heartbeat interval
The time, in seconds, to wait before checking that a client requesting an operation is still active. This heartbeat interval allows a sending channel to verify that the receiving channel is still active just before committing a batch of messages. If the receiving channel is not active, the batch can be backed out rather than becoming indoubt, as would otherwise be the case. By backing out the batch, the messages remain available for processing so they can, for example, be redirected to another channel.
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 Range
0 through 999999 A value of 0 (zero) indicates that the heartbeat mechanism is not used.
Initial state
Whether the WebSphere MQ client link is started or stopped when the associated messaging engine is first started. Until started, the WebSphere MQ client link is unavailable.
Required
No Data type
drop-down list Range
- Stopped
- When the associated messaging engine is started, the WebSphere MQ client link is in a stopped state and cannot process any new requests for inbound connections from clients.
- Started
- When the associated messaging engine is started, the WebSphere MQ client link is ready and enabled to receive inbound connections.
Additional Properties
Advanced properties- Advanced configurable properties, such as message reliability and broker queue names, for the WebSphere MQ client link.
Last updated Nov 10, 2010 8:23:07 PM CST