WebSphere WebSphere Application Server Express, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

WebSphere MQ link sender channel settings

The sender channel that sends messages to the gateway queue manager. The sender channel communicates with a WebSphere MQ receiver channel on the gateway queue manager, and converts service integration bus messages to MQ format messages.

In the administrative console page, to view this page click Service integration > Buses [Content Pane] > bus_name > [Additional Properties] Messaging engines > engine_name > [Additional Properties] WebSphere MQ links > link_name > [Additional Properties] Sender channels > channel_name.

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

Sender MQ channel name

The name of the sender channel for the WebSphere MQ link, used to send messages from the bus to WebSphere MQ.

This name must be the same as the name of the receiver channel on WebSphere MQ.

For considerations when choosing channel names, see the description of the Channel name (CHANNEL) property in the WebSphere MQ Intercommunication book.

Required No
Data type Text

Host name

The hostname or TCP/IP IP address for the gateway queue manager that is used to connect into the WebSphere MQ network.

Type the host name or IP address of the host on which the gateway queue manager runs.

If this field is blank, the gateway queue manager is assumed to be running on the same host as the messaging engine on which the WebSphere MQ link is defined.

Required No
Data type Text
Default Null

Port

The TCP/IP port number on which the gateway queue manager is listening for the WebSphere MQ link.

Required No
Data type Integer
Range 0 through 2147483647

Transport chain

The type of channel chain used for communication with the foreign bus.

This must be one of the outbound transport chains in the application server, to be used when establishing a network connection to a WebSphere MQ queue manager receiver channel.
By default, this field can take one of the following values:
OutboundBasicMQLink
Used to establish connections with WebSphere MQ queue manager receiver channels.
OutboundSecureMQLink
Used to establish connections with WebSphere MQ queue manager receiver channels that have been secured using SSL. The SSL configuration used is taken from the default SSL repertoire for the application server being used to contact the queue manager.

You can also choose to specify another outbound transport chain that you have defined separately on the TransportChannelService object of the application server used for WebSphere MQ interoperation.

Required Yes
Data type Custom

Disconnect interval

The time in seconds for which the sender channel waits for new messages to arrive on the transmission queue after sending a batch of messages. The channel disconnects after this interval, and must be restarted manually or by triggering.

The default value is a reasonable interval. Change this value only if you understand the implications for performance, and you need a different value for the requirements of the traffic flowing down your channels.

Performance is affected by the value specified for the disconnect interval. A very low value (a few seconds) can cause excessive overhead in constantly starting up the channel. A very large value (more than an hour) could mean that system resources are unnecessarily held up.

If you want your channels to be active only when there are messages for them to transmit, you should set the disconnect interval to a fairly low value. Note that the default setting is quite high and so is not recommended for channels where this level of control is required. Because it is difficult to interrupt the receiving channel, the most economical option is to have the channel automatically disconnect and reconnect as the workload demands. For most channels, the appropriate setting of the disconnect interval can be established heuristically.

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

A value of 0 (zero) means never disconnect; the channel waits indefinitely for messages.

Short retry count

The maximum number of times that the sender channel tries to restart after a communication or partner failure. If the count of remaining retries reaches zero, and the channel has not restarted, then the long retry mechanism is invoked.

Required No
Data type Integer
Default 10
Range 0 through 999999999

Short retry interval

The number of seconds between attempts by the sender channel to restart after a communication or partner failure.

For considerations about using retry mechanisms with WebSphere MQ, see the WebSphere MQ Intercommunication book.

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

Long retry count

The maximum number of times that the sender channel tries to restart after the short retry mechanism did not recover from a communication or partner failure. If the count of remaining retries reaches zero, and the channel has not restarted, then an error is logged and the channel is stopped.

For considerations about using retry mechanisms with WebSphere MQ, see the WebSphere MQ Intercommunication book.

Required No
Data type Long
Default 999999999
Range 0 through 999999999

Long retry interval

The number of seconds between attempts by the sender channel to restart after the short retry mechanism did not recover from a communication or partner failure.

For considerations about using retry mechanisms with WebSphere MQ, see the WebSphere MQ Intercommunication book.

Required No
Data type Long
Default 1200 seconds
Range 0 through 999999

Initial state

Whether the sender channel is started or stopped when the associated WebSphere MQ link is first started. Until started, the channel is unavailable.

Required No
Data type Selection 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

Queue manager

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.

Required No
Data type Text

