+

Search Tips   |   Advanced Search

 

Configure a V5 queue connection factory

 

Use this task to browse or change the properties of a JMS queue connection factory for point-to-point messaging with the default messaging provider on a V5 node in a deployment manager cell. This task contains an optional step for you to create a new JMS queue connection factory.

 

Overview

To configure a JMS queue connection factory for use by WebSphere appserver V5 applications, use the console to complete the following steps:

 

Procedure

  1. Display the V5 default messaging provider. In the navigation pane, expand Resources > JMS > JMS Providers.

  2. Select the V5 provider for which you want to configure a queue connection factory.

     

  3. Optional: Change the Scope setting to the level at which the JMS queue connection factory 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.

  4. In the content pane, under Additional Properties, click Queue connection factories This displays any existing JMS queue connection factories for the V5 messaging provider in the content pane.

  5. To browse or change an existing JMS queue connection factory, click its name in the list. Otherwise, to create a new connection factory, complete the following steps:

    1. Click New in the content pane.

    2. Specify the following required properties. You can specify other properties, as described in a later step.

      Name

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

      JNDI Name

      The JNDI name that is used to bind the JMS queue connection factory into the name space.

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

     

  6. Optional: Change properties for the queue connection factory, according to your 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.

 

Related tasks


Configure a V5 WebSphere queue destination
Configure V5 default JMS resourcesManaging WebSphere V5 JMS use of WebSphere V6 messaging resources

 

Related Reference

V5 WebSphere queue connection factory settings