Use this task to browse or change a JMS topic destination
for publish/subscribe messaging with WebSphere MQ as a 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
configure a JMS topic destination for use with WebSphere MQ as a messaging
provider, use the administrative console to complete the following
steps:
Procedure
- In the navigation pane, click .
- Select the WebSphere MQ 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.
- In the contents pane, under Additional Properties, click Topics
This displays a table listing any existing JMS topic destinations,
with a summary of their properties.
- 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 connection factory is known for administrative
purposes within IBM WebSphere Application Server.
- JNDI Name
- The JNDI name that is used to bind the connection factory 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.
- 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.