Use this task to view or change the configuration of a JMS topic
destination for publish/subscribe messaging with the WebSphere® MQ messaging provider. This
task contains an optional step for you to create a new JMS topic destination.
About this task
To optimize performance, configure the topic destination
properties to best fit your applications. For more information, see Performance considerations for WebSphere MQ topic destinations.
To view or change
the configuration of a topic destination for use with the WebSphere MQ
messaging provider, use the administrative console to complete the following
steps:
Procedure
- In the navigation pane, click .
- Select the WebSphere MQ messaging provider for
the topic destination that you want to configure.
- Optional: Change the Scope setting
to the level at which the topic destination is visible to applications.
- In the contents pane, under Additional Properties, click Topics to
display a table of existing topic destinations, with a summary of their properties.
- To view or change the properties of an existing 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.
- Base Topic Name
- The name of the WebSphere MQ topic to which messages are sent.
- CCSID
- The coded character set identifier for use with the WebSphere MQ
queue manager; for example: 850. See the properties for the topic destination for more details.
- Click Apply. This defines
the topic destination to WebSphere Application Server, and enables you to
view 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.