Network Deployment (Distributed operating systems), v8.0 > Reference > Sets
WebSphere MQ link sender channel [Settings]
This pane displays 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.
Service integration -> Buses -> bus_name -> [Topology] Messaging engines -> engine_name -> [Additional properties] WebSphere MQ links -> link_name -> [Additional Properties] Sender channel -> channel_name .
Configuration tab
These property values are preserved even if the runtime environment is stopped then restarted.
General Properties
WebSphere MQ link sender 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 information about choosing channel names, see the description of the Channel name (CHANNEL) 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.
If the previous channel is unknown, restart is delayed until the uncertainty is resolved.
Required No Data type String
Single Connection
Use Single connection for the gateway queue manager used to connect into the WebSphere MQ network.
Select Single Connection to specify the host name and port for one target queue manager. If we have a high availability configuration, with one or more failover gateway queue managers available in the WebSphere MQ network in addition to the target queue manager, select Multiple Connection Names List instead.
If you do not specify any host names, either as a single connection or in a list of multiple connections, 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 Radio button
Host name
The hostname or TCP/IP IP address for the gateway queue manager used to connect into the WebSphere MQ network.
This is the host name or IP address of the target queue manager in the WebSphere MQ network.
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
Required No Data type String
Port
The TCP/IP port number on which the gateway queue manager is listening for the WebSphere MQ link.
This is the port number on which the gateway queue manager is listening for the inbound communication requests.
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 65535 Default 1414
Multiple Connection Names List
Select Multiple Connection Names List if we have one or more failover gateway queue managers available in the WebSphere MQ network in addition to the target queue manager. If no failover gateway queue manager is available, you can select Single Connection instead.
If you do not specify any host names, either as a single connection or in a list of multiple connections, 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 Radio button
Connection Names List
List of hostnames or TCP/IP IP address for the gateway queue manager used to connect into the WebSphere MQ network.
Specify a list of host names, or IP addresses, and ports for the active and standby WebSphere MQ queue managers in a high availability configuration. You may also use this field to specify a single host name and port.
Specify the host names, or IP addresses, and ports in the format hostname1(nnnn),hostname2(nnnn) separating each pair with a comma. Specify IP addresses in IPv4 format.
If you specify a port alone as an entry in the list, WAS uses the default host name localhost with the port. If you specify a host name alone as an entry in the list, WAS uses the default port number 1414 with the host name. For example, a connection names list consisting of the values (1422),example.com is interpreted as localhost(1422),example.com(1414).
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
Required No Data type Custom
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 property 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 by using SSL. The SSL configuration used is taken from the default SSL repertoire for the application server being used to contact the queue manager. We can also choose to specify another outbound transport chain that we have defined separately on the TransportChannelService object of the application server used for WebSphere MQ interoperation.
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
Modified transport chains are visible only after a server restart.
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 an unacceptable amount of processing in constantly starting up the channel. A very large value (more than an hour) might 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.
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 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 connection name list is provided, during each retry the connections are tried in the order in which they are specified in the connection list until a connection is successfully established. If the count of remaining retries reaches zero, and the channel has not restarted, then the long retry mechanism is invoked.
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 999999999
Short retry interval
The number of seconds between attempts by the sender channel to restart after a communication or partner failure.
For more information about using retry mechanisms with WebSphere MQ, 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 999999999
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 connection name list is provided, during each retry the connections are tried in the order in which they are specified in the connection list until a connection is successfully established. 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 more information about about using retry mechanisms with WebSphere MQ, 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 Long 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 more information about using retry mechanisms with WebSphere MQ, 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 Long Range 0 through 999999999
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.
Dynamic updates to this property are effective on messaging engine restart or sender channel creation. Use the Runtime tab to check the current state.
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.
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.
General Properties
WebSphere MQ link sender channel name
The name of the sender channel for the WebSphere MQ link, used to send messages from the bus to WebSphere MQ.
See the description of this property for the Configuration tab.
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
If the previous channel is unknown, restart is delayed until the uncertainty is resolved.
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, 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.
Required No Data type String
I/P address
The TCP/IP IP address of the host on which the target queue manager runs.
Required No Data type String
Status
The runtime status of the sender channel.
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.
Host name
The hostname or TCP/IP IP address for the gateway queue manager used to connect into the WebSphere MQ network.
See the description of this property for the Configuration tab.
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
Port
The TCP/IP port number on which the gateway queue manager is listening for the WebSphere MQ link.
See the description of this property for the Configuration tab.
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
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. See the description of this property for the Configuration tab.
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
Modified transport chains are visible only after a server restart.
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.
See the description of this property for the Configuration tab.
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
Short retry count
The maximum number of times that the sender channel tries to restart after a communication or partner failure. If the connection name list is provided, during each retry the connections are tried in the order in which they are specified in the connection list until a connection is successfully established. If the count of remaining retries reaches zero, and the channel has not restarted, then the long retry mechanism is invoked.
See the description of this property for the Configuration tab.
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
Short retry interval
The number of seconds between attempts by the sender channel to restart after a communication or partner failure.
See the description of this property for the Configuration tab.
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
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 connection name list is provided, during each retry the connections are tried in the order in which they are specified in the connection list until a connection is successfully established. If the count of remaining retries reaches zero, and the channel has not restarted, then an error is logged and the channel is stopped.
See the description of this property for the Configuration tab.
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
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.
See the description of this property for the Configuration tab.
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
Batch size
The maximum number of messages that a batch can contain.
Required No Data type String
Channel start time
The time at which the channel was last started.
Required No Data type String
Channel start date
The date on which the channel was last started.
Required No Data type String
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 queue.
Required No Data type Integer
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. The default value is 999999999.
For more information about choosing the value for this property, see the description of the Sequence Number wrap (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
Maximum message length
The negotiated maximum message length, in bytes, that can be transmitted on the channel. This value is compared with the value from the partner WebSphere MQ receiver channel, and the maximum message length used is the lower of the two values.
Required No Data type Integer
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 drop-down 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.
Current LUWID
The current logical unit-of-work identifier for the message on the channel.
Indoubt channel problems are usually resolved automatically. Sequence number and logical unit of work ID (LUWID) records are kept to help resolve indoubt channel problems when communication has been re-established. For information resolving indoubt channels, see the Intercommunication section of the WebSphere MQ information center.
Required No Data type String
Current sequence number
The current sequence number for the message on the channel.
Indoubt channel problems are usually resolved automatically. Sequence number and logical unit of work ID (LUWID) records are kept to help resolve indoubt channel problems when communication has been re-established. For information resolving indoubt channels, see the Intercommunication section of the WebSphere MQ information center.
Required No Data type String
In doubt
Whether the message on the channel is in an indoubt state.
Problems with a channel that is in an indoubt state are usually resolved automatically. Sequence number and logical unit of work ID (LUWID) records are kept to help resolve problems with an indoubt channel when communication has been re-established. For information about resolving indoubt channels, see the Intercommunication section of the WebSphere MQ information center.
Required No Data type drop-down 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 indoubt 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 indoubt messages on the transmission queue and re-send them.
Required No Data type String
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 might have 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 String
Messages in current batch
The number of messages in the current batch on the channel.
Required No Data type String
Number of batches sent
The number of batches that have been sent on the channel.
Required No Data type String
Number of messages sent
The number of messages that have been sent on the channel.
Required No Data type String
Buffers sent
The number of message buffers sent.
Required No Data type String
Buffers received
The number of message buffers received.
Required No Data type String
Bytes sent
The number of bytes sent.
Required No Data type String
Bytes received
The number of bytes received.
Required No Data type String
Last message send time
The time at which the last message was sent on the channel.
Required No Data type String
Last message send date
The date on which the last message was sent on the channel.
Required No Data type String
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 String
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 String
Nonpersistent message speed
The class of service for nonpersistent messages on the sender channel.
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.
Additional Properties
Saved batch status
The runtime status of message batches for the sender channel of the WebSphere MQ link. We can choose to commit or roll back each batch.
View the status of a WebSphere MQ link and its sender and receiver channels
Set a WebSphere MQ link sender channel
Disable WebSphere MQ functionality in WAS
Related
WebSphere MQ library
Administrative console buttons
Administrative console preferences