WebSphere MQ queue points [Settings]

A WebSphere MQ queue point is used when sending messages to and receiving messages from a WebSphere MQ queue.

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

Service integration -> Buses -> bus_name -> [Topology] Messaging engines -> engine_name -> Runtime > [Message points] WebSphere MQ Queue points -> queue_point_name.

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

Identifier

The system-generated name by which this message point is known.

Information	Value
Required	No
Data type	String

UUID

The universal unique identifier assigned by the system to this message point for administrative purposes.

Information	Value
Required	No
Data type	String

Target UUID

The UUID of the bus destination for which this is a message point.

Information	Value
Required	No
Data type	String

WebSphere MQ queue name

The WebSphere MQ queue name as defined in WebSphere MQ.

Information	Value
Required	Yes
Data type	String

Inbound nonpersistent reliability

The level of reliability to apply when a nonpersistent WebSphere MQ message is received.

The messages in a WebSphere MQ network have their own quality of service level. This is either persistent or non-persistent. When these messages are received by a service integration application, they are assigned a service integration quality of service level that depends on their WebSphere MQ quality of service level.

For nonpersistent WebSphere MQ messages received, you will probably choose one of the nonpersistent service integration qualities of service, that is reliable nonpersistent, best effort nonpersistent or express nonpersistent. However, we can choose any of the five possible service integration qualities of service:

Best effort nonpersistent

Express nonpersistent

Reliable nonpersistent

Reliable persistent

Assured persistent

For more information, see Mapping the JMS delivery option and message reliability to and from the WebSphere MQ persistence value.

Information	Value
Required	No
Data type	drop-down list
Range	Best effort nonpersistent 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 nonpersistent 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 nonpersistent Messages are discarded when a messaging engine stops or fails. Reliable persistent Messages might be discarded when a messaging engine fails. Assured persistent Messages are not discarded.

Inbound persistent reliability

The level of reliability to apply when a persistent WebSphere MQ message is received.

The messages in a WebSphere MQ network have their own quality of service level. This is either persistent or non-persistent. When these messages are received by a service integration application, they are assigned a service integration quality of service level that depends on their WebSphere MQ quality of service level.

For persistent WebSphere MQ messages received, you will probably choose one of the persistent service integration qualities of service, that is either assured persistent or reliable persistent. However, we can choose any of the five possible service integration qualities of service:

Best effort nonpersistent

Express nonpersistent

Reliable nonpersistent

Reliable persistent

Assured persistent

For more information, see Mapping the JMS delivery option and message reliability to and from the WebSphere MQ persistence value.

Information	Value
Required	No
Data type	drop-down list
Range	Best effort nonpersistent 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 nonpersistent 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 nonpersistent Messages are discarded when a messaging engine stops or fails. Reliable persistent Messages might be discarded when a messaging engine fails. Assured persistent Messages are not discarded.

Include an RFH2 message header when sending messages to WebSphere MQ

If selected, messages sent to WebSphere MQ will include an RFH2 header. The RFH2 header stores additional information to that which is stored in the WebSphere MQ message header.

Information	Value
Required	No
Data type	Boolean

Related concepts

WebSphere MQ queue points and mediation points

Related tasks

Create a queue-type destination and assigning it to a WebSphere MQ queue

Related information:

Administrative console buttons

Administrative console preference settings Reference topic