Third-party JMS destination settings
Use this panel to browse or change the configuration properties of the selected JMS destination for use with an associated third-party non-JCA messaging provider.
A JMS destination is used to configure the properties of a JMS destination for the associated third-party non-JCA messaging provider. Connections to the JMS destination are created by the associated JMS connection factory.
To navigate to this panel:
- In the navigation pane, click...
Resources > JMS->JMS providers. The JMS providers collection panel is displayed. This lists all currently configured messaging providers across all scopes (we can modify the scope if required).
- Click the name of the third-party non-JCA messaging provider.
- Under Additional Properties, click Queues for point-to-point messaging or Topics for publish/subscribe messaging.
- Click the name of the JMS destination to work with.
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.
Information Value Data type String
Name
The name by which the queue is known for administrative purposes within WebSphere Application Server.
Information Value Data type String
Type
Whether this JMS destination is a queue (for point-to-point) or topic (for publish/subscribe).
Select one of the following options:
- Queue
- A JMS queue destination for point-to-point messaging.
- Topic
- A JMS topic destination for publish/subscribe messaging.
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.
Information Value Data type String
Description
A description of the queue, for administrative purposes
Information Value Data type String
Category
A category used to classify or group this queue, for our WAS administrative records.
Information Value Data type String
External 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.
Information Value Data type String