Generic JMS destination settings

Use this panel to view or change the configuration properties of the selected JMS destination for use with the associated JMS provider.

A JMS destination is used to configure the properties of a JMS destination for the associated generic JMS provider. Connections to the JMS destination are created by the associated JMS connection factory. A JMS destination for use with a generic JMS provider (not the embedded WebSphere JMS provider or WebSphere MQ JMS provider) has the following properties.

To view this administrative console page, click Resources-> Generic JMS Providers-> provider_name-> JMS Destinations-> destination

Name

The name by which the queue is known for administrative purposes within IBM WebSphere Application Server.

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 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.

Data type

String

Description

A description of the queue, for administrative purposes

Category

A category used to classify or group this queue, for your IBM WebSphere Application Server administrative records.

Data type

String

External JNDI name

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.

Data type

String