Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage messaging with the default messaging provider > Configure resources for the default messaging provider > Configure a unified connection factory for the default messaging provider

Administrative properties for JMS connections to a bus

We can configure properties to enable workload management of connections to a service integration bus for JMS applications. The same properties can also be used to control the client connection topology. For example, connection options can be specified such that client applications only connect to a set of client serving messaging engines and never to the set of destination serving messaging engines in a bus.

The properties for connecting JMS applications to a bus are used by the administrator. The JMS applications do not specify how to connect to the bus, beyond using a JMS connection factory or JMS activation specification (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 is to use. Applications running inside an application server can locate a suitable messaging engine and connect directly to the selected messaging engine. Client applications running outside of an application server cannot locate a suitable messaging engine themselves, these clients must use a bootstrap server to locate a suitable messaging engine on behalf of the client application.

When an application connects to the bus, the bus chooses a suitable messaging engine based on administrative properties of the JMS connection factory or activation specification that the application uses. For maximum connection flexibility, you can leave most properties to default, the only required connection property is the name of the bus that the application is to connect to.

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.

The following rules are used to test the connection proximity for a selected messaging engine:

When a connection is made to a messaging engine in the same server as the application, the connection is made directly through memory, so the Remote transport chain is ignored.