File name: umj_MQQueueAdvancedProps.html
WebSphere MQ messaging
provider queue and topic advanced properties settings
Use this panel to view or change 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.
To view
WebSphere MQ queue or
topic advanced properties settings, use the administrative console
to complete the following steps:
- In the navigation pane, click .
- Click Queues or Topics to
display existing queue or topic destinations.
- If appropriate, in the content pane, change the Scope setting
to the level at which the queue or topic destinations are defined.
This restricts the set of queue or topic destinations displayed.
- 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 five groups of properties:
- Delivery
- Message format
- Optimizations
- newfeatMessage descriptor
- newfeatAdditional
Make any required changes to these groups and then click Apply to
return to the queue or topic.
Note: 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 that you specify must match the values that
you specified when configuring JMS resources for WebSphere MQ. For more information about
configuring JMS resources for WebSphere MQ,
see Using Java section
of the WebSphere MQ information center.
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 per 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 you use 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 per 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 you select this option, you must 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 you select
this option, you must 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 coded character set identifier (CCSID)
must be one of the CCSIDs supported by WebSphere MQ. Blank.
Leaving this field empty indicates that the default value must be
used. |
For more information about supported CCSIDs, and about converting
between message data from one coded character set to another, see
the System Administration Guide and Application
Programming Reference sections of the WebSphere MQ information center.
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.
|
Message body
newfeatSpecifies whether an application processes the RFH version
2 header of a WebSphere MQ message
as part of the JMS message body.
Data type |
Drop-down list |
Default |
UNSPECIFIED |
Range |
- UNSPECIFIED
- When sending messages, the WebSphere MQ messaging
provider does or does not generate and include an RFH version 2 header,
depending on the value of the Append RFH version 2 headers to messages
sent to this destination property. When receiving messages, the WebSphere MQ messaging provider acts
as if the value is set to JMS.
- JMS
- When sending messages, the WebSphere MQ messaging
provider automatically generates an RFH version 2 header and includes
it in the WebSphere MQ message. When
receiving messages, the WebSphere MQ messaging
provider sets the JMS message properties according to values in the
RFH version 2 header (if these value are present); it does not present
the RFH version 2 header as part of the JMS message body.
- MQ
- When sending messages, the WebSphere MQ messaging
provider does not generate an RFH version 2 header. When receiving
messages, the WebSphere MQ messaging
provider presents the RFH version 2 header as part of the JMS message
body.
|
ReplyTo destination style
newfeatSpecifies the format of the JMSReplyTo field.
Data type |
Drop-down list |
Default |
DEFAULT |
Range |
- DEFAULT
- The default value is equivalent to the information in the RFH
version 2 header.
- MQMD
- Use the value supplied in the MQMD. This populates the reply to
queue manager field with the value from the MQMD, equivalent to the
default behaviour of WebSphere MQ Version
6.0.2.4 and 6.0.2.5.
- RFH2
- Use the value supplied in the RFH version 2 header. If the sending
application set a JMSReplyTo value, then that value is used.
|
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 you are working with
a queue or topic destination.
- As per queue definition
- The default value if you are working with a queue destination.
- As per topic definition
- The default value if you are working with a topic destination.
|
Range |
- As per queue definition
- Messages are acknowledged according to the WebSphere MQ queue definition properties.
- As per 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 you are working with
a queue or topic destination.
- As per queue definition
- This is the default value if you are working with a queue destination.
- As per topic definition
- This is the default value if you are working with a topic destination.
|
Range |
- As per queue definition
- Messages are sent to the client according to the WebSphere MQ queue definition properties.
- As per 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.
|
ReplyTo destination style
newfeatSpecifies the format of the JMSReplyTo field.
Data type |
Drop-down list |
Default |
DEFAULT |
Range |
- DEFAULT
- The default value is equivalent to the information in the RFH
version 2 header.
- MQMD
- Use the value supplied in the MQMD. This populates the reply to
queue manager field with the value from the MQMD, equivalent to the
default behaviour of WebSphere MQ Version
6.0.2.4 and 6.0.2.5.
- RFH2
- Use the value supplied in the RFH version 2 header. If the sending
application set a JMSReplyTo value, then that value is used.
|
For more information about automatic client reconnection, see the WebSphere MQ information center.
Read ahead consumer close method
If Read ahead and cache non-persistent messages
for consumers is set to Yes or As
per 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.
|
MQMD read enabled
newfeatSpecifies whether an application can read the values of
MQMD fields from JMS messages that have been sent or received using
the WebSphere MQ messaging provider.
Data type |
Check box |
Default |
Cleared |
Range |
- Cleared
- Applications cannot read the values of the MQMD fields.
- Selected
- Applications can read the values of the MQMD fields.
|
MQMD write enabled
newfeatSpecifies whether an application can write the values of
MQMD fields to JMS messages that will be sent or received using the WebSphere MQ messaging provider.
Data type |
Check box |
Default |
Cleared |
Range |
- Cleared
- Applications cannot write the values of the MQMD fields.
- Selected
- Applications can write the values of the MQMD fields.
|
MQMD message context
newfeatDefines the message context options specified when sending
messages to a destination.
Data type |
Drop-down list |
Default |
DEFAULT |
Range |
- DEFAULT
- The MQOPEN API call and the MQPMO structure specify no explicit
message context options.
- SET_IDENTITY_CONTEXT
- The MQOPEN API call specifies the message context option MQOO_SET_IDENTITY_CONTEXT,
and the MQPMO structure specifies MQPMO_SET_IDENTITY_CONTEXT.
- SET_ALL_CONTEXT
- The MQOPEN API call specifies the message context option MQOO_SET_ALL_CONTEXT,
and the MQPMO structure specifies MQPMO_SET_ALL_CONTEXT.
|
|
