Set a queue connection factory for V5 default messaging
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 dmgr 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 V5 applications, use the admin console to complete the following steps:
- In the navigation pane, click Resources > JMS > JMS providers .
- Select the V5 default messaging provider for which you want to configure a queue connection factory.
- Change the Scope setting to the level at which the JMS queue 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.
- 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.
- To browse or change an existing JMS queue connection factory, click its name in the list. Otherwise, to create a new connection factory...
- Click New in the content pane.
- Specify the following required properties. We can specify other properties.
- Name
- The name by which this JMS queue connection factory is known for administrative purposes within WAS.
- JNDI Name
- The JNDI name used to bind the JMS queue connection factory into the namespace.
- Click Apply. This defines the JMS queue connection factory to WAS, and enables you to browse or change additional properties.
- Change properties for the queue connection factory, according to the needs.
- Click OK.
- Save any changes to the master configuration.
- To have the changed configuration take effect, stop then restart the appserver.
Version 5 default messaging queue connection factory settings
Related tasks
Set a queue for V5 default messaging
Set V5 default messaging resources
Manage WAS V5 JMS use of messaging resources in later versions of WAS ND