Connection factory collection
A JMS connection factory is used to create connections to the associated messaging provider of JMS destinations, for both point-to-point and publish/subscribe messaging. Use connection factory administrative objects to manage JMS connection factories for the default messaging provider, the WebSphere® MQ messaging provider or a third-party messaging provider.
In the administrative console, to view this page click .
To browse or change the properties of a listed item, select its name in the list.
To act on one or more of the listed items, select the check boxes next to the names of the items that you want to act on, then use the buttons provided.
To change what entries are listed, or to change what information is shown for entries in the list, use the Filter settings.
A JMS connection factory is used to create connections to JMS destinations. When an application needs a JMS connection, an instance can be created by the factory of the messaging provider named in the Provider column of the list.
This type of connection factory is for
applications that use the JMS 1.1 domain-independent interfaces (referred to as the common
interfaces
in the JMS specification).
This type of JMS connection factory can also be used by the domain-specific (queue and topic) interfaces, as used in JMS 1.0.2, so applications can still use those interfaces without the need for you to create a domain-specific connection factory, such as a queue connection factory.
In a mixed release cell, these connection factories are only available for Version 7 and later nodes.
If WebSphere MQ functionality has been disabled, an informational message indicating that WebSphere MQ has been disabled appears when the scope field is set to a scope which is the same as, or above, the scope at which WebSphere MQ has been disabled, or when the scope field is set to display all scopes. Note that this informational message is not displayed if you are viewing a provider specific collection that is not for WebSphere MQ (for example, the default messaging provider collection). In a single server environment this informational message is only displayed when the server is restarted after WebSphere MQ functionality has been disabled. In a network deployment environment the informational message is displayed immediately.
- Name
- The display name of each connection factory instance.
- JNDI name
- The Java™ Naming and Directory Interface (JNDI) name of each connection factory instance.
- Provider
- The messaging provider that supports each connection factory instance. This is the default messaging provider (service integration), the WebSphere MQ messaging provider or a third-party messaging provider.
- Description
- An optional description of each connection factory instance.
- Scope
- The level to which this resource definition is visible; for example, the cell, node, cluster, or server level.