WebSphere MQ Provider queue connection factory settings for application clients

Provider queue connection factory settings for application clients

To set the configuration properties of the selected queue connection factory for use with the MQSeries product JMS provider. These configuration properties control how connections are created between the JMS provider and WebSphere MQ.
To view this ACRCT page, click File > Open. After you browse for an EAR file, click Open. Expand the selected JAR file > Messaging Providers > WebSphere MQ Provider. Right click Queue Connection Factories, and click New.
The following fields are displayed on the General tab.

The property values specified must match the values specified when configuring WebSphere MQ for JMS resources.
See about configuring WebSphere MQ for JMS resources, see the WebSphere MQ Use Java section of the WebSphere MQ library.
In WebSphere MQ, names can have a maximum of 48 characters, with the exception of channels which have a maximum of 20 characters.

A queue connection factory for the JMS provider has the following properties.

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

Description

A description of this connection factory for admin purposes within IBM WAS.

Data type String
Default Null

JNDI Name

The application client run time uses this field to retrieve configuration information.

User ID

The user ID used, with the property, for authentication if the calling application does not provide a userid and password explicitly.
If we specify a value for the User ID property, also specify a value for the property.
The connection factory User ID and properties are used if the calling application does not provide a userid and password explicitly; for example, if the calling application uses the method createQueueConnection(). The JMS client flows the userid and password to the JMS server.

Data type String

The password used, with the User ID property, for authentication if the calling application does not provide a userid and password explicitly.
If we specify a value for the User ID property, also specify a value for the property.

Data type String
Default Null

Re-Enter

Confirms the password.

Queue Manager

The name of the MQSeries queue manager for this connection factory.
Connections created by this factory connect to that queue manager.

Data type String

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 host name

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

Whether the WebSphere MQ client connection or JNDI 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 we are using non-ASF nonpersistent, nondurable, nontransactional 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

JNDI 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 poses 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.

DIRECT

For WebSphere MQ Event Broker using DIRECT mode. DIRECT is a lightweight sockets protocol used in nontransactional, nondurable and nonpersistent Publish/Subscribe messaging. DIRECT only works for clients and message-driven beans using the non-ASF protocol.

QUEUED

QUEUED is a standard TCP protocol.

Recommended

Queue connection factory transport type

BINDINGS is faster by 30% or more, but it lacks security. When we have security concerns, BINDINGS is more desirable than CLIENT.

Topic connection factory transport type

DIRECT is the fastest type and should be used where possible. Use BINDINGS when you want to satisfy additional security tasks and the queue manager is local to the JMS client. QUEUED is the fallback for all other cases. WebSphere MQ 5.3 before CSD2 with the DIRECT setting can lose messages when used with message-driven beans and under load. This loss also happens with client-side applications unless the broker maxClientQueueSize is set to 0. We can set this to 0 with the command:
#wempschangeproperties WAS_nodeName_server1 -e default -o DynamicSubscriptionEngine -n maxClientQueueSize -v 0 -x executionGroupUUID
where executionGroupUUID can be found by starting the broker and looking in the Event Log/Applications for event 2201. This value is usually ffffffff-0000-0000-000000000000.

The WebSphere MQ 5.3 JMS cannot be used within WAS 6.1 because WAS 6.1 has a Java 5 runtime. Therefore, cross-memory connections cannot be established with WebSphere MQ 5.3 queue managers. This can result in a performance degradation if we were previously using WebSphere MQ 5.3 and BINDINGS for the connections and move to CLIENT network connections in migrating to WAS 6.1.

Client ID

The JMS client identifier used for connections to the MQSeries queue manager.

Data type String

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

See 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 references are available from the WebSphere MQ messaging multiplatform and platform-specific topics at the WebSphere MQ library.

Message Retention

Select this check box to specify that unwanted messages are to be left on the queue. Otherwise, unwanted messages are handled 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 handled according to their disposition options.

Temporary model

The name of the model definition used to create temporary connection factories if a connection factory does not already exist.

Data type String
Range 1 through 48 ASCII characters

Temporary queue prefix

The prefix used for dynamic queue naming.

Data type String