I/P address

The TCP/IP IP address of the host on which the target queue manager runs.

Required No
Data type Text

Status

The run-time status of the sender channel.

Required No
Data type Selection 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.

Current LUWID

The current logical unit-of-work identifier for the message on the channel.

In-doubt channel problems are usually resolved automatically. Sequence number and LUWID records are kept to help resolve in-doubt channel problems when communication has been re-established. For information resolving in-doubt channels, see the WebSphere MQ Intercommunication book.

Required No
Data type Text

Current sequence number

The current sequence number for the message on the channel.

In-doubt channel problems are usually resolved automatically. Sequence number and LUWID records are kept to help resolve in-doubt channel problems when communication has been re-established. For information resolving in-doubt channels, see the WebSphere MQ Intercommunication book.

Required No
Data type Text

In doubt

Whether or not the message on the channel is in-doubt.

In-doubt channel problems are usually resolved automatically. Sequence number and LUWID records are kept to help resolve in-doubt channel problems when communication has been re-established. For information resolving in-doubt channels, see the WebSphere MQ Intercommunication book.

Required No
Data type Selection list
Range
True
The channel is in doubt about which messages have been committed by WebSphere MQ for the unit of work that it has sent.

False
The channel is not in doubt about which messages have been committed by WebSphere MQ.

Last LUWID

The last logical unit-of-work identifier for a message on the channel.

To determine the last-committed logical unit of work ID (LUWID) for the channel, compare this value to the last-committed LUWID for the receiving side of the channel.
  • If the two LUWIDs are the same, the receiving side has committed the unit of work that the sender considers to be in doubt. The sending side can now remove the in-doubt messages from the transmission queue and re-enable it.
  • If the two LUWIDs are different, the receiving side has not committed the unit of work that the sender considers to be in doubt. The sending side needs to retain the in-doubt messages on the transmission queue and re-send them.
Required No
Data type Text

Last sequence number

The last sequence number for a message on the channel.

WebSphere MQ channels cannot initialize successfully if the channel negotiation detects that the message sequence number is different at each end. You may need to reset this manually.

To be effective, the sequence number must be reset in both the sender and the receiver channel definitions. The starting sequence number is not negotiated when a channel starts up, nor is there a default provided.

Required No
Data type Text

Messages in current batch

The number of messages in the current batch on the channel.

Required No
Data type Text

Number of batches sent

The number of batches that have been sent on the channel.

Required No
Data type Text

Batch size

The maximum number of messages that a batch can contain.

Required No
Data type Text

Number of messages sent

The number of messages that have been sent on the channel.

Required No
Data type Text

Buffers sent

The number of message buffers sent.

Required No
Data type Text

Buffers received

The number of message buffers received.

Required No
Data type Text

Bytes sent

The number of bytes sent.

Required No
Data type Text

Bytes received

The number of bytes received.

Required No
Data type Text

Channel start time

The time at which the channel was last started.

Required No
Data type Text

Channel start date

The date on which the channel was last started.

Required No
Data type Text

Last message send time

The time at which the last message was sent on the channel.

Required No
Data type Text

Last message send date

The date on which the last message was sent on the channel.

Required No
Data type Text

Heartbeat interval

The negotiated 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.

Required No
Data type Text

Remaining short retry starts

The remaining number of short retry attempts that can be used to start the sender channel. If the count of remaining retries reaches zero, and the channel has not restarted, then the long retry mechanism is invoked.

Required No
Data type Text

Remaining long retry starts

The remaining number of long retry attempts that can be used to start the sender channel. If the count of remaining retries reaches zero, and the channel has not restarted, then an error is logged and the channel is stopped.

Required No
Data type Text

Maximum message length

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

Required No
Data type Text

Nonpersistent message speed

The class of service for nonpersistent messages on the sender channel.

Required No
Data type Selection 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.

Stop requested

Whether or not a manual stop request has been made for the sender channel.

To make a stop request, use the buttons provided on the WebSphere MQ link sender channel collection panel.
Required No
Data type Selection list
Range
True
A stop request has been made for the channel.

False
A manual stop request has not been made for the channel.

Additional properties

Saved batch status
The run-time status of message batches for the sender channel of the WebSphere MQ link. You can choose to commit or roll back each batch.

Reference topic

Terms of Use | Feedback

Last updated: 2 Aug 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.express.doc\sibresources\SIBMQLinkSenderChannel_DetailForm.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)