Broker 10.5 | webMethods Broker Documentation | webMethods Broker Messaging Programmer's Guide | Introduction | Basics of webMethods Messaging | JMS API Programming Model | Administered Objects | Types of Administered Object | Connection Factories
 
Connection Factories
A connection factory is the object a client uses to create a connection with a JMS provider. It encapsulates the set of configuration parameters that a JMS administrator defines for a connection.
The type of connection factory determines whether a connection is made to a topic (in a publish-subscribe application), a queue (in a point-to-point application), or can be made to both (generic connection), and whether messages are managed like elements in a distributed transaction in the client application.
You use XA-based connection factories in JMS applications managed by an application server, in the context of a distributed transaction. You do not use XA-based connection factories in:
*Standalone JMS messaging applications
*webMethods C# messaging applications
Following are the types of connection factories:
*ConnectionFactory. The preferred connection factory object. This is a generic connection factory object, which can be used as either a QueueConnectionFactory or TopicConnectionFactory or both at run time.
Note:
The webMethods C# API only supports use of a generic ConnectionFactory. All other types of connection factory can only be used in JMS clients.
*QueueConnectionFactory. Used to make connections in a point-to-point application.
*TopicConnectionFactory. Used to make connections in a publish-subscribe application.
*XAConnectionFactory. A generic connection factory object, where the object can be used in a transactional context.
*XAQueueConnectionFactory. Used to make connections in a point-to-point application, where the object will be used in a transactional context.
*XATopicConnectionFactory. Used to make connections in a publish-subscribe application, where the object will be used in a transactional context.