WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Configuring a unified JMS connection factory for the default messaging provider

Use this task to configure a unified JMS connection factory for applications that use the JMS 1.1 domain-independent (unified) interfaces.

A unified1 JMS connection factory can be used for both point-to-point and publish/subscribe JMS messaging. With JMS 1.1, this approach is preferred to the domain-specific queue connection factory and topic connection factory.

To configure a JMS connection factory for the default messaging provider, use the administrative console to complete the following steps. This task contains an optional step for you to create a new connection factory if you have not already created the connection factory that you want to configure.

  1. Display the default messaging provider. In the navigation pane, expand Resources > JMS Providers > Default messaging. This displays in the content pane a table of properties for the default messaging provider, including links to the types of JMS resources that it provides.
  2. Optional: Change the Scope check box to set the level at which the connection factory is to be visible, according to your needs.
  3. In the content pane, under the Connection factories heading, click JMS connection factory. This displays any existing connection factories in the content pane.
  4. Display the properties of the JMS connection factory. If you want to display an existing JMS connection factory, click one of the names listed.

    Alternatively, if you want to create a new JMS connection factory, click New, then specify the following required properties:

    Name
    Type the name by which the connection factory is known for administrative purposes.
    JNDI name
    Type the JNDI name that is used to bind the connection factory into the name space.
    Bus name
    Select the name of the service integration bus to which the connection factory is to create connections. This service integration bus hosts the destinations that the JMS queues and topics represent.
  5. Review the other properties for the JMS connection factory, to check that the defaults are suitable. If needed, change the values according to your needs.

    If the connection factory is for use by client applications running outside of an application server, you need to specify suitable provider endpoints. For more information about configuring provider endpoints, see Configuring connection to a non-default bootstrap server.

    By default connections created using the connection factory in the server containers (for example, from an enterprise bean) are pooled using J2C connection pooling. You can modify the connection pool settings for the connection factory by selecting the Connection pool properties link in the Additional Properties section of the panel. For more information about changing the connection pool properties, see Changing connection pool settings with the wsadmin tool.

  6. Click OK.
  7. Save your changes to the master configuration.
Related concepts
JMS connection factories and service integration
Related tasks
Configuring JMS resources for point-to-point messaging
Configuring JMS resources for publish/subscribe messaging
Configuring a JMS queue, default messaging provider
Configuring connection to a non-default bootstrap server
Configuring the messaging engine selection process for applications
Configuring a JMS topic, default messaging provider
Related information
JMS connection factory settings
Administrative options for JMS connections to a bus
1 The term "unified" refers to the support of both queues and topics by the same connection factory. This is similar to the JMS 1.1 domain-independent interfaces (referred to as the "common interfaces" in the JMS specification).

Task topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tjn0001_.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)