IBM 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 IBM MQ receiver channel on the gateway queue manager, and converts service integration bus messages to MQ format messages.
To view this page in the console, click the following path:
.
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
IBM MQ link sender channel name
The name of the sender channel for the IBM MQ link, used to send messages from the bus to IBM MQ.
For information about choosing channel names, see the description of the Channel name (CHANNEL) property in the Intercommunication section of the IBM 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.
Information | Value |
---|---|
Required | No |
Data type | String |
Single Connection
Use Single connection for the gateway queue manager that is used to connect into the IBM MQ network.
Select Single Connection to specify the host name and port for one target queue manager. If you have a high availability configuration, with one or more failover gateway queue managers available in the IBM 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 IBM MQ link is defined.
Information | Value |
---|---|
Required | No |
Data type | Radio button |
Host name
The hostname or TCP/IP IP address for the gateway queue manager that is used to connect into the IBM MQ network.
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
Information | Value |
---|---|
Required | No |
Data type | String |
Port
The TCP/IP port number on which the gateway queue manager is listening for the IBM MQ link.
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
Information | Value |
---|---|
Required | No |
Data type | Integer |
Range | 0 through 65535 |
Default | 1414 |
Multiple Connection Names List
Select Multiple Connection Names List if you have one or more failover gateway queue managers available in the IBM 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 IBM MQ link is defined.
Information | Value |
---|---|
Required | No |
Data type | Radio button |
Connection Names List
List of hostnames or TCP/IP IP address for the gateway queue manager that is used to connect into the IBM MQ network.
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, WebSphere® Application Server uses the default host name localhost with the port. If you specify a host name alone as an entry in the list, WebSphere Application Server 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.
Information | Value |
---|---|
Required | No |
Data type | Custom |
Transport chain
The type of channel chain used for communication with the foreign bus.
- OutboundBasicMQLink
- Used to establish connections with IBM MQ queue manager receiver channels.
- OutboundSecureMQLink
- Used to establish connections with IBM 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.
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 IBM 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.
Information | Value |
---|---|
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.
Information | Value |
---|---|
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.
Information | Value |
---|---|
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 IBM MQ, see the Intercommunication section of the IBM MQ information center.
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
Information | Value |
---|---|
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 IBM MQ, see the Intercommunication section of the IBM MQ information center.
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
Information | Value |
---|---|
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 IBM MQ, see the Intercommunication section of the IBM MQ information center.
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
Information | Value |
---|---|
Required | No |
Data type | Long |
Range | 0 through 999999999 |
Initial state
Whether the sender channel is started or stopped when the associated IBM 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.
Information | Value |
---|---|
Required | No |
Data type | drop-down list |
Range |
|
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
IBM MQ link sender channel name
The name of the sender channel for the IBM MQ link, used to send messages from the bus to IBM MQ.
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 IBM MQ network. It is generally recommended that you set the virtual queue manager name to match the name of the local bus. As IBM 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.
Information | Value |
---|---|
Required | No |
Data type | String |
I/P address
The TCP/IP IP address of the host on which the target queue manager runs.
Information | Value |
---|---|
Required | No |
Data type | String |
Status
The runtime status of the sender channel.
Information | Value |
---|---|
Required | No |
Data type | drop-down list |
Range |
|
Host name
The hostname or TCP/IP IP address for the gateway queue manager that is used to connect into the IBM MQ network.
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 IBM MQ link.
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.
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.
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.
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.
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.
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.
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.
Information | Value |
---|---|
Required | No |
Data type | String |
Channel start time
The time at which the channel was last started.
Information | Value |
---|---|
Required | No |
Data type | String |
Channel start date
The date on which the channel was last started.
Information | Value |
---|---|
Required | No |
Data type | String |
Heartbeat interval
The negotiated time, in seconds, between heartbeat flows passed from the IBM MQ link sender channel to the IBM MQ receiver channel when there are no messages on the transmission queue.
Information | Value |
---|---|
Required | No |
Data type | Integer |
Sequence wrap
The value at which message sequence numbers wrap to start again at 1.
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 IBM MQ information center.
Dynamic updates to this property are effective when the channel restarts. Use the Runtime tab to check the current state.
Information | Value |
---|---|
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 IBM MQ receiver channel, and the maximum message length used is the lower of the two values.
Information | Value |
---|---|
Required | No |
Data type | Integer |
Stop requested
Whether or not a manual stop request has been made for the sender channel.
Information | Value |
---|---|
Required | No |
Data type | drop-down list |
Range |
|
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 IBM MQ information center.
Information | Value |
---|---|
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 IBM MQ information center.
Information | Value |
---|---|
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 IBM MQ information center.
Information | Value |
---|---|
Required | No |
Data type | drop-down list |
Range |
|
Last LUWID
The last logical unit-of-work identifier for a message on 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.
Information | Value |
---|---|
Required | No |
Data type | String |
Last sequence number
The last sequence number for a message on the channel.
IBM 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.
Information | Value |
---|---|
Required | No |
Data type | String |
Messages in current batch
The number of messages in the current batch on the channel.
Information | Value |
---|---|
Required | No |
Data type | String |
Number of batches sent
The number of batches that have been sent on the channel.
Information | Value |
---|---|
Required | No |
Data type | String |
Number of messages sent
The number of messages that have been sent on the channel.
Information | Value |
---|---|
Required | No |
Data type | String |
Buffers sent
The number of message buffers sent.
Information | Value |
---|---|
Required | No |
Data type | String |
Buffers received
The number of message buffers received.
Information | Value |
---|---|
Required | No |
Data type | String |
Bytes sent
The number of bytes sent.
Information | Value |
---|---|
Required | No |
Data type | String |
Bytes received
The number of bytes received.
Information | Value |
---|---|
Required | No |
Data type | String |
Last message send time
The time at which the last message was sent on the channel.
Information | Value |
---|---|
Required | No |
Data type | String |
Last message send date
The date on which the last message was sent on the channel.
Information | Value |
---|---|
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.
Information | Value |
---|---|
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.
Information | Value |
---|---|
Required | No |
Data type | String |
Nonpersistent message speed
The class of service for nonpersistent messages on the sender channel.
Information | Value |
---|---|
Required | No |
Data type | drop-down list |
Range |
|
Additional Properties
- Saved batch status
- The runtime status of message batches for the sender channel of the IBM MQ link. You can choose to commit or roll back each batch.