WebSphere MQ topic connection factory custom propertiesUse 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.
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.
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.
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.
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 |
|
| Data type | String |
| Default | MIGRATE |
| Range |
|
For more information about the use of this property in WebSphere MQ, see the section Subscription stores in the WebSphere MQ Using Java book.