Version 5 default messaging queue settings
To set the configuration properties of the selected JMS queue destination for point-to-point messaging by WAS V5 applications.
A queue destination is used to configure a JMS queue of the default messaging provider for use by WAS Version 5 applications. Connections to the queue are created by the associated V5 default messaging WebSphere queue connection factory.
To view this page, use the admin console to complete the
- In the navigation pane, click Resources > JMS > JMS providers .
- (Optional) In the content pane, change the Scope setting to the level at which JMS resources are visible to applications. If we define a V5 JMS resource at the Cell scope level, all users in the cell can look up and use that JMS resource. However, the JMS resource has only the subset of properties that apply to WAS V5. To define a JMS resource at Cell level for use on non-Version 5 nodes, you should define the JMS resource for the V6 default messaging provider.
- In the content pane, click the name of the V5 default messaging provider to support the JMS destination.
- Under Additional Resources, click Queues. This displays a list of any existing JMS queue destinations.
- Click the name of the JMS queue destination to work with.
A JMS queue for use with the internal WebSphere JMS provider has the following properties.
- Scope
Level to which this resource definition is visible to applications.
Resources such as messaging providers, namespace bindings, or shared libraries can be defined at multiple scopes, with resources defined at more specific scopes overriding duplicates defined at more general scopes.
The scope displayed is for information only, and cannot be changed on this panel. To browse or change this resource (or other resources) at a different scope, change the scope on the messaging provider settings panel, then click Apply, before clicking the link for the type of resource.
Data type String
- Name
The name by which the queue is known for administrative purposes within IBM WAS.
To enable applications to use this queue, add the queue name to the Queue Names field on the panel for the JMS server that hosts the queue.
Data type String
- JNDI name
The JNDI name used to bind the queue into the application server namespace.
As a convention, use the fully qualified JNDI name; for example, in the form jms/Name, where Name is the logical name of the resource.
This name is used to link the platform binding information. The binding associates the resources defined by the deployment descriptor of the module to the actual (physical) resources bound into JNDI by the platform.
Data type String
- Description
A description of the queue, for admin purposes
Data type String Default Null
- Category
A category used to classify or group this queue, for the IBM WAS administrative records.
Data type String
- Persistence
Whether all messages sent to the destination are persistent, non-persistent, or have their persistence defined by the application
Data type Enum Default APPLICATION DEFINED Range
- APPLICATION DEFINED
- Messages on the destination have their persistence defined by the application that put them onto the queue.
- NON PERSISTENT
- Messages on the destination are not persistent.
- PERSISTENT
- Messages on the destination are persistent. When a persistent message is put to a queue, all of the message data is written to the messaging log (under the embedded_messaging_install\log directory) to make recovery of the message possible.
- Priority
Whether the message priority for this destination is defined by the application or the Specified priority property
Data type Enum Default APPLICATION DEFINED Range
- APPLICATION DEFINED
- The priority of messages on this destination is defined by the application that put them onto the destination.
- QUEUE DEFINED
- [WebSphere MQ destination only] Messages on the destination have their persistence defined by the WebSphere MQ queue 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 is set to Specified, type here the message priority for this queue, in the range 0 (lowest) through 9 (highest)
If the Priority property is set to Specified, messages sent to this queue have the priority value specified by this property.
Data type Integer Units Message priority level Default 0 Range 0 (lowest priority) through 9 (highest priority)
- Expiry
Whether the expiry timeout for this queue is defined by the application or the Specified expiry property, or messages on the queue never expire (have an unlimited expiry timeout)
Data type Enum Default APPLICATION DEFINED Range
- APPLICATION DEFINED
- The expiry timeout for messages on this queue is defined by the application that put them onto the queue.
- UNLIMITED
- Messages on this queue have no expiry timeout, so those messages never expire.
- SPECIFIED
- The expiry timeout for messages on this queue is defined by the Specified expiry property.If we select this option, define a timeout on the Specified expiry property.
- Specified expiry
If the Expiry timeout property is set to Specified, type here the number of milliseconds (greater than 0) after which messages on this queue expire
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
Related tasks
Set a queue for V5 default messaging