A JMS connection factory is used to create connections to the associated JMS 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.
In the administrative console page, to view this page click factory_name.
By default, connections created using this JMS connection factory in the server containers (for example, from an enterprise bean) are pooled using J2C connection pooling. You can modify the connection pool settings for this connection factory by selecting the Connection pool properties link in the Additional properties section of the administrative console panel.
The configuration of a container-managed authentication alias and mapping module on a connection factory are deprecated in release 6.0. You now set these properties in the bindings for the resource reference of the application. If you do not want to modify the bindings for an existing application, locate this connection factory in the J2C panels where you can still find these properties.
Configuration properties for this object. These property values are preserved even if the runtime environment is stopped then restarted. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.
The level to which this resource definition is visible; for example, the cell, node, cluster, or server level.
The scope displayed is for information only, and cannot be changed on this panel. If you want to browse or change this resource (or other resources) at a different scope, change the scope on the messaging provider settings panel, then click Apply, before clicking the link for the type of resource.
Required | Yes |
Data type | Text |
The name by which this resource is known for administrative purposes.
Required | Yes |
Data type | Text |
The JNDI name for the resource.
As a convention, use a JNDI name of the form jms/Name, where Name is the logical name of the resource. For more information about the use of JNDI and its syntax, see JNDI support in WebSphere Application Server.
Required | Yes |
Data type | Text |
An optional category string to use when classifying or grouping the resource.
Required | No |
Data type | Text |
The name of the service integration bus to connect to.
Required | Yes |
Data type | Custom |
The JMS client identifier needed for durable topic subscriptions on all connections created using this connection factory.
The preferred way to assign a client identifier is for it to be configured on the connection factory and transparently assigned to connections that the factory creates. Alternatively, an application can set the client identifier immediately after creating the connection.
For more information about the use of client identifiers, see the "Client identifiers" section of the JMS Specification.
Required | No |
Data type | Text |
The reliability applied to nonpersistent JMS messages sent using this connection factory.
Required | No |
Data type | Selection list |
Default | Express nonpersistent |
Range |
|
Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
You can override this property for individual JMS destinations by setting the Read ahead property on the JMS destination.
Required | No |
Data type | Selection list |
Default | Default |
Range |
|
The prefix of up to twelve characters used for names of temporary queues created by applications that use this connection factory.
The default for this property is null, which causes temporary queues to be named without any prefix.
Required | No |
Data type | Text |
The prefix of up to twelve characters used for names of temporary topics created by applications that use this connection factory.
_T<topic_prefix>_<messaging_engine_id><destination_id>
If the topic is to be used with WebSphere MQ, the topic prefix value should be a maximum of 12 characters.
The default for this property is null, which causes temporary topics to be named without any prefix.
Required | No |
Data type | Text |
Default | Null |
The name of the messaging engine used to store messages delivered to durable subscriptions for objects created from this JMS connection factory.
Required | No |
Data type | Text |
Default | Null |
The name of a target that identifies a group of messaging engines. Specify the type of target using the Target type property.
This indicates the name of one of the following types of targets, as indicated by the Target type property
Connections are load balanced across the available messaging engines that satisfy the selection criteria.
If want applications to be able to connect to any messaging engine in the bus, do not set this property.Required | No |
Data type | Text |
The type of target named in the Target property.
Required | No |
Data type | Selection list |
Range |
|
This property specifies the significance of the target group.
Required | No |
Data type | Selection list |
Default | Preferred |
Range |
|
The name of the protocol that resolves to a group of messaging engines.
If the selected messaging engine is in the same server as the application, a direct in-process connection is made and this transport chain property is ignored.
The transport chains represent network protocol stacks operating within a server. The name you specify must be one of the transport chains available in the server that hosts the messaging engine, as listed on the panel. The following transport chains are provided, but you can define your own transport chains on that panel.
Required | No |
Data type | Text |
Default | Null |
The list of comma separated endpoints used to connect to a bootstrap server.
To specify endpoint addresses, type a comma-separated list of endpoint triplets, each of the form host_name:port_number:chain_name where:
[2002:914:fc12:179:9:20:141:42]:7276:BootstrapBasicMessagingIf host_name is not specified, the default is localhost.
localhost:7276:BootstrapBasicMessaging
You can create other transport chains and specify them as part of the provider endpoints.
Required | No |
Data type | Text area |
The proximity of messaging engines that can accept connection requests, in relation to the bootstrap messaging engine.
Required | No |
Data type | Selection list |
Default | Bus |
Range |
|
This alias specifies a user ID and password to be used to authenticate connections to the JMS provider for application-managed authentication.
This property provides a list of the J2C authentication data entry aliases that have been defined to WebSphere Application Server. You can select a data entry alias to be used to authenticate the creation of a new connection to the JMS provider.
If you have enabled global security for WebSphere Application Server, select the alias that specifies the user ID and password used to authenticate the creation of a new connection to the JMS provider. The use of this alias depends on the resource authentication (res-auth) setting declared in the connection factory resource reference of an application component's deployment descriptors.
Required | No |
Data type | Selection list |
Whether or not the container logs that there is a missing transaction context when a connection is obtained.
Select this property to log connections being created without a transaction context.
Required | No |
Data type | Check box |
Default | Cleared |
Whether cached handles (handles held in instance variables in a bean) should be tracked by the container.
Required | No |
Data type | Check box |
Default | Cleared |
The authentication alias used during XA recovery processing.
This property provides a list of the J2C authentication data entry aliases that have been defined to WebSphere Application Server. You can select a data entry alias to be used to authenticate during XA recovery processing.
If you have enabled security for the associated service integration bus, select the alias that specifies the user ID and password used for XA recovery. This property must be set if bus security is enabled and XA transactions are to be used.
Required | No |
Data type | Selection list |
The reliability applied to persistent JMS messages sent using this connection factory.
Required | No |
Data type | Selection list |
Default | Reliable persistent |
Range |
|