+

Search Tips   |   Advanced Search

Set a topic connection factory for V5 default messaging


Use this task to browse or change a JMS topic connection factory for publish/subscribe messaging by WAS V5 applications.

To configure a JMS topic connection factory for use by WebSphere application server 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 connection factory.

  3. Change the Scope setting to the level at which the JMS topic connection factory 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 Topic connection factories This displays any existing JMS topic connection factories for the V5 messaging provider in the content pane.

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

    1. Click New in the content pane.

    2. Specify the following required properties. We can specify other properties.

      Name

      The name by which this JMS topic connection factory is known for administrative purposes within IBM WAS.

      JNDI Name

      The JNDI name used to bind the JMS topic connection factory into the namespace.

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

  6. Change properties for the topic connection factory, 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 connection factory settings

 

Related tasks


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