Use this task to browse or change the properties of a JMS
topic destination for publish/subscribe messaging by WebSphere® Application Server Version 5 applications.
This task contains an optional step for you to create a new topic
destination.
About this task
To optimize performance, configure the
topic destination properties to best fit your applications. For more
information, see Performance for Version 5 default messaging topics.
To
configure a JMS topic destination for use WebSphere Application Server Version 5 applications,
use the administrative console to complete the following steps:
Procedure
- In the navigation pane, click .
- 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 Version 5 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 Version 5 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,
complete the following steps:
- Click New in the content pane.
- Specify the following required properties. You 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® WebSphere Application Server.
- JNDI Name
- The JNDI name that is 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 WebSphere Application Server, and enables you
to browse or change additional properties.
- Optional: Change properties for the topic destination, according
to your needs.
- Click OK.
- Save any changes to the master configuration.
- To have the changed configuration take effect, stop then
restart the application server.