V5 WebSphere queue connection factory settings

V5 WebSphere queue connection factory settings

Use this panel to browse or change the configuration properties of the selected JMS queue connection factory for point-to-point messaging for use by WAS V5 applications.
A WebSphere queue connection factory is used to create JMS connections to the default messaging provider for use by WAS V5 applications. To view this page, use the console to complete the following steps:

In the navigation pane, click Resources > JMS Providers > V5 Default Messaging .

(Optional) In the content pane, change the Scope setting to the level at which JMS resources are visible to applications. If you define a V5 JMS resource at the Cell scope level, all users in the cell can look up and use that JMS resource.

Under Additional Resources, click WebSphere queue connection factories. This displays a list of any existing JMS queue connection factories.

Click the name of the JMS queue connection factory to work with.

A queue connection factory for the embedded WebSphere JMS provider has the following properties:

Configuration tab

Scope

Level to which this resource definition is visible to applications.
Resources such as messaging providers, namespace bindings, or shared libraries can be defined at multiple scopes, with resources defined at more specific scopes overriding duplicates which are defined at more general scopes.
The scope displayed is for information only, and cannot be changed on this panel. 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.

Data type String

Name

The name by which this JMS queue connection factory is known for administrative purposes within IBM WAS. The name must be unique within the JMS connection factories across the WebSphere administrative domain.

Data type String
Default Null

JNDI name

The JNDI name that is used to bind the JMS connection factory into the name space.
As a convention, use the fully qualified JNDI name; for example, in the form jms/Name, where Name is the logical name of the resource.
This name is used to link the platform binding information. The binding associates the resources defined by the deployment descriptor of the module to the actual (physical) resources bound into JNDI by the platform.

Data type String

Description

A description of this connection factory for administrative purposes within IBM WAS.

Data type String
Default Null

Category

A category used to classify or group this connection factory, for your IBM WAS administrative records.

Data type String

Node

The WebSphere node name of the administrative node where the JMS server runs for this connection factory. Connections created by this factory connect to that JMS server.

Data type Enum
Default Null
Range Pull-down list of V5 nodes in the WebSphere administrative domain.

Component-managed Authentication Alias

This alias specifies a user ID and password to be used to authenticate connection to the messaging provider for application-managed authentication.
This property provides a list of the J2C authentication data entry aliases defined to WAS. 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 administrative security for WAS, select the alias that specifies the user ID and password used to authenticate the creation of a new connection to the messaging 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.
User IDs longer than 12 characters cannot be used for authentication with the V5 default messaging provider. For example, the default Windows NT user ID, Administrator, is not valid because it contains 13 characters. Therefore, an authentication alias for a WebSphere queue connection factory must specify a user ID no longer than 12 characters.

Container-managed Authentication Alias

This alias specifies a user ID and password to be used to authenticate connection to the messaging provider for container-managed authentication.
This field is deprecated in 6.0. The specification of a login configuration and associated properties on the component resource reference determines the container-managed authentication strategy when the res-auth value is Container. If the 'DefaultPrincipalMapping' login configuration is used, the associated property is a container-managed authentication alias. This field is used only in the absence of a loginConfiguration on the component resource reference. To define a new alias, see the related item J2EE Connector Architecture (J2C) authentication data entries.
This property provides a list of the J2C authentication data entry aliases defined to WAS. 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 administrative security for WAS, select the alias that specifies the user ID and password used to authenticate the creation of a new connection to the messaging 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.
User IDs longer than 12 characters cannot be used for authentication with the V5 default messaging provider. For example, the default Windows NT user ID, Administrator, is not valid because it contains 13 characters. Therefore, an authentication alias for a WebSphere topic connection factory must specify a user ID no longer than 12 characters.

Mapping-Configuration Alias

The module used to map authentication aliases.
This field is deprecated in 6.0. The specification of a login configuration and associated properties on the component resource reference determines the container-managed authentication strategy when the res-auth value is Container. This field is used only in the absence of a loginConfiguration on the component resource reference.
This field provides a list of the modules configured on the Security > JAAS Configuration > Application Logins Configuration property. For more information about the mapping configurations, see Java Authentication and Authorization service configuration entry settings.

Data type Enum
Default Null
Range

ClientContainer

The client container maps authentication aliases.

WSLogin

The WSLogin module maps authentication aliases.

DefaultPrincipalMapping

The JAAS configuration maps an authentication alias to its userid and password.

XA Enabled

Specify whether the connection factory is for XA or non-XA coordination of messages and controls if the appserver uses XA QCF/TCF. Enable XA if multiple resources are used in the same transaction.
If you clear this checkbox property (for non-XA coordination), the JMS session is still enlisted in a transaction, but uses the resource manager local transaction calls (session.commit and session.rollback) instead of XA calls. This can lead to an improvement in performance. However, this means that only a single resource can be enlisted in a transaction in WebSphere Application Server.
Last participant support enables you to enlist one non-XA resource with other XA-capable resources.
For a WebSphere Topic Connection Factory with the Port property set to DIRECT this property does not apply, and always adopts non-XA coordination.

Data type Checkbox
Default Selected (enabled for XA coordination)
Range

Selected

The connection factory is enabled for XA-coordination of messages

Cleared

The connection factory is not enabled for XA coordination of messages

Recommended Do not enable XA coordination when the message queue or topic received is the only resource in the transaction. Enable XA coordination when other resources, including other queues or topics, are involved.

Connection pool

Specify an optional set of connection pool settings.
Connection pool properties are common to all J2C connectors.
The appserver pools connections and sessions with the messaging provider to improve performance. We need to configure the connection and session pool properties appropriately for your applications, otherwise you may not get the connection and session behavior that you want.
Change the size of the connection pool if concurrent server-side access to the JMS resource exceeds the default value. The size of the connection pool is set on a per queue or topic basis.

Session pool

An optional set of session pool settings.
This link provides a panel of optional connection pool properties, common to all J2C connectors.
The appserver pools connections and sessions with the messaging provider to improve performance. We need to configure the connection and session pool properties appropriately for your applications, otherwise you may not get the connection and session behavior that you want.

Sub-topics

Session pool settings

Related tasks

Configure a V5 queue connection factory

Related Reference
Connection pool settings
Java 2 Connector authentication data entry settings

Reference topic

Data type	Enum
Default	Null
Range	Pull-down list of V5 nodes in the WebSphere administrative domain.

Data type	Checkbox
Default	Selected (enabled for XA coordination)
Range	Selected The connection factory is enabled for XA-coordination of messages Cleared The connection factory is not enabled for XA coordination of messages
Recommended	Do not enable XA coordination when the message queue or topic received is the only resource in the transaction. Enable XA coordination when other resources, including other queues or topics, are involved.