Configure a topic connection factory for the default messaging provider
Use this task to configure a JMS topic connection factory for publish/subscribe 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.
You configure JMS connection factories when you deploy JMS applications that use publish/subscribe messaging.
This task contains an optional step for you to create a new topic connection factory.
- Display the default messaging provider. In the navigation pane, click Resources -> JMS -> JMS providers.
- Select the default provider for which to configure a topic connection factory.
- Optional: Change the Scope check box to set the level at which the connection factory is to be visible, according to the needs.
- In the content pane, under the Additional properties heading, click Topic connection factories. This displays any existing JMS topic connection factories for the default messaging provider in the content pane.
- Optional: 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 properties for the 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 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 the changes to the master configuration.
Related concepts
JMS connection factories and service integration JMS topic resources 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
Related tasks
Configure a topic for the default messaging provider Configure JMS resources for publish/subscribe messaging Configure a connection to a non-default bootstrap server Configure the messaging engine selection process for JMS applications
Related information:
Default messaging provider topic connection factory [Settings] (zos) Administrative properties for JMS connections to a bus