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 > Maintain (deprecated) v5 default messaging resources > Configure v5 default messaging resources
Configure 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...
Procedure
- In the navigation pane, click Resources > JMS ->JMS providers.
- Select the V5 default messaging provider for which you want to configure a topic destination.
- Optional: Change the Scope setting to the level at which the JMS destination is visible to applications. If you define a v5 JMS resource at the Cell scope level, all users in the cell can look up and use that JMS resource.
- 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.
- To browse or change an existing JMS topic destination, click its name in the list. Otherwise, to create a new topic destination...
Optional. Change properties for the topic destination, according to your needs.
- Click New in the content pane.
- Specify the following required properties. We can specify other properties, as described in a later step.
- 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.
- Click Apply. This defines the topic destination to WAS, and enables you to browse or change additional properties.
- Click OK.
- Save any changes to the master configuration.
- To have the changed configuration take effect, stop then restart the application server.
Related
Version 5 default messaging topic settings
Configure a topic connection factory for v5 default messaging
Configure v5 default messaging resources
Enable WAS v5.1 JMS usage of messaging resources in later versions of the product