WebSphere MQ Provider connection factory settings for application clients

WebSphere MQ Provider connection factory settings for application clients

Use this panel to view or change the configuration properties of the selected connection factory for use with the MQSeries product Java Messaging Service (JMS) provider. These configuration properties control how connections are created to the associated JMS queue destination.
To view this Application Client Resource Configuration Tool (ACRCT) page, click File > Open. After you browse for an EAR file, click Open. Expand the selected JAR file > JMS Providers > JMS provider instance. Right click WebSphere MQ Provider Connection Factories, and click New. The following fields are displayed on the General tab. A queue connection factory creates JMS connections to queue destinations. The queue connection factory is created by the MQSeries product JMS provider. A queue connection factory for the JMS provider has the following properties.

The property values specified must match the values specified when configuring MQSeries for JMS resources. For more information about configuring MQSeries product JMS resources, see the MQSeries Use Java book, located in the WebSphere MQ Family library.

In MQSeries, names can have a maximum of 48 characters, with the exception of channels which have a maximum of 20 characters.

Related tasks

Tuning the application serving environment

Name

The required display name for the resource.

Data type String

Description

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

Data type String
Default Null

JNDI Name

The application client run time uses this field to retrieve configuration information. The name must match the value of the Name field on the General tab in the Application Client Resource Reference section of the Assembly Tool.

User

The user ID used, with the Password property, for authentication if the calling application does not provide a userid and password explicitly.
If you specify a value for the User ID property, 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 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

Password

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

Data type String
Default Null

Re-Enter Password

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

Specify 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 nonpersistent, nondurable, nontransactional messaging or when you want to satisfy security issues and the client is local to the queue manager node.
Data type String
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 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 is only works for clients and message-driven beans using the non-ASF protocol.
Recommended
DIRECT is the fastest transport 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. WebSphere MQ 5.3 before CSD2 with the DIRECT setting can lose messages when used with message-driven beans and under load. This also happens with client-side based applications unless the broker's maxClientQueueSize is set to 0. You can set this to 0 with the command
#wempschangeproperties WAS_nodeName_server1 
-e default 
-o DynamicSubscriptionEngine 
-n maxClientQueueSize 
-v 0 
-x executionGroupUUID
You can locate executionGroupUUID 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 you were previously using WebSphere MQ 5.3 and BINDINGS for your 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

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 references are available from the WebSphere MQ messaging multiplatform and platform-specific books Web pages; or from the IBM Publications Center, or the WebSphere MQ collection kit, SK2T-0730.

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

Broker Control Queue

The name of the broker control queue to which all command messages (except publications and requests to delete publications) are sent.

Data type String
Units En_US ASCII characters
Range 1 through 48 ASCII characters

Broker Queue Manager

The name of the MQSeries queue manager that provides the Publisher and Subscriber message broker.

Data type String
Units En_US ASCII characters
Range 1 through 48 ASCII characters

Broker Pub Queue

The name of the broker input queue that receives all publication messages for the default stream
The name of the broker's input queue (stream queue) that receives all publication messages for the default stream. Applications can also send requests to delete publications on the default stream to this queue.

Data type String
Units En_US ASCII characters
Range 1 through 48 ASCII characters

Broker Sub Queue

The name of the broker queue from which nondurable subscription messages are retrieved.
The name of the broker queue from which nondurable subscription messages are retrieved. The subscriber specifies the name of the queue when it registers a subscription.

Data type String
Units En_US ASCII characters
Range 1 through 48 ASCII characters

Broker CCSubQ

The name of the broker queue from which nondurable subscription messages are retrieved for a ConnectionConsumer request. This property applies only for use of the Web container.

Data type String
Units En_US ASCII characters
Range 1 through 48 ASCII characters

Broker Version

Specify whether the message broker is provided by the MQSeries MA0C SupportPac or newer versions of WebSphere family message broker products.

Data type Enum
Default Advanced
Range

Advanced

The message broker is provided by newer versions of WebSphere family message broker products (MQ Integrator and MQ Publish and Subscribe)

Basic

The message broker is provided by the MQSeries MA0C SupportPac (MQSeries - Publish and Subscribe)

Cleanup level

Level of cleanup provided by the Publish/Subscribe cleanup utility.

Data type Enum
Default SAFE
Range

ASPROP

NONE

STRONG

Cleanup interval

Specify the interval, in milliseconds, between background executions of the publish/subscribe cleanup utility.

Data type Integer
Units Milliseconds
Default 6000
Range

Message selection

Specify where Broker message selection is performed.

Data type Enum
Default BROKER
Range

BROKER

Message selection is done at the broker location.

Message CLIENT

Message selection is done at the client location.

Publish acknowledge interval

The interval, in number of messages, between publish requests that require acknowledgement from the broker.

Data type Integer
Default 25
Range

Sparse subscriptions

Enables sparse subscriptions.

Data type Check box
Default Deselected

Status refresh interval

The interval, in milliseconds, between transactions to refresh publish or subscribe status.

Data type Integer
Default 6000

Subscription store

Specify where WebSphere MQ stores data relating to active JMS subscriptions.

Data type Enum
Default MIGRATE
Range

MIGRATE

QUEUE

BROKER

Multicast

Specify whether this connection factory uses multicast transport.

Data type Enum
Default AS_CF
Range

AS_CF

This connection factory uses multicast transport.

DISABLED

This connection factory does not use multicast transport.

NOT_RELIABLE

This connection factory always uses multicast transport.

RELIABLE

This connection factory uses multicast transport when the topic destination is not relable.

ENABLED

This connection factory uses reliable multicast transport.

Direct authentication

Specify whether to use direct broker authorization.

Data type Enum
Default NONE
Range

NONE

Direct broker authorization is not used.

PASSWORD

Direct broker authorization is authenticated with a password.

CERTIFICATE

Direct broker authorization is authenticated with a certificates.

Proxy host name

Specify the host name of a proxy to be used for communication with WebSphere MQ.

Data type String
Range

Proxy port

Port number of a proxy to be used for communication with WebSphere MQ.

Data type Integer
Default 0
Range

Fail if quiesce

Specify 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

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

Data type Integer
Units Milliseconds
Default 5000
Range

Rescan interval

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

Data type Integer
Units Milliseconds
Default 5000
Range

SSL cipher suite

Specify the cipher suite to use for SSL connection to WebSphere 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.
Set this property, if you set the SSL Peer Name property.

SSL certificate store

Specify 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, 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. This property 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

Specify 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. We 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.

Data type Check box
Default Selected

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	Cleared
Range	Selected Unwanted messages are left on the queue. Cleared Unwanted messages are handled according to their disposition options.