WebSphere MQ link [Settings]

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

To view this pane in the console, click the following path:

Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines > engine_name > [Additional Properties] WebSphere MQ links > [Content Pane] link_name.

For considerations when choosing settings, see the WebSphere MQ Intercommunication book.

Configuration tab

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 Text

UUID

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

Required No
Data type Text

Description

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

Required No
Data type Text area

Foreign bus name

The foreign bus to which this link connects.

If you do not see the bus that you expected to select, you need to set up a foreign bus for the WebSphere MQ link.
Required Yes
Data type drop-down list

Queue manager name

The name of the virtual queue manager associated with the messaging engine, and by which the messaging engine is known to a remote WebSphere MQ network.

The queue manager name must conform to the WebSphere MQ naming conventions; for example, the name must be a maximum of 48 characters.
Required Yes
Data type Text

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 considerations when choosing the number for batch size, see the description of the Batch size (BATCHSZ) property in the WebSphere MQ Intercommunication book.

Required No
Data type Integer
Default 50
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 partner and the actual maximum used is the lower of the two values.

For considerations when choosing the number for message size, see the description of the Maximum message length (MAXMSGL) property in the WebSphere MQ Intercommunication book.

Required No
Data type Integer
Default 4194304 bytes (4MB)
Range 0 through 104857600

0 indicates to use the largest value that the target queue manager will honour.

Heartbeat interval

The time, in seconds, between heartbeat flows passed from the sender channel across the WebSphere MQ link when there are no messages on the transmission queue.

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

For considerations when choosing the number for this property, see the WebSphere MQ Intercommunication book.

Required No
Data type Integer
Default 300 seconds
Range 0 through 999999

Sequence wrap

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

This is the highest number the message sequence number reaches before it restarts at 1.

For considerations when choosing the number for this property, see the WebSphere MQ Intercommunication book.

Required No
Data type Long
Default 999999999
Range 1 through 999999999

For considerations when choosing the number for this property, see the description of the Sequence Numberwrap (SEQWRAP) property in the WebSphere MQ Intercommunication book.

Nonpersistent message speed

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

Required No
Data type drop-down list
Default Fast
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.

Adoptable

Whether or not this WebSphere MQ link can be adopted by another messaging engine if the original hosting messaging engine is restarted or adopted on another machine.

If you select this option, the WebSphere MQ sender channels may reestablish a connection to this WebSphere MQ link in the event that a communications failure has occurred and the link has not yet detected the failure condition.

Required No
Data type Check box
Default Selected

Initial state

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

Required No
Data type drop-down list
Default Started
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.

Runtime tab

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 run-time 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.




Reference topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 11:08:29 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-mp&topic=SIBMQLink_DetailForm
File name: SIBMQLink_DetailForm.html