Configure the messaging engine selection process for JMS applications
Configure the JMS connection factory for the application, in order to tune the process through which messaging engine connections are selected for the application. To use JMS destinations of the default messaging provider, a client application connects to a messaging engine on the service integration bus to which the destinations are assigned. For example, a JMS queue is assigned to a queue destination on a service integration bus.
By default, the environment automatically connects applications to an available messaging engine on the bus. However you can specify extra configuration details to influence the connection process; for example to identify special bootstrap servers, or to limit connection to a subgroup of available messaging engines, or to improve availability or performance, or to ensure sequential processing of messages received.
- For a JMS application, you apply the extra configuration to the associated JMS connection factory.
- For a message-driven bean (MDB) application, you apply the equivalent extra configuration to the associated activation specification.
For the default configuration, you only have to specify the one required connection property, Bus name, which sets the name of the bus to which the application is to connect. To further restrict the range of messaging engines to which the applications can connect, you can also configure the other connection properties:
- Target
- Target type
- Target significance
- Target inbound transport chain
- Connection proximity
The steps for this task are based on an application that uses a unified JMS connection factory. Use the same task to configure a JMS queue connection factory or JMS topic connection factory, but you select the appropriate type of connection factory instead of JMS connection factory.
- If the client application uses a JMS connection factory in the client container, use the Client Resource Configuration tool (ACRCT) to configure the Provider endpoint property:
- Start the tool and open the EAR file for which you want to configure the JMS connection factory.
- From the tree, select the JAR file in which you want to configure the JMS connection factory.
- Expand the JAR file to view its contents.
- Expand...
Messaging Providers | Default Provider | Connection Factories- Display the general properties of the connection factory:
- To use an existing JMS connection factory, click the name of the connection factory.
- To create a new JMS connection factory, click New.
- On the General tab, configure the connection properties.
- Click OK.
- To save the changes, click File > Save.
- If the client application uses a JMS connection factory on the server, use the WAS admin console to configure the connection properties:
- Display the default messaging provider. In the navigation pane, expand...
Resources | JMS | JMS providers- 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 click Default messaging provider.
This displays a table of properties for the default messaging provider, including links to the types of JMS resources that it provides.
- In the content pane, click...
Additional Properties | Connection factories- Display the general properties of the connection factory:
- To use an existing JMS connection factory, click the name of the connection factory.
- To create a new JMS connection factory, click New.
- Configure the connection properties.
- Click OK.
- Save the changes to the master configuration.