Use this panel to view or change the configuration properties of the selected queue connection factory for use with the WebSphere MQ JMS provider. These configuration properties control how connections are created to the associated JMS queue destination.
A queue connection factory is used to create JMS connections to queue destinations. The queue connection factory is created by the WebSphere MQ JMS provider. A queue connection factory for the WebSphere MQ JMS provider has the following properties.
Note:
To view this administrative console page, click Resources-> WebSphere MQ JMS Provider-> (In content pane, under Additional Properties) WebSphere MQ Queue Connection Factories-> connection_factory
Data type | String |
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 |
Data type | String |
Default | Null |
Data type | String |
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:
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:
Data type | String |
Default | Null |
Range | A valid WebSphere MQ queue manager name, as 1 through 48 ASCII characters |
Data type | String |
Default | Null |
Range | A valid TCP/IP hostname |
This port must be configured on the WebSphere MQ queue manager.
Data type | Integer |
Default | Null |
Range | A valid TCP/IP port number, configured on the WebSphere MQ queue manager. |
Data type | String |
Default | Null |
Range | 1 through 20 ASCII characters |
Data type | Enum |
Units | Not applicable |
Default | BINDINGS |
Range |
|
Recommended | BINDINGS is faster by 30% or more, but it lacks security. When you have security concerns, BINDINGS is more desirable than CLIENT. |
Data type | String |
Default | Null |
Range | 1 through 48 ASCII characters |
Data type | String |
Default | Null |
This coded character set identifier (CCSID) must be one of the CCSIDs supported by WebSphere MQ.
Data type | String |
Units | Integer |
Default | Null |
Range | 1 through 65535 |
For more information about supported CCSIDs, and about converting between
message data from one coded character set to another, see the WebSphere
MQ System Administration and the WebSphere MQ Application Programming
Reference books. These are available from the WebSphere MQ messaging
multiplatform and platform-specific books Web pages; for example, at
http://www-3.ibm.com/software/ts/mqseries/library/manualsa/manuals/platspecific.html
,
the
IBM Publications Center
, or from
the WebSphere MQ collection kit, SK2T-0730.
Data type | Enum |
Units | Not applicable |
Default | Cleared |
Range |
|
If you set this property to NON_XA, 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.
Data type | Enum |
Units | Not applicable |
Default | XA enabled |
Range |
|
Recommended | Do not enable XA when the message queue received is the only resource in the transaction. Enable XA 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. 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.
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. 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.
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 |