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
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
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.
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 |
Data type | String |
Default | Null |
Data type | String |
Default | Null |
Data type | String |
Data type | Enum |
Default | Null |
Range | Pull-down list of nodes in the WebSphere administrative domain. |
Note: 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 |
The TCP/IP port numbers for these ports are defined on the WebSphere Internal JMS Server. |
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.
Note: 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.
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.
Note: 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.
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 Configuration entry settings for Java Authentication and Authorization Service.
Data type | Pick-list |
Data type | Enum |
Default | Cleared |
Range |
|
If you select this property, you must also specify a value for the Client ID property.
Data type | String |
Range | A valid JMS client ID |
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 WebSphere Application Server Enterprise
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 |
|
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 properties are common to all J2C connectors.
The application server 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.
This link provides a panel of optional connection pool properties, common to all J2C connectors.
The application server 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.