WebSphere MQ link [Settings]

The WebSphere® MQ link connects the messaging engine as a queue manager to WebSphere MQ, providing a bridge between the bus and a WebSphere MQ network.

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 links -> link_name

For more information about choosing settings, see the Intercommunication section of the WebSphere MQ information center.

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 Disabling WebSphere MQ functionality in WebSphere Application Server.

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 link, used for administrative purposes.

Required Yes
Data type String

UUID

The universal unique identifier assigned by the system to this WebSphere MQ link for administrative purposes.

Required No
Data type String

Description

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

Dynamic updates to this property are effective immediately.

Required No
Data type Text area

Foreign bus connection name

The foreign bus to which this link connects.

If you do not see the foreign bus connection name that you expected to see, you must create a new foreign bus connection.
Required Yes
Data type drop-down list

Local messaging engine

The local messaging engine that this WebSphere MQ link is hosted on.

Required Yes
Data type drop-down list

Virtual queue manager name

The virtual queue manager name by which the local bus is to be known to a WebSphere MQ network. It is generally recommended that you set the virtual queue manager name to match the name of the local bus. As WebSphere MQ queue manager names can be no longer than 48 characters, you must ensure that the length of the local bus name does not exceed 48 characters.

The bus appears to WebSphere MQ as if it is a WebSphere MQ queue manager or queue-sharing group. This field gives the queue manager name that WebSphere MQ uses to address the virtual queue manager represented by this bus. Any value that you specify must meet the following criteria:
  • It must contain between 1 and 48 characters.
  • It must conform to the WebSphere MQ queue naming rules (see the Rules for naming WebSphere MQ objects topic in the WebSphere MQ information center).
Required Yes
Data type String

Batch size

The maximum number of messages that can be sent through a channel before taking a checkpoint.

The batch size does not affect the way the sender and receiver channels for this link transfer messages; messages are always transferred individually, but are committed or backed out as a batch.

For information about choosing the batch size, see the description of the Batch size (BATCHSZ) property in the Intercommunication section of the WebSphere MQ information center.

Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.

Required No
Data type Integer
Range 1 through 9999

Maximum message size

The maximum message length, in bytes, that can be transmitted on any channel for the WebSphere MQ link. This is compared with the value for the corresponding partner WebSphere MQ channel and the actual maximum used is the lower of the two values.

For more information about choosing a value for the maximum message size, see the description of the Maximum message length (MAXMSGL) property in the Intercommunication section of the WebSphere MQ information center.

Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.

Required No
Data type Integer
Range 0 through 104857600

Heartbeat interval

The negotiated time, in seconds, between heartbeat flows passed from the WebSphere MQ link sender channel to the WebSphere MQ receiver channel when there are no messages on the transmission point being served by the WebSphere MQ link sender channel.

Heartbeats give the receiving channel the opportunity to quiesce the channel connection.

For more information about choosing a value for this property, see the Intercommunication section of the WebSphere MQ information center.

Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.

Required No
Data type Integer
Range 0 through 999999

Sequence wrap

The value at which message sequence numbers wrap to start again at 1.

For more information about choosing a value for this property, see the description of the Sequence Numberwrap (SEQWRAP) property in the Intercommunication section of the WebSphere MQ information center.

Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.

Required No
Data type Long
Range 100 through 999999999

Adoptable

Whether or not a running instance of a WebSphere MQ link receiver channel (associated with this MQ link) should be adopted or not. In the event of a communications failure, it is possible for a running instance of a WebSphere MQ link receiver channel to be left waiting for messages. When communication is re-established, and the partner WebSphere MQ sender channel next attempts to establish a session with the WebSphere MQ link receiver channel, the request will fail as there is already a running instance of the WebSphere MQ link receiver channel that believes it is in session with the partner WebSphere MQ sender channel. You can overcome this problem by selecting this option, which causes the already running instance of the WebSphere MQ link receiver channel to be stopped and a new instance to be started.

Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.

Required No
Data type Boolean

Exception destination

The destination for an inbound message when the WebSphere MQ link cannot deliver the message to its target bus destination, or to the exception destination that is configured for that target destination, or when the target destination does not exist.

Select a radio button as required to configure the exception destination that this WebSphere MQ link uses:
  • Select None to specify that the WebSphere MQ link does not use an exception destination. Undeliverable messages are not rerouted to an exception destination and can block the processing of other messages waiting for delivery through that link to the same bus. This option can be used to preserve message ordering.
  • Select System to use the default exception destination. Messages that cannot be delivered to the bus destination are rerouted to the system default exception destination for the messaging engine that this link is assigned to: _SYSTEM.Exception.Destinationmessaging_engine_name.
  • Select Specify and enter an exception destination to use the exception destination specified here. If the WebSphere MQ link cannot use this exception destination, it uses the system exception destination.
Required No
Data type Custom
Default System

Initial state

Whether the WebSphere MQ link is started or stopped when the hosting messaging engine is first started. Until it is started, the WebSphere MQ link is unavailable.

Dynamic updates to this property are effective when the messaging engine restarts.

Required No
Data type drop-down list
Range
Stopped
When the associated messaging engine is started, the WebSphere MQ link is in a stopped state and cannot communicate with the WebSphere MQ network.

Started
When the associated messaging engine is started, the WebSphere MQ link is started automatically and is enabled for communication with the WebSphere MQ network.

Nonpersistent message speed

The class of service for nonpersistent messages on channels of this WebSphere MQ link.

Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.

Required No
Data type drop-down list
Range
Fast
Nonpersistent messages can be lost if there is a transmission failure or if the channel stops when the messages are in transit.

Normal
Nonpersistent messages are not lost if there is a transmission failure or if the channel stops when the messages are in transit.

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 link.

Required No
Data type drop-down list
Range
Inactive
The WebSphere MQ link is ready and enabled to create connections, but no connections have yet been established.

Starting
The WebSphere MQ link has received a connection request, and is in the process of starting this connection.

Binding
The WebSphere MQ link is performing channel negotiation and is not yet ready to transfer messages.

Initializing
The WebSphere MQ link is initializing the session for a connection and is not yet ready to transfer messages.

Retrying
The WebSphere MQ link is retrying a failed connection.

Standby
The channel is being used for standby purposes. Messages can be transferred only when the channel is active.

Running
The WebSphere MQ link has an active session with WebSphere MQ, and data can be flowing between WebSphere MQ and the WebSphere MQ link.

Stopping
The WebSphere MQ link, or a connection with that link, is in the process of being stopped.

Paused
The channel is waiting for the message-retry interval to finish.

Stopped
The WebSphere MQ link is in a stopped state and cannot process any new requests for connections.

Multiple
The WebSphere MQ link has established several sessions with WebSphere MQ, and the sessions can be in different states: Starting, Running, Stopping, or Stopped.




Related concepts
Related reference


Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 3:08:41 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-zos&topic=SIBMQLink_DetailForm
File name: SIBMQLink_DetailForm.html