IBM MQ Provider queue connection factory settings for application clients

The name by which this queue connection factory is known for administrative purposes within WebSphere® Application Server. The name must be unique within the JMS connection factories across the WebSphere administrative domain.

A description of this connection factory for administrative purposes within WebSphere Application Server.

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

The user ID used, with the password property, for authentication if the calling application does not provide a user ID and password explicitly.

If you specify a value for the user ID property, you must also specify a value for the password property.

The connection factory user ID and password properties are used if the calling application does not provide a user ID and password explicitly; for example, if the calling application uses the method createQueueConnection(). The JMS client flows the user ID and password to the JMS server.

The password used, with the user ID property, for authentication if the calling application does not provide a user ID and password explicitly.

If you specify a value for the user ID property, you must also specify a value for the password property.

Confirms the password.

The name of the IBM MQ queue manager for this connection factory.

Connections created by this factory connect to that queue manager.

This radio button is selected by default and, if selected, enables the host and port properties and disables the connection name list property.

The name of the host on which the IBM MQ queue manager runs for client connection only.

The TCP/IP port number used for connection to the IBM MQ queue manager, for client connection only.

This port must be configured on the IBM MQ queue manager.

If selected, this radio button enables the connection name list property and disables the host and port name properties. Select this radio button if you want to connect to a multi-instance queue manager.

A comma-separated list of host and port information which can be used to connect to a multi-instance queue manager.

host[(port)],[host[(port)]]

hostname1,hostname2(1415)

For further information about multi-instance queue managers, see the IBM MQ documentation.

This property must only be used for connecting to a multi-instance queue manager. It must not be used for connecting to a list of distinct queue managers as that can result in transaction integrity issues.

The name of the channel used for connection to the IBM MQ queue manager, for client connection only.

Specifies whether the IBM MQ client connection or JNDI bindings are used for connection to the IBM 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 nonpersistent, nondurable, nontransactional messaging or when you want to satisfy security issues and the client is local to the queue manager node.

Information	Value
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 must be addressed through the use of EJB roles. CLIENT IBM MQ client connection is used to connect to the queue manager. CLIENT is a typical TCP-based protocol. DIRECT For IBM 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 requires correctly set up EJB roles to guarantee security. If you have security concerns and need to use CLIENT then you should make appropriate use of SSL to secure the connection to the queue manager. Topic connection factory transport type DIRECT is the fastest type and must 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. IBM 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. You can set this value 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. Note: The IBM MQ 5.3 JMS cannot be used within WebSphere Application Server Version 6.1 because WebSphere Application Server Version 6.1 has a Java 5 runtime. Therefore, cross-memory connections cannot be established with IBM MQ 5.3 queue managers. This can result in a performance degradation if you were previously using IBM MQ 5.3 and BINDINGS for your connections and move to CLIENT network connections in migrating to WebSphere Application Server Version 6.1. If you are using IBM MQ 5.3 for z/OS®, you might also need to install an additional feature pack.

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

The coded character set identifier for use with the IBM MQ queue manager.

This coded character set identifier (CCSID) must be one of the CCSIDs supported by IBM MQ.

For more information about supported CCSIDs, and about converting between message data from one coded character set to another, see the System Administration and Application Programming Reference sections of the IBM MQ information center.

Select this check box to specify that unwanted messages are to remain on the queue. Otherwise, unwanted messages are handled according to their disposition options.

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

The prefix used for dynamic queue naming.

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

Specifies the local server address.

Specifies the interval, in milliseconds, between scans of all receivers during asynchronous message delivery

Specifies the 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 an IBM MQ browse cursor.

Specifies the cipher suite to use for SSL connection to IBM MQ.

Set this property to a valid cipher suite provided by your JSSE provider. The value must match the CipherSpec specified on the SVRCONN channel as the Channel property.

You must set this property, if you set the SSL Peer Name property.

Specifies a list of zero or more Certificate Revocation List (CRL) servers used to check for SSL certificate revocation. If you specify a value for this property, you must use IBM MQ JVM at Java 2 version 1.4.

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 information about Working with Certificate Revocation Lists in the Security section of the IBM MQ documentation.

For SSL, a distinguished name skeleton that must match the name provided by the IBM 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.

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 IBM MQ, see the information about Distinguished Names in the IBM MQ documentation.

Specifies an optional set of connection pool settings.

Connection pool properties are common to all J2C connectors.

The application server pools connections and sessions with the JMS provider to improve performance. This connection pooling is independent from any IBM MQ connection pooling. You must configure the connection and session pool properties appropriately for your applications, otherwise you might 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.

Specifies whether a client mode connection reconnects automatically, or not, in the event of a communications or queue manager failure. This property is ignored unless the connection factory is being used in a thin or managed client environment.

For more information about automatic client reconnection, see the IBM MQ documentation.

The maximum number of seconds that a client mode connection spends attempting to automatically reconnect to a queue manager after a communications or queue manager failure. This parameter is ignored unless the connection factory is being used in a thin or managed client environment. Whether this parameter is used or not depends on the value of the client reconnect options parameter.

For more information about automatic client reconnection, see the IBM MQ documentation.