Network Deployment (Distributed operating systems), v8.0 > Applications > Messaging resources > Default messaging
JMS connection factories and service integration
A JMS connection factory is used to create connections to JMS resources on a service integration bus.
A "domain-independent" JMS connection factory supports the JMS 1.1 domain-independent interfaces (sometimes referred to as the "unified" or "common" interfaces). This enables applications to use the same, common, interfaces for both point-to-point and publish/subscribe messaging. This also enables both point-to-point and publish/subscribe messaging within the same transaction.
Due to the interface inheritance defined by the JMS specification, a JMS 1.1 application can use a JMS 1.0.2b, domain-specific, connection factory. However, a JMS 1.0.2b application cannot use a JMS 1.1 domain-independent connection factory.
You should use the connection factory type that matches the JMS level and domain pattern in which an application is developed. For example, use a domain-independent JMS connection factory for a JMS application developed to use JMS 1.1 domain-independent interfaces, and use a JMS queue connection factory for a JMS application developed to use domain-specific queue interfaces.
Applications running in a server that is a member of a bus can locate a messaging engine in that bus. Client applications running outside of an application server - for example, running in a client container or outside the WAS environment - cannot locate directly a suitable messaging engine to connect to in the target bus. Similarly, an application running on a server in one cell to connect to a target bus in another cell cannot locate directly a suitable messaging engine to connect to in the target bus.
In these scenarios, the clients (or servers in another bus) must complete a bootstrap process through a bootstrap server that is a member of the target bus. A bootstrap server is an application server running the SIB Service, but does not have to be running any messaging engines. The bootstrap server selects a messaging engine that is running in an application server that supports the required target transport chain. For the bootstrap process to be possible, configure one or more provider end points in the connection factory used by the client.
JNDI namespaces and connecting to different JMS provider environments
Default messaging
Workload sharing with publish/subscribe messaging
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
Default messaging provider unified connection factory [Settings]
Default messaging provider queue connection factory [Settings]
Default messaging provider topic connection factory [Settings]
Concept topic