[Version 5.1 and later]WebSphere MQ topic connection factory custom properties

Use this panel to view or change an optional set of name and value pairs for custom properties of the selected topic connection factory for use with the WebSphere MQ JMS provider. These custom properties are passed to WebSphere MQ.

To view this administrative console page, click Resources-> WebSphere MQ JMS Provider-> (In content pane, under Additional Properties) WebSphere MQ Topic Connection Factories-> connection_factory-> Custom Properties

You can use the Custom properties page to define the following WebSphere MQ properties. These properties apply only if you set the property Transport type=CLIENT.

For more information about setting the SSL properties for WebSphere MQ, see the section SSL properties in the WebSphere MQ Using Java book.

SSLCIPHERSUITE
The cipher suite to use for SSL connection.

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 SSLPEERNAME is to be set.

SSLCRL
A list of zero or more CRL (Certificate Revocation List) servers used to check for SSL certificate revocation. (Use of this property requires a WebSphere MQ JVM at Java 2 version 1.4.)

The value is a space-delimited list of entries of the form:

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.

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

If SSLPEERNAME is not set, such checking is performed. SSLPEERNAME is ignored if SSLCIPHERSUITE is not specified.

The SSLPEERNAME property is a list of attribute name and value pairs separated by commas or semicolons. For example:

SSLPEERNAME(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; for example, the section "Distinguished Names" at http://publibfp.boulder.ibm.com/epubs/html/csqzas01/csqzas010p.htm#HDRDCDN.

MSGSELECTION
Determines whether message selection is done by the JMS Client or by the Broker.

If you set the property Transport type=BINDINGS, message selection is always done by the Broker and the setting of this property is ignored.

Data type String
Default CLIENT
Range
CLIENT
Message selection is done by the JMS Client.
BROKER
Message selection is done by the Broker.
SUBSTORE
Where WebSphere MQ JMS should store persistent data relating to active subscriptions.
Data type String
Default MIGRATE
Range
BROKER
Subscription information is stored by the publish/subscribe broker used by the application.

If a non-durable subscriber fails, the subscription is deregistered from the broker as soon as possible. The broker adds a response to this deregistration onto the SYSTEM.JMS.REPORT.QUEUE, which is used to clean up after the failed subscriber. With SUBSTORE(BROKER), a separate cleanup thread is run regularly in the background of each JMS publish/subscribe application.

MIGRATE
This option dynamically selects the queue-based or broker-based subscription store based on the levels of queue manager and publish/subscribe broker installed. If both queue manager and broker are capable of supporting SUBSTORE(BROKER), this behaves as SUBSTORE(BROKER); otherwise it behaves as SUBSTORE(QUEUE). Additionally, SUBSTORE(MIGRATE) transfers durable subscription information from the queue-based subscription store to the broker-based store.

This provides an easy migration path from older versions of WebSphere MQ JMS, WebSphere MQ, and publish/subscribe broker.

QUEUE
Subscription information is stored on SYSTEM.JMS.ADMIN.QUEUE and SYSTEM.JMS.PS.STATUS.QUEUE on the local queue manager. SUBSTORE(QUEUE) is provided for compatibility with versions of MQSeries JMS.

For more information about the use of this property in WebSphere MQ, see the section Subscription stores in the WebSphere MQ Using Java book.

Related information

WebSphere MQ topic connection factory settings