Generic JMS connection factory settings
Use this panel to view or change the configuration properties of the selected JMS connection factory for use with the associated JMS provider. These configuration properties control how connections are created to the associated JMS destination.
A JMS connection factory is used to create connections to JMS destinations. The JMS connection factory is created by the associated JMS provider. A JMS connection factory for a generic JMS provider (other than the embedded WebSphere JMS provider or the WebSphere MQ JMS provider) has the following properties:
To view this administrative console page, click Resources-> Generic JMS Providers-> provider_name-> JMS Connection Factories-> connection_factory
- Name
- The name by which this JMS connection factory is known for administrative
purposes within IBM WebSphere Application Server. The name must be unique
within the associated JMS provider.
Data type String - Type
- Whether this connection factory is for creating JMS queue destinations
or JMS topic destinations.
Select one of the following options:
- Queue
- A JMS queue connection factory for point-to-point messaging.
- Topic
- A JMS topic connection factory for publish/subscribe messaging.
- JNDI name
- The JNDI name that is used to bind the 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 - Description
- A description of this connection factory for administrative purposes
within IBM WebSphere Application Server.
Data type String Default Null - Category
- A category used to classify or group this connection factory, for
your IBM WebSphere Application Server administrative records.
Data type String - 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 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.
- 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 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.
- 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. This is independent from any WebSphere MQ connection pooling. 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. This is independent from any WebSphere MQ connection pooling. 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.
- Custom properties
- An optional set of name and value pairs for custom properties passed to the JMS provider.
Configuration tab
- Scope
- Specifies the 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 - 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 Configuration entry settings for Java Authentication and Authorization Service.
Data type Pick-list
Configuring a JMS connection factory, generic JMS provider
Managing J2EE Connector Architecture authentication data entries
Asynchronous messaging - security considerations
Tuning performance parameter index