IBM MQ queue points [Settings]

A IBM MQ queue point is used when sending messages to and receiving messages from a IBM 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] IBM 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

IBM MQ queue name

The IBM MQ queue name as defined in IBM MQ.

Information Value
Required Yes
Data type String

Inbound nonpersistent reliability

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

The messages in a IBM 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 IBM MQ quality of service level.

For nonpersistent IBM 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, you 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 IBM 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 IBM MQ message is received.

The messages in a IBM 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 IBM MQ quality of service level.

For persistent IBM 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, you 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 IBM 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 IBM MQ

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

Information Value
Required No
Data type Boolean

Icon that indicates the type of topic Reference topic



Timestamp icon Last updated: March 5, 2017 17:54
File name: SIBMQQueueLocalizationPoint_DetailForm.html