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 pane in the console, click the following path:
bus_name link_name channel_name.
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 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 |
The hostname or TCP/IP IP address for the gateway queue manager that is used to connect into the WebSphere MQ network.
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 |
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 |
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.
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 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. |
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 |
The number of seconds between attempts by the sender channel to restart after a communication or partner failure.
For considerations when using retry mechanisms with WebSphere MQ, see the WebSphere MQ Intercommunication book.
Required | No |
Data type | Integer |
Default | 60 seconds |
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 count of remaining retries reaches zero, and the channel has not restarted, then an error is logged and the channel is stopped.
For considerations when using retry mechanisms with WebSphere MQ, see the WebSphere MQ Intercommunication book.
Required | No |
Data type | Long |
Default | 999999999 |
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 considerations when using retry mechanisms with WebSphere MQ, see the WebSphere MQ Intercommunication book.
Required | No |
Data type | Long |
Default | 1200 seconds |
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.
Required | No |
Data type | drop-down list |
Default | Started |
Range |
|
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 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 |
The TCP/IP IP address of the host on which the target queue manager runs.
Required | No |
Data type | Text |
The run-time status of the sender channel.
Required | No |
Data type | drop-down list |
Range |
|
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 |
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 |
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 | drop-down list |
Range |
|
The last logical unit-of-work identifier for a message on the channel.
Required | No |
Data type | Text |
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 |
The number of messages in the current batch on the channel.
Required | No |
Data type | Text |
The number of batches that have been sent on the channel.
Required | No |
Data type | Text |
The number of messages that have been sent on the channel.
Required | No |
Data type | Text |
The time at which the last message was sent on the channel.
Required | No |
Data type | Text |
The date on which the last message was sent on the channel.
Required | No |
Data type | Text |
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 |
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 |
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 |
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 |
The class of service for nonpersistent messages on the sender channel.
Required | No |
Data type | drop-down list |
Range |
|
Whether or not a manual stop request has been made for the sender channel.
Required | No |
Data type | drop-down list |
Range |
|