Configure a Version 5 queue connection factory

Configuring a Version 5 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 Version 5 node in the deployment manager cell. This task contains an optional step for you to create a new JMS queue connection factory.

To configure a JMS queue connection factory for use by WebSphere application server Version 5 applications, use the administrative console to complete the following steps:

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

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

  3. In the content pane, under Additional Properties, click WebSphere queue connection factories This displays any existing JMS queue connection factories for the Version 5 messaging provider in the content pane.

  4. 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 WebSphere Application Server.

      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 WebSphere Application Server, and enables you to browse or change additional properties.

  5. Optional: Change properties for the queue connection factory, according to your needs.

  6. Click OK .

  7. Save any changes to the master configuration.

  8. To have the changed configuration take effect, stop then restart the application server.



Related tasks
Configuring a Version 5 WebSphere queue destination
Configuring Version 5 default JMS resources
Managing WebSphere Version 5 JMS use of WebSphere version 6 JMS resources

Related reference
Version 5 WebSphere queue connection factory settings



Searchable topic ID: tmj_adm21