WebSphere MQ queue connection factory settings

 

Overview

To change the configuration properties of a queue connection factory for use with the WebSphere MQ JMS provider, go to...

Resources | WebSphere MQ JMS Provider | WebSphere MQ Queue Connection Factories | connection_factory

A queue connection factory is used to create JMS connections to queue destinations.

Note that in WebSphere MQ, names can have a maximum of 48 characters, with the exception of channels which have a maximum of 20 characters.

 

Sets

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
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 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
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. If you want to use a WebSphere MQ JMS Provider JMS connection when using Bindings transport mode, you set the property Transport type=BINDINGS on the WebSphere MQ Queue Connection Factory. You must also choose one of the following options: To use security credentials, ensure that the user specified is the currently logged on user for the WAS process. If the user specified is not the current logged on user for the WAS process, then the WebSphere MQ JMS Bindings authentication throws the error MQJMS2013 invalid security authentication supplied for MQQueueManager. Do not specify security credentials. On the WebSphere MQ Connection Factory, ensure that both the Component-managed Authentication Alias and the Container-managed Authentication Alias properties are not set.
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. If you want to use a WebSphere MQ JMS Provider JMS connection when using Bindings transport mode, you set the property Transport type=BINDINGS on the WebSphere MQ Queue Connection Factory. You must also choose one of the following options: To use security credentials, ensure that the user specified is the currently logged on user for the WAS process. If the user specified is not the current logged on user for the WAS process, then the WebSphere MQ JMS Bindings authentication throws the error MQJMS2013 invalid security authentication supplied for MQQueueManager. Do not specify security credentials. On the WebSphere MQ Connection Factory, ensure that both the Component-managed Authentication Alias and the Container-managed Authentication Alias properties are not set.
Queue manager	The name of the WebSphere MQ queue manager for this connection factory. Connections created by this factory connect to that queue manager. Data type String Default Null Range A valid WebSphere MQ queue manager name, as 1 through 48 ASCII characters
Host	The name of the host on which the WebSphere MQ queue manager runs, for client connection only. Data type String Default Null Range A valid TCP/IP hostname
Port	The TCP/IP port number used for connection to the WebSphere MQ queue manager, for client connection only. 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.
Channel	The name of the channel used for connection to the WebSphere MQ queue manager, for client connection only. Data type String Default Null Range 1 through 20 ASCII characters
Transport type	Specifies whether the WebSphere MQ client connection or JNI bindings are used for connection to the WebSphere MQ queue manager. The external JMS provider controls the communication protocols between JMS clients and JMS servers. Tune the transport type when you are using non-ASF non-persistent, non-durable, non-transactional messaging or when you want to satisfy security issues and the client is local to the queue manager node. Data type Enum Units Not applicable Default BINDINGS Range BINDINGS JNI bindings are used to connect to the queue manager. BINDINGS is a shared memory protocol and can only be used when the queue manager is on the same node as the JMS client and comes at some security risks that should be addressed through the use of EJB roles. CLIENT WebSphere MQ client connection is used to connect to the queue manager. CLIENT is a typical TCP-based protocol. Recommended BINDINGS is faster by 30% or more, but it lacks security. When you have security concerns, BINDINGS is more desirable than CLIENT.
Model queue definition	The name of the model queue definition that can be used by the queue manager to create temporary queues if a queue requested does not already exist. Data type String Default Null Range 1 through 48 ASCII characters
Client ID	The JMS client identifier used for connections to the WebSphere MQ queue manager. Data type String Default Null
CCSID	The coded character set identifier for use with the WebSphere MQ queue manager. 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
Message retention	Select this check box to specify that unwanted messages are to be left on the queue. Otherwise, unwanted messages are dealt with according to their disposition options. Data type Enum Units Not applicable Default Cleared Range Selected Unwanted messages are left on the queue. Cleared Unwanted messages are dealt with according to their disposition options.
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 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 WAS. In WBI Server Foundation 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 XA The connection factory is for XA-coordination of messages NON_XA The connection factory is for non-XA coordination of messages 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	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.
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 WebSphere MQ. Use the Custom properties page to define the following WebSphere MQ SSL properties. These properties apply only if you set the property Transport type=CLIENT. SSLCIPHERSUITE SSLCRL SSLPEERNAME For more information about setting these properties, see the section SSL properties in the WebSphere MQ Using Java book.