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 WebSphere MQ queue connection factory is used to create JMS connections to queues provided by WebSphere MQ for point-to-point messaging.
The JNDI name that is used to bind the connection factory into the 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 |
A description of this connection factory for administrative purposes within IBM WebSphere Application Server.
Data type | String |
Default | Null |
Whether or not unwanted messages are left on the queue. If this option is not enabled, unwanted messages are dealt with according to their disposition options.
Data type | Enum |
Default | Selected |
Range |
|
The cipher suite to use for SSL connection to WebSphere MQ.
Set this property to a valid cipher suite provided by your JSSE provider; it must match the CipherSpec named on the SVRCONN channel named by the Channel property.
You must set this property if the SSL Peer Name property is to be set.
A list of zero or more Certificate Revocation List (CRL) servers used to check for SSL certificate revocation. (Use of this property requires a WebSphere MQ JVM at Java 2 version 1.4.)
ldap://hostname:[port]
optionally followed by a single / (forward slash). 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.
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 connect-time.
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 WebSphere MQ, see the WebSphere MQ Security book in the WebSphere MQ library at: http://www.ibm.com/software/integration/wmq/library/.
The prefix that is used for names of temporary JMS queues created by applications that use this connection factory.
Data type | String |
Default | Null |
Whether or not to use WebSphere MQ connection pooling.
For more information on WebSphere MQ connection pooling see Configuring WebSphere MQ connection pooling.
Data type | Checkbox | |
Default | Selected | |
Range |
|
|