Fail if quiesce

Whether applications return from a method call if the queue manager has entered a controlled failure.

Data type Check box
Default Selected

Local Server Address

Local server address.

Data type String

Polling Interval

Interval, in milliseconds, between scans of all receivers during asynchronous message delivery

Data type Integer
Units Milliseconds
Default 5000

Rescan interval

Interval in milliseconds between which a topic is scanned to look for messages that have been added to a topic out of order.
This interval controls the scanning for messages that have been added to a topic out of order with respect to a WebSphere MQ browse cursor.

Data type Integer
Units Milliseconds
Default 5000

SSL cipher suite

Cipher suite to use for SSL connection to WebSphere MQ.
Set this property to a valid cipher suite provided by the JSSE provider. The value must match the CipherSpec specified on the SVRCONN channel as the Channel property.
Set this property, if we set the SSL Peer Name property.

SSL certificate store

List of zero or more Certificate Revocation List (CRL) servers used to check for SSL certificate revocation. If we specify a value for this property, use WebSphere MQ JVM at Java 2 version 1.4.
The value is a space-delimited list of entries of the form:
ldap: //hostname:[port]

A single slash (/) follows this value. If port is omitted, the default LDAP port of 389 is assumed. At connect-time, the SSL certificate presented by the server is checked against the specified CRL servers. For more information about CRL security, see the section "Working with Certificate Revocation Lists" in the WebSphere MQ Security book; for example at: http://publibfp.boulder.ibm.com/epubs/html/csqzas01/csqzas012w.htm#IDX2254.

SSL peer name

For SSL, a distinguished name skeleton that must match the name provided by the WebSphere MQ queue manager. The distinguished name is used to check the identifying certificate presented by the server at connection time.
If this property is not set, such certificate checking is performed.
The SSL peer name property is ignored if SSL Cipher Suite property is not specified.
Is a list of attribute name and value pairs separated by commas or semicolons. For example:
CN=QMGR.*, OU=IBM, OU=WEBSPHERE

The example given checks the identifying certificate presented by the server at connect-time. For the connection to succeed, the certificate must have a Common Name beginning QMGR., and must have at least two Organizational Unit names, the first of which is IBM and the second WEBSPHERE. Checking is not case-sensitive.
For more details about distinguished names and their use with WebSphere MQ, see the section "Distinguished Names" in the WebSphere MQ Security book.

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 the 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.

Data type Check box
Default Selected

Related tasks

Tuning the application serving environment

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	BINDINGS JNDI 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 poses 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. DIRECT For WebSphere MQ Event Broker using DIRECT mode. DIRECT is a lightweight sockets protocol used in nontransactional, nondurable and nonpersistent Publish/Subscribe messaging. DIRECT only works for clients and message-driven beans using the non-ASF protocol. QUEUED QUEUED is a standard TCP protocol.
Recommended	Queue connection factory transport type BINDINGS is faster by 30% or more, but it lacks security. When we have security concerns, BINDINGS is more desirable than CLIENT. Topic connection factory transport type DIRECT is the fastest type and should be used where possible. Use BINDINGS when you want to satisfy additional security tasks and the queue manager is local to the JMS client. QUEUED is the fallback for all other cases. WebSphere MQ 5.3 before CSD2 with the DIRECT setting can lose messages when used with message-driven beans and under load. This loss also happens with client-side applications unless the broker maxClientQueueSize is set to 0. We can set this to 0 with the command: #wempschangeproperties WAS_nodeName_server1 -e default -o DynamicSubscriptionEngine -n maxClientQueueSize -v 0 -x executionGroupUUID where executionGroupUUID can be found by starting the broker and looking in the Event Log/Applications for event 2201. This value is usually ffffffff-0000-0000-000000000000. The WebSphere MQ 5.3 JMS cannot be used within WAS 6.1 because WAS 6.1 has a Java 5 runtime. Therefore, cross-memory connections cannot be established with WebSphere MQ 5.3 queue managers. This can result in a performance degradation if we were previously using WebSphere MQ 5.3 and BINDINGS for the connections and move to CLIENT network connections in migrating to WAS 6.1.