WebSphere WebSphere Application Server Express, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Administrative options for JMS connections to a bus

This topic describes options that you can configure to enable workload management of connections to a service integration bus for JMS applications.

The options for connecting JMS applications to a bus are for administrator interest; the JMS applications are unconcerned with connections to the bus, beyond using a JMS connection factory or JMS activationSpec (for message-driven beans).

The general aim of connecting to a bus is to connect to a suitable messaging engine that provides the message point for a JMS destination that the application wants to use. When an application connects to the bus, the bus first makes a connection to a "bootstrap" messaging engine. The bus then chooses a suitable messaging engine based on administrative options provided by the properties of the JMS connection factory or activationSpec. If you do not want to use workload management of connections, you can leave the properties to default.

The bus uses the following general process to choose a suitable messaging engine, based on the value you select for the Connection proximity property. If you understand this process, you can better configure the properties that control how the bus chooses messaging engines.
  1. The bus looks for a suitable messaging engine in the same application server as the bootstrap messaging engine. If a suitable messaging engine is found, it is used.

    If a suitable messaging engine is not found, and Connection proximity is set to Server (the default), the bus fails the connection request. Otherwise, continue with the next step.

  2. The bus looks for a suitable messaging engine that uses the specified remote protocol, on the same host as the bootstrap messaging engine. If a suitable messaging engine is found, it is used.

    If a suitable messaging engine is not found, and Connection proximity is set to Host, the bus fails the connection request. Otherwise, continue with the next step.

  3. The bus looks for a suitable messaging engine that uses the specified remote protocol, in the same custom group as the bootstrap messaging engine. If a suitable messaging engine is found, it is used.

    If a suitable messaging engine is not found, and Connection proximity is set to Group, fail the connection request. Otherwise, continue with the next step.

  4. The bus looks for a suitable messaging engine that uses the specified remote protocol, on the same bus as the bootstrap messaging engine. If a suitable messaging engine is found, it is used.

    If a suitable messaging engine is not found, fail the connection request.

To configure how JMS applications connect to a service integration bus, set the following properties on the JMS connection factory or activationSpec:

If there are no active messaging engines that match the options specified, applications cannot use the connection factory or activationSpec to connect to the bus.

Related concepts
JMS connection factories and service integration
JMS queue resources and service integration
JMS topic resources and service integration
Related tasks
Configuring a unified JMS connection factory for the default messaging provider
Configuring a JMS queue connection factory, default messaging provider
Configuring a JMS topic connection factory, default messaging provider
Configuring a JMS activation specification, default messaging provider

Reference topic

Terms of Use | Feedback

Last updated: 2 Aug 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.express.doc\ui\ujb0001_.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)