WebSphere MQ link receiver channel connections [Settings]

A connection that exists on the receiver channel of the WebSphere MQ link.

To view this page in the console, click the following path:

Service integration -> Buses -> bus_name -> [Topology] Messaging engines -> engine_name -> [Additional properties] WebSphere MQ links -> link_name -> [Additional Properties] Receiver channel -> channel_name -> Runtime > Receiver channel connections -> channel_connection_name.

Runtime tab

The Runtime tab shows runtime properties and current runtime state for this MQ link receiver channel connection. These properties are not preserved when the current runtime environment is stopped.

General Properties

WebSphere MQ link receiver channel name

The name of the receiver channel for the WebSphere MQ link, used to receive messages from WebSphere MQ onto the bus.

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

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

WebSphere MQ Queue Manager name

The name of the WebSphere MQ queue manager on which the WebSphere MQ sender channel, that is connected to this MQ link receiver channel connection instance, is running.

Information	Value
Required	No
Data type	String

IP address

The IP address of the queue manager for the WebSphere MQ link receiver channel connection.

Information	Value
Required	No
Data type	String

Status

The runtime status of the WebSphere MQ link receiver channel connection.

Information	Value
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.

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 WebSphere MQ sender channel to the WebSphere MQ link receiver channel when there are no messages on the transmission queue being served by the WebSphere MQ sender channel.

Information	Value
Required	No
Data type	String

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 information about how to choose an appropriate value for this property, see the description of the Sequence Numberwrap (SEQWRAP) property in the WebSphere MQ Intercommunication book.

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

Adoptable

Whether or not a running instance of a WebSphere MQ link receiver channel (associated with this MQ link) should be adopted or not. In the event of a communications failure, it is possible for a running instance of a WebSphere MQ link receiver channel to be left waiting for messages. When communication is re-established, and the partner WebSphere MQ sender channel next attempts to establish a session with the WebSphere MQ link receiver channel, the request will fail as there is already a running instance of the WebSphere MQ link receiver channel that believes it is in session with the partner WebSphere MQ sender channel. We can overcome this problem by selecting this option, which causes the already running instance of the WebSphere MQ link receiver channel to be stopped and a new instance to be started.

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	drop-down list
Range	true false

Maximum message length

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

Information	Value
Required	No
Data type	String

Stop requested

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

Information	Value
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 of the WebSphere MQ link receiver channel connection.

Information	Value
Required	No
Data type	String

Current sequence number

The current sequence number for the message on the channel.

We can reset the sequence number of an MQLinkReceiver channel by resetting the sequence number of the partner WebSphere MQ sender channel. For details of how to reset the sequence number of a WebSphere MQ sender channel, see the WebSphere MQ Intercommunications Guide section of the WebSphere MQ library.

Information	Value
Required	No
Data type	String

Last LUWID

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

Information	Value
Required	No
Data type	String

Last Sequence number

The last sequence number for a message on the channel.

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 received

The number of batches received on the channel.

Information	Value
Required	No
Data type	String

Number of messages received

The number of messages received on the channel.

Information	Value
Required	No
Data type	String

Buffers sent

The number of buffers sent on the channel.

Information	Value
Required	No
Data type	String

Buffers received

The number of buffers received on the channel.

Information	Value
Required	No
Data type	String

Bytes sent

The number of bytes sent on the channel.

Information	Value
Required	No
Data type	String

Bytes received

The number of bytes received on the channel.

Information	Value
Required	No
Data type	String

Last message receive time

The time at which the last message was received on the receiver channel connection.

Information	Value
Required	No
Data type	String

Last message receive date

The date on which the last message was received on the receiver channel connection.

Information	Value
Required	No
Data type	String

nonpersistent message speed

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

Information	Value
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.

Inbound nonpersistent message reliability

The acceptable reliability of message delivery for nonpersistent message flows from WebSphere MQ through this WebSphere MQ link, from Best effort to Reliable, in order of increasing reliability.

This reliability delivery option is assigned to all WebSphere MQ nonpersistent messages flowing over this receiver channel.

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	drop-down list
Range	Best effort Messages are discarded when a messaging engine stops or fails. Messages might also be discarded if a connection used to send them becomes unavailable or as a result of constrained system resources. Express Messages are discarded when a messaging engine stops or fails. Messages might also be discarded if a connection used to send them becomes unavailable. Reliable Messages are discarded when a messaging engine stops or fails.

Inbound persistent message reliability

The acceptable reliability of message delivery for inbound persistent message flows from WebSphere MQ through this WebSphere MQ link, from Reliable to Assured, in order of increasing reliability.

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	drop-down list
Range	Reliable Messages might be discarded when a messaging engine fails. Assured Messages are not discarded.

Related tasks

View the status of a WebSphere MQ link and its sender and receiver channels

Add a WebSphere MQ link receiver channel

Related information:

Administrative console buttons

Administrative console preference settings Reference topic