Configure a JMS connection factory for the generic JMS provider

Use this task to browse or change the properties of a JMS connection factory for use with a generic JMS provider (other than the default, V5 default or WebSphere MQ messaging providers).

Overview

To configure a JMS connection factory for use with a generic JMS provider, use the administrative console to complete the following steps:

Procedure

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

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

3. Optional: Change the Scope setting to the level at which the connection factory is visible to applications.

4. In the content pane, under Additional Properties, click Connection factories This displays a table listing any existing JMS connection factories, with a summary of their properties.

5. To browse or change an existing JMS 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 connection factory is known for administrative purposes within IBM WebSphere Application Server.

      Type

      Select whether the connection factory is for JMS queues (QUEUE) or JMS topics (TOPIC).

      JNDI Name

      The JNDI name that is used to bind the JMS connection factory into the WebSphere Application Server name space.

      External JNDI Name

      The JNDI name that is used to bind the JMS connection factory into the name space of the messaging provider.

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

6. Optional: Change properties for the JMS 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 application server.

Related tasks

Related Reference