Set a JMS destination for a third-party messaging provider

Use this task to browse or change the properties of a JMS destination for use with a third-party messaging provider; that is a messaging provider other than the default messaging provider, the WebSphere MQ messaging provider or the V5 default messaging provider.

To configure a JMS destination for use with a third-party messaging provider, use the admin console to complete the

 

1. In the navigation pane, click Resources > JMS > JMS providers .

2. Click the name of the third-party messaging provider.

3. In the content pane, under Additional Properties, click Queues for point-to-point messaging or Topics for publish/subscribe messaging. This displays a table listing any existing JMS destinations, with a summary of their properties.

4. To browse or change an existing JMS destination, click its name in the list. Otherwise, to create a new destination...

   1. Click New in the content pane.

   2. Specify the following required properties.

      Name

      The name by which this JMS destination is known for administrative purposes within WAS.

      Type

      Select whether the destination is for JMS queues (QUEUE) or JMS topics (TOPIC).

      JNDI Name

      The JNDI name used to bind the JMS destination into the WAS namespace.

      External JNDI Name

      The JNDI name used to bind the JMS destination into the namespace of the messaging provider.

   3. Click Apply. This defines the JMS destination to WAS, and enables you to browse or change additional properties.

5. Change properties for the JMS destination, according to the needs.

6. Click OK.

7. Save any changes to the master configuration.

8. To have the changed configuration take effect, stop then restart the appserver.

Third-party JMS destination settings

 

Related tasks

Set a JMS connection factory for a third-party messaging provider
Set JMS resources for a third-party messaging provider