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.
To view this page in the console, click the following path:
.
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.
The name of the sender channel for the WebSphere MQ link, used to send messages from the bus to 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 |
Use Single connection for the gateway queue manager that is used to connect into the WebSphere 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 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 |
The hostname or TCP/IP IP address for the gateway queue manager that is used to connect into 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 |
The TCP/IP port number on which the gateway queue manager is listening for the 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 | Integer |
Range | 0 through 65535 |
Default | 1414 |
Select Multiple Connection Names List if you 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 |
List of hostnames or TCP/IP IP address for the gateway queue manager that is used to connect into the WebSphere 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.
Required | No |
Data type | Custom |
The type of channel chain used for communication with the foreign bus.
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.
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 |
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. |
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
|
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
|
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
|
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
|
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 |
|
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.
The name of the sender channel for the WebSphere MQ link, used to send messages from the bus to WebSphere MQ.
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.
Required | No |
Data type | String |
The TCP/IP IP address of the host on which the target queue manager runs.
Required | No |
Data type | String |
The runtime status of the sender channel.
Required | No |
Data type | drop-down list |
Range |
|
The hostname or TCP/IP IP address for the gateway queue manager that is used to connect into the WebSphere MQ network.
The TCP/IP port number on which the gateway queue manager is listening for the WebSphere MQ link.
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.
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 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.
The number of seconds between attempts by the sender channel to restart after a communication or partner failure.
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.
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.
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 |
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 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
|
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 |
Whether or not a manual stop request has been made for the sender channel.
Required | No |
Data type | drop-down list |
Range |
|
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 |
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 |
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 |
|
The last logical unit-of-work identifier for a message on the channel.
Required | No |
Data type | String |
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 |
The number of messages in the current batch on the channel.
Required | No |
Data type | String |
The number of batches that have been sent on the channel.
Required | No |
Data type | String |
The number of messages that have been sent on the channel.
Required | No |
Data type | String |
The time at which the last message was sent on the channel.
Required | No |
Data type | String |
The date on which the last message was sent on the channel.
Required | No |
Data type | String |
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 |
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 |
The class of service for nonpersistent messages on the sender channel.
Required | No |
Data type | drop-down list |
Range |
|