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 we 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, we apply the extra configuration to the associated JMS connection factory. For a message-driven bean (MDB) application, we apply the equivalent extra configuration to the associated activation specification.

For the default configuration, we 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, we can also configure the other connection properties:

• Target
• Target type
• Target significance
• Target inbound transport chain
• Connection proximity

For detailed information about these connection properties, and an overview of the process through which the default messaging provider chooses the messaging engine for the application, see How JMS applications connect to a messaging engine on a bus.

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 we select the appropriate type of connection factory instead of JMS connection factory.

Tasks

• 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:

  1. Start the tool and open the EAR file for which we want to configure the JMS connection factory. The EAR file contents are displayed in a tree view.

  2. From the tree, select the JAR file in which we want to configure the JMS connection factory.

  3. Expand the JAR file to view its contents.

  4. Expand Messaging Providers > Default Provider > Connection Factories.

  5. Optional: 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.

       For more information about configuring a JMS connection factory in the JMS provider configuration for the application client, see Configure Java messaging client resources.

  6. On the General tab, configure the connection properties.

  7. Click OK.

  8. To save the changes, click File > Save.

• If the client application uses a JMS connection factory on the server, use the WebSphere Application Server administrative console to configure the connection properties:
  1. Display the default messaging provider. In the navigation pane, expand Resources -> JMS -> JMS providers.

  2. Optional: Change the Scope check box to set the level at which the connection factory is to be visible, according to our needs.

  3. 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.

  4. In the content pane, under Additional Properties, click Connection factories This displays any existing connection factories in the content pane.

  5. Optional: 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.

       For more information about configuring a JMS connection factory, see Configure a unified connection factory for the default messaging provider.

  6. Configure the connection properties.

  7. Click OK.

  8. Save changes to the master configuration.

Related:

How JMS applications connect to a messaging engine on a bus

JNDI namespaces and connecting to different JMS provider environments

Configure a unified connection factory for the default messaging provider

Configure a queue connection factory for the default messaging provider

Configure a topic connection factory for the default messaging provider