Network Deployment (Distributed operating systems), v8.0 > Reference > Sets
Default messaging provider queue [Settings]
A JMS queue is used as a destination for point-to-point messaging. Use JMS queue destination administrative objects to manage JMS queues for the default messaging provider.
To view this page in the console, click one of the following paths:
- Resources -> JMS -> Queues -> queue_name
- Resources -> JMS -> JMS providers -> a_messaging_provider -> [Additional Properties] Queues -> queue_name
Configuration tab
These property values are preserved even if the runtime environment is stopped then restarted.
General Properties
Scope
Highest topological level at which application servers can use this resource object.
Required No Data type String
Provider
Specifies a JMS provider, which enables asynchronous messaging based on the JMS. It provides J2EE connection factories to create connections for specific JMS queue or topic destinations. JMS provider administrative objects are used to manage JMS resources for the associated JMS provider.
Required No Data type String
Name
The required display name for the resource.
Required Yes Data type String
JNDI name
The JNDI name for the resource.
As a convention, use a JNDI name of the form jms/Name, where Name is the logical name of the resource. For more information about the use of JNDI and its syntax, see the topic JNDI support in WAS.
Required Yes Data type String
Description
An optional description for the resource.
Required No Data type Text area
Bus name
The bus on which the associated queue exists, or leave blank to use the bus to which the application connects.
Required No Data type Custom
Queue name
The name of the associated queue on the service integration bus.
Type the name of a queue that has been created on the service integration bus.
Required Yes Data type Custom
Delivery mode
The delivery mode for messages sent to this destination. This controls the persistence of messages on this destination.
Required No Data type drop-down list Range
Application
The persistence of messages on this topic is defined by the producing application.
Nonpersistent
All messages sent to this topic are treated as nonpersistent.
Persistent
All messages sent to this topic are treated as persistent.
Time to live
The default length of time in milliseconds from its dispatch time that a message sent to this destination should be kept by the system.
Required No Data type Integer Range 0 through 574476389546486783 A value of 0 (zero) means that messages are kept indefinitely. The default for this property is null, which allows the application to determine the time to keep messages.
Priority
The relative priority for messages sent to this destination, in the range 0 to 9, with 0 as the lowest priority and 9 as the highest priority.
If a value is not specified for this property, the message priority set by the producing application is used.
Required No Data type Integer Range 0 through 9 The message priority range is from 0 (lowest) through 9 (highest).
Read ahead
Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
Messages that are assigned to a consumer are locked on the server and cannot be consumed by any other consumers for that destination. Messages that are assigned to a consumer, but not consumed before that consumer is closed, are subsequently unlocked on the server and then available for receipt by other consumers.
This property overrides the value set by the Read ahead property on the JMS connection factory.
Required No Data type drop-down list Range
Enabled
The messaging provider preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests for this destination.
Disabled
The messaging provider does not preemptively assign messages to consumers for this destination.
Inherit from connection factory
Read ahead optimization is defined on the connection.
Restrict messages to the local queue point if a queue point is configured on the connected messaging engine
Indicates whether the underlying service integration bus queue destination is scoped to a local queue point when addressed by using this JMS queue. A local queue point is a queue point of the service integration bus queue that is configured on the messaging engine to which the JMS application is connected.
This option applies when using this JMS queue to send and receive messages, and when setting a reply queue in a request message. When a reply queue is set in a request message, the local queue point is on the messaging engine to which the application setting the reply queue is connected, not the messaging engine to which the application that uses the reply queue sends the reply message. If the connected messaging engine does not have a queue point for the destination this option is ignored. The default value is FALSE.
This option is supported only when used by a JMS application that is running with a WAS v7.0 or later server or client, and that is connected to a messaging engine running on WAS v7.0 or later server. Use on previous versions of WAS will result in an exception to the application.
Required Yes Data type Boolean Default FALSE
Local queue point preference
Prefer to send messages to a local queue point
If a queue point for this queue exists on the messaging engine that the application is connected to, prefer to send all messages to it to improve performance. If this local queue point is not accepting new messages, the messages are sent to other queue points, if possible.
Required No Data type Radio button
Do not prefer a local queue point over other queue points
All available queue points are treated equally, with no preference given to a local queue point. Messages are workload balanced across all queue points. This option is supported only when used by a JMS application that is running with a WAS Version 7.0 or later server or client, and that is connected to a messaging engine running on WAS Version 7.0 or later server. Use on previous versions of WAS will result in an exception to the application.
Required No Data type Radio button
Message affinity across queue points
Send all messages to the same queue point
A message producer created to use this queue sends all messages to the same queue point. This option does not influence the initial choice of queue point. This option applies to a message producer only if the queue is identified at the time the message producer is created, not at the time of sending messages. This option is supported only when used by a JMS application that is running with a WAS Version 7.0 or later server or client, and that is connected to a messaging engine running on WAS Version 7.0 or later server. Use on previous versions of WAS will result in an exception to the application.
Required No Data type Radio button
Messages may be sent to different queue points
A message producer can send messages to different queue points, based on the availability of the queue points and workload balancing of the system.
Required No Data type Radio button
Message visibility
Only messages on a single queue point are visible
A consumer or browser has access to messages on only one queue point, not the entire queue. The single queue point is chosen by the messaging system. A queue point that is defined on the same messaging engine that the application is connected to is preferred to other queue points.
Required No Data type Radio button
Messages on all queue points are visible
A consumer or browser has access to messages on all queue points of the queue. If you enable this option, all queue points are actively checked for messages. This means that no messages are left on an unattended queue point. However, there is a performance cost in scanning all queue points for messages, and you can no longer control the order in which messages are taken off the queue. This option is supported only when used by a JMS application that is running with a WAS Version 7.0 or later server or client, and that is connected to a messaging engine running on WAS Version 7.0 or later server. Use on previous versions of WAS will result in an exception to the application.
Required No Data type Radio button
Related Items
Buses
A service integration bus supports applications using message-based and service-oriented architectures. A bus is a group of interconnected servers and clusters that have been added as members of the bus. Applications connect to a bus at one of the messaging engines associated with its bus members.
JMS queue resources and service integration
Configure a queue for the default messaging provider
Administrative console buttons
Administrative console preferences