+

Search Tips   |   Advanced Search

Set a topic for V5 default messaging


Use this task to browse or change the properties of a JMS topic destination for publish/subscribe messaging by WAS V5 applications. This task contains an optional step for you to create a new topic destination.

To configure a JMS topic destination for use WAS V5 applications, use the admin console to complete the following steps:

 

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

  2. Select the V5 default messaging provider for which you want to configure a topic destination.

  3. Change the Scope setting to the level at which the JMS destination is visible to applications.

    If we define a V5 JMS resource at the Cell scope level, all users in the cell can look up and use that JMS resource.

  4. In the content pane, under Additional Properties, click Topics

    This displays any existing JMS topic destinations for the V5 default messaging provider in the content pane.

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

    1. Click New in the content pane.

    2. Specify the following required properties.

      Name

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

      JNDI Name

      The JNDI name used to bind the topic destination into the namespace.

      Topic

      The name of the topic in the default messaging provider, to which messages are sent.

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

  6. Change properties for the topic destination, according to the needs.

  7. Click OK.

  8. Save any changes to the master configuration.

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


Version 5 default messaging topic settings

 

Related tasks


Set a topic connection factory for V5 default messaging
Set V5 default messaging resources
Manage WAS V5 JMS use of messaging resources in later versions of WAS ND