Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage messaging with a third-party or (deprecated) V5 default messaging provider > Manage messaging with a third-party non-JCA messaging provider > Configure JMS resources for a third-party non-JCA messaging provider


Configure a JMS destination for a third-party non-JCA messaging provider

Use this task to browse or change the properties of a JMS destination for use with a third-party non-JCA messaging provider. Before starting this task, you should have defined the messaging provider to WAS.


Procedure

  1. Start the admin console.

  2. In the navigation pane, click Resources > JMS ->JMS providers.

  3. Click the name of the third-party non-JCA messaging provider.

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

  5. 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. We can specify other properties, as described in a later step.

      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.
    Optional. Change properties for the JMS destination, according to your needs.

  6. Click OK.

  7. Save any changes to the master configuration.

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


Related


Third-party JMS destination settings
Configure a JMS connection factory for a third-party non-JCA messaging provider
Configure JMS resources for a third-party non-JCA messaging provider

+

Search Tips   |   Advanced Search