Configuring the messaging engine selection process for JMS applications
Configure the JMS connection factory for your application, in order to tune the process through which messaging engine connections are selected for your application.
About this task
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.
- 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. You can 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.