Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage messaging with the default messaging provider > Configure resources for the default messaging provider
Configure a unified 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.
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). A unified 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.
This task contains an optional step for you to create a new connection factory if we have not already created the connection factory to configure.
Procedure
- Display the default messaging provider. In the navigation pane, click Resources -> JMS -> JMS providers .
- Select the default provider for which to configure a unified connection factory.
- Optional: Change the Scope check box to set the level at which the connection factory is to be visible.
- In the content pane, under the Additional properties heading, click Connection factories. This displays any existing connection factories in the content pane.
- If the connection factory is for use by client applications, display the properties of the JMS connection factory. To display an existing JMS connection factory, click one of the names listed.
Alternatively, 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 used to bind the connection factory into the namespace.
- 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.
- Review the other properties for the JMS connection factory, to check that the defaults are suitable.
If the connection factory is for use by client applications running outside of an application server, specify suitable provider endpoints. For more information about configuring provider endpoints, see Configure a connection to a non-default bootstrap server.
By default, connections created by using the connection factory in the server containers (for example, from an enterprise bean) are pooled by using Java EE Connector Architecture (JCA) connection pooling. We 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 Change connection pool settings with wsadmin.sh.
- Click OK.
- Save your changes to the master configuration.
Pass message payload by reference: Example code for producer and consumer applications
Pass message payload by reference: Usage scenarios and example code for forwarding applications
Pass message payload by reference: Potential benefits for each processing step
JMS connection factories and service integration
Why and when to pass the JMS message payload by reference
Configure JMS resources for point-to-point messaging
Configure JMS resources for publish/subscribe messaging
Configure a queue for the default messaging provider
Configure a connection to a non-default bootstrap server
Configure the messaging engine selection process for JMS applications
Configure a topic for the default messaging provider
Default messaging provider unified connection factory [Settings]