WebSphere MQ messaging provider queue and topic advanced properties settings
To set the advanced properties for the selected queue or topic destination for use with the WebSphere MQ messaging provider. These advanced properties control the behavior of connections made to WebSphere MQ messaging provider destinations.
- In the navigation pane, click...
Resources | JMS
- Click Queues or Topics to display existing queue or topic destinations.
- Set the Scope
- Click the name of the queue or topic destination that you want to work with.
- In the content pane, under Additional properties, click Advanced properties to display a list of the advanced properties of the WebSphere MQ queue or topic destination.
Under General Properties there are three groups of properties:
- Delivery
- Message format
- Optimizations
Make any required changes to these groups and then click Apply to return to the queue or topic.
When specifying WebSphere MQ properties, the following restrictions apply:
- Names can have a maximum of 48 characters, with the exception of channels, which have a maximum of 20 characters.
- The property values specified must match the values that you specified when configuring WebSphere MQ for JMS resources.
A queue or topic for use with the WebSphere MQ messaging provider has the following advanced properties.
- Persistence
- The level of persistence used to store messages sent to this destination.
Data type Drop-down list Default As set by application Range
- As set by application
- Messages on the destination have their persistence defined by the application that put them onto the queue.
- As for WebSphere MQ queue definition
- Messages on the destination have their persistence defined by the WebSphere MQ queue definition properties.
- WebSphere MQ Persistent
- Messages on the destination are persistent.
- WebSphere MQ Non-persistent
- Messages on the destination are not persistent.
- WebSphere MQ High
- Permit persistent messages to be sent as non-persistent messages when using an underlying WebSphere MQ queue with a NPMCLASS of 'HIGH'.
- Priority
- The priority assigned to messages sent to this destination.
Data type Drop-down list Default As set by application Range
- As set by application
- The priority of messages on this destination is defined by the application that put them onto the destination.
- As for WebSphere MQ queue definition
- Messages on the destination have their persistence defined by the WebSphere MQ destination definition properties.
- Specified
- The priority of messages on this destination is defined by the Specified priority property. If we select this option, define a priority on the Specified priority property.
- Specified priority
If the Priority property was set to Specified, select the priority assigned to messages sent to this queue type destination.
Data type Drop-down list Units Message priority level Default As set by application Range 0 (lowest priority) through 9 (highest priority)
- Expiry
An option that specifies the expiry timeout for this destination.
Data type Drop-down list Default As set by application Range
- As set by application
- The expiry timeout for messages on this destination is defined by the application that put them onto the destination.
- Specified
- The expiry timeout for messages on this destination is defined by the Specified expiry property. If we select this option, define a timeout on the Specified expiry property.
- Unlimited
- Messages on this destination have no expiry timeout, so these messages never expire.
- Specified expiry
If the Expiry property is set to Specified, enter the number of milliseconds after which messages expire and are removed from this destination.
Data type Integer Units Milliseconds Default 0 Range Greater than or equal to 0
- 0 indicates that messages never timeout
- Other values are an integer number of milliseconds
- Coded character set identifier
The character set to use when encoding strings in the message.
Data type Integer Default 1208 Range 1 through 65535. The CCSID must be one of the CCSIDs supported by WebSphere MQ.
- Use native encoding
- An option that specifies whether the destination should use native encoding to provide appropriate encoding values for the Java platform.
Data type Check box Default Selected Range
- Selected
- Native encoding is used.
- Cleared
- Native encoding is not used, so specify the properties for Integer encoding, Decimal encoding, and Floating point encoding.
- Integer encoding
If the Use native encoding check box is cleared, select the type of integer encoding to be used.
Data type Drop-down list Default Normal Range
- Normal
- Normal integer encoding is used.
- Reversed
- Reversed integer encoding is used.
- Decimal encoding
- If the Use native encoding check box is cleared, select the type of decimal encoding to be used.
Data type Drop-down list Units Not applicable Default Normal Range
- Normal
- Normal decimal encoding is used.
- Reversed
- Reversed decimal encoding is used.
- Floating point encoding
- If the Use native encoding check box is cleared, select the type of floating point encoding to be used.
Data type Drop-down list Default IEEENORMAL Range
- IEEENORMAL
- IEEE normal floating point encoding is used.
- IEEEREVERSED
- IEEE reversed floating point encoding is used.
- z/OS
- z/OS floating point encoding is used.
- Append RFH version 2 headers to messages sent to this destination
The action to take when replying to a message that is sent to this destination.
Data type Check box Default Selected Range
- Cleared
- Do not append RFH version 2 headers to messages sent to this destination.
- Selected
- Append RFH version 2 headers to messages sent to this destination.
- Asynchronously send messages to the queue manager
An option that enables the queue manager to acknowledge receipt of messages sent to it. Asynchronously sending messages to the queue manager is faster, but messages can be lost if the messaging infrastructure fails.
Data type Drop-down list Default The default value depends on whether we are working with a queue or topic destination.
- As for queue definition
- The default value if we are working with a queue destination.
- As for topic definition
- The default value if we are working with a topic destination.
Range
- As for queue definition
- Messages are acknowledged according to the WebSphere MQ queue definition properties.
- As for topic definition
- Messages are acknowledged according to the WebSphere MQ topic definition properties.
- Yes
- The queue manager acknowledges receipt of messages sent to it.
- No
- The queue manager does not acknowledge receipt of messages sent to it.
- Read ahead and cache non-persistent messages for consumers
An option that determines whether messages for non-persistent consumers are sent to the client speculatively. Selecting this option results in faster message delivery but messages can be lost in the event of a failure in the messaging infrastructure.
Data type Drop-down list Default The default value depends on whether we are working with a queue or topic destination.
- As for queue definition
- Default value if we are working with a queue destination.
- As for topic definition
- Default value if we are working with a topic destination.
Range
- As for queue definition
- Messages are sent to the client according to the WebSphere MQ queue definition properties.
- As for topic definition
- Messages are sent to the client according to the WebSphere MQ topic definition properties.
- Yes
- Messages are sent to the client speculatively.
- No
- Messages are not sent to the client speculatively.
- Read ahead consumer close method
- If Read ahead and cache non-persistent messages for consumers is set to Yes or As for queue definition this property is enabled. This property determines what happens to messages in the internal read ahead buffer when the message consumer is closed.
Data type Drop-down list Default Close method waits for all cached messages to be delivered Range
- Wait for all cached messages to be delivered
- All messages in the internal read ahead buffer are delivered to the application's message listener before returning.
- Wait for the current message to be delivered
- Only the current message listener invocation completes before returning, potentially leaving messages in the internal read ahead buffer, which are then discarded.
Related
Mapping of admin console panel names to command names and WebSphere MQ names
WebSphere MQ messaging provider queue settings
WebSphere MQ messaging provider topic settings