WebSphere topic connection factory settings

Use this panel to view or change the configuration properties of the selected topic connection factory for use with the embedded WebSphere JMS provider. These configuration properties control how connections are created to the associated JMS topic destination.

A topic connection factory is used to create JMS connections to topic destinations. The topic connection factory is created by the associated JMS provider. A topic connection factory for the embedded WebSphere JMS provider has the following properties.

To view this administrative console page, click Resources-> WebSphere JMS Provider-> (In content pane, under Additional Properties) WebSphere Topic Connection Factories-> connection_factory

JNDI name

The JNDI name that is used to bind the topic connection factory into the appserver's 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

 

Configuration tab

Scope	Level to which this resource definition is visible -- the cell, node, or server level. Resources such as JMS 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. Note that no matter what the scope of a defined resource, the resource's properties only apply at an individual server level. For example, if you define the scope of a data source at the Cell level, all users in that Cell can look up and use that data source, which is unique within that Cell. However, resource property settings are local to each server in the Cell. For example, if you set Max Connections to 10, then each server in that Cell can have 10 connections. Cell The most general scope. Resources defined at the Cell scope are visible from all Nodes and servers, unless they are overridden. To view resources defined in the cell scope, do not specify a server or a node name in the scope selection form. Node The default scope for most resource types. Resources defined at the Node scope override any duplicates defined at the Cell scope and are visible to all servers on the same node, unless they are overridden at a server scope on that node. To view resources defined in a node scope, do not specify a server, but select a node name in the scope selection form. Server The most specific scope for defining resources. Resources defined at the Server scope override any duplicate resource definitions defined at the Cell scope or parent Node scope and are visible only to a specific server. To view resources defined in a server scope, specify a server name as well as a node name in the scope selection form. When resources are created, they are always created into the current scope selected in the panel. To view resources in other scopes, specify a different node or server in the scope selection form. Data type String
Name	The name by which this 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
Description	A description of this topic connection factory for administrative purposes within IBM WAS. Data type String Default Null
Category	A category used to classify or group this topic 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 nodes in the WebSphere administrative domain.
Port	Which of the two ports that connections use to connect to the JMS Server. The QUEUED port is for full-function JMS publish/subscribe support, the DIRECT port is for non-persistent, non-transactional, non-durable subscriptions only. Note that Message-driven beans cannot use the direct listener port for publish/subscribe support. Therefore, any topic connection factory configured with Port set to Direct cannot be used with message-driven beans. Data type Enum Units Not applicable Default QUEUED Range QUEUED The listener port used for full-function JMS-compliant, publish/subscribe support. DIRECT The listener port used for direct TCP/IP connection (non-transactional, non-persistent, and non-durable subscriptions only) for publish/subscribe support. The TCP/IP port numbers for these ports are defined on the WebSphere Internal JMS Server.
Component-managed Authentication Alias	This alias specifies a user ID and password to be used to authenticate connection to a JMS provider for application-managed authentication. This property provides a list of the J2C authentication data entry aliases that have been 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 global security for WAS, 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. Note that User IDs longer than 12 characters cannot be used for authentication with the embedded WebSphere JMS provider. For example, the default Windows NT user ID, Administrator, is not valid for use with embedded WebSphere messaging, because it contains 13 characters. Therefore, an authentication alias for a WebSphere JMS provider 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 a JMS provider for container-managed authentication. This property provides a list of the J2C authentication data entry aliases that have been 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 global security for WAS, 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. Note that User IDs longer than 12 characters cannot be used for authentication with the embedded WebSphere JMS provider. For example, the default Windows NT user ID, Administrator, is not valid for use with embedded WebSphere messaging, because it contains 13 characters. Therefore, an authentication alias for a WebSphere JMS provider connection factory must specify a user ID no longer than 12 characters.
Mapping-Configuration Alias	Allows users to select from the Security > JAAS Configuration > Application Logins Configuration list. The DefaultPrincipalMapping JAAS configuration maps the authentication alias to the userid and password. You may define and use other mapping configurations. For more information about the mapping configurations, see Warning: no string named [usecjaas] found.. Data type Pick-list
Clone Support	Select this checkbox to enable clone support to allow the same durable subscription across topic clones. Data type Enum Default Cleared Range Selected Clone support is enabled. Cleared Clone support is disabled. If you select this property, also specify a value for the Client ID property.
Client ID	The JMS client identifier used for connections to the queue manager. Data type String Range A valid JMS client ID
XA Enabled	Specifies 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 not 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. In WBI Server Foundation the 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	Specifies an optional set of connection pool settings. Connection pool properties are common to all J2C connectors. The appserver pools connections and sessions with the JMS provider to improve performance. You 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. See the following table for details.
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 JMS provider to improve performance. You 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.