Configure a queue connection factory for the default messaging provider
Configure a JMS queue connection factory for point-to-point messaging with the default messaging provider. This is intended more for backwards compatibility, as described in section 1.5 of the JMS 1.1 specification.
To configure a JMS queue 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 queue connection factory.
Tasks
- Display the default messaging provider. In the navigation pane, click...
Resources -> JMS -> JMS providers.
- Select the default provider for which we want to configure a queue connection factory.
- Optional: Change the Scope check box to set the level at which the connection factory is to be visible, according to our needs.
- In the content pane, under the Additional properties heading, click Queue connection factories. This displays any existing JMS queue connection factories for the default messaging provider in the content pane.
- 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
- Type the name of the service integration bus that the connection factory is to create connections to. This service integration bus hosts the destinations that the JMS queues and topics represent.
- Review the other Default messaging provider queue connection factory [Settings], 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 using the connection factory in the server containers (for example, from an enterprise bean) are pooled 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 the wsadmin tool.
- Click OK.
- Save changes to the master configuration.
Related:
JMS queue resources and service integration Restricting reply messages to the queue point that is local to the requesting application JMS connection factories and service integration Why and when to pass the JMS message payload by reference Pass message payload by reference: Potential benefits for each processing step Pass message payload by reference: Usage scenarios and example code for forwarding applications Pass message payload by reference: Example code for producer and consumer applications Configure a queue for the default messaging provider Configure JMS resources for point-to-point messaging Configure a connection to a non-default bootstrap server Configure the messaging engine selection process for JMS applications Default messaging provider queue connection factory [Settings] (ZOS) Administrative properties for JMS connections to a bus