WebSphere queue settings
To view or change queue destinations go to...Console | Resources | WebSphere JMS Provider | WebSphere Queue Destinations | destination_name
Connections to the queue are created by the associated queue connection factory for the embedded JMS provider. A queue for use with the internal WebSphere JMS provider has the following properties.
Level to which this resource definition is visible -- the cell, node, or server level.
Resources such as JMS Providers, Namespace bindings, or shared libraries can be defined at multiple scopes, with resources defined at more specific scopes overriding duplicates which are defined at more general scopes.
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 list of queue names in the configuration of the JMS servers that host the queue.
The JNDI name that is used to bind the queue into the application server's name space.
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.
A description of the queue, for administrative purposes
A category used to classify or group this queue, for your IBM WAS administrative records.
Whether all messages sent to the destination are persistent, non-persistent, or have their persistence defined by the application
Default is APPLICATION DEFINED
Range of values is...
Messages on the destination have their persistence defined by the application that put them onto the queue.
Messages on the destination are not 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 to make recovery of the message possible.
Whether the message priority for this destination is defined by the application or the Specified priority property. Default is APPLICATION DEFINED. Range includes...
The priority of messages on this destination is defined by the application that put them onto the destination.
[WebSphere MQ destination only] Messages on the destination have their persistence defined by the WebSphere MQ queue definition properties.
The priority of messages on this destination is defined by the Specified priority property.If you select this option, define a priority on the Specified priority property.
If the Priority property is set to Specified, messages sent to this queue have the priority value specified by this property. Default is 0 (lowest priority). Range is 0-9
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). Default is APPLICATION DEFINED. Range includes... APPLICATION DEFINED
The expiry timeout for messages on this queue is defined by the application that put them onto the queue.
Messages on this queue have no expiry timeout, so those messages never expire.
The expiry timeout for messages on this queue is defined by the Specified expiry property.If you select this option, define a timeout on the Specified expiry property.
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. Default is 0. Range is greater than or equal to 0. 0 indicates that messages never timeout.