Use this panel to view or change the configuration properties of the selected topic connection factory for use with the WebSphere MQ as a JMS provider. These configuration properties control how connections are created to the associated JMS topic destination.
A WebSphere MQ topic connection factory is used to create JMS connections to topic destinations provided by WebSphere MQ for publish/subscribe messaging.
The JNDI name that is used to bind the topic 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 topic connection factory for administrative purposes within IBM WebSphere Application Server.
Data type | String |
Default | Null |
Specifies whether to use the WebSphere MQ client connection or JNI bindings for connection to the WebSphere MQ queue manager. WebSphere MQ as the JMS provider controls the communication protocols between JMS clients and JMS servers. Tune the transport type when you are using non-ASF nonpersistent, non-durable, non-transactional messaging or when you want to satisfy security issues and the client is local to the queue manager node.
Data type | Enum |
Units | Not applicable |
Default | BINDINGS |
Range |
|
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. QUEUED is fallback for all other cases. Note: 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,
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.
|
The name of the publish/subscribe broker's control queue, to which publisher and subscriber applications send all command messages (except publications and requests to delete publications).
Data type | String |
Default | Null |
Range | 1 through 48 ASCII characters |
The name of the WebSphere MQ queue manager that provides the publish/subscribe message broker.
Data type | String |
Default | Null |
Range | 1 through 48 ASCII characters |
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 |
Default | Null |
Range | 1 through 48 ASCII characters |
The name of the broker's queue from which non-durable subscription messages are retrieved. The subscriber specifies the name of the queue when it registers a subscription.
Data type | String |
Default | Null |
Range | 1 through 48 ASCII characters |
The name of the broker's queue from which non-durable subscription messages are retrieved for a ConnectionConsumer. This property applies only for use of the Web container.
Data type | String |
Default | Null |
Range | 1 through 48 ASCII characters |
Whether the message broker is provided by the WebSphere MQ MA0C Supportpac or newer versions of WebSphere message broker products.
Data type | Enum |
Default | Advanced |
Range |
|
Select this check box to enable clone support to allow the same durable subscription across topic clones.
Data type | Check box |
Default | Cleared |
Range |
|
If you select this property, you must also specify a value for the Client ID property.
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.
The term 'null' means leave blank; if you do this, a null value is passed and the default WebSphere MQ CCSID value is used.
Data type | String |
Units | Integer |
Default | Null |
Range | 1 through 65535 |
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 are available from the WebSphere MQ messaging multiplatform and platform-specific books Web pages; for example, at http://www.ibm.com/software/integration/wmq/library/, the IBM Publications Center, or from the WebSphere MQ collection kit, SK2T-0730.
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; for example, the section "Distinguished Names" at http://www.ibm.com/software/integration/wmq/library/.
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 is independent from any WebSphere MQ connection pooling. You 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.
Leave the aged timeout at the default value of 0 for connection pools used with WebSphere MQ JMS connection factories.
If a firewall is being used that closed idle connections, set the unused timeout of the connection pool to be less than the idle timeout on the firewall. If WebSphere MQ connection pooling is also enabled, set the total of the unused timeout and the mqjms.pooling.timeout to be less than the idle timeout configured on the firewall. This allows connections to be cleaned up by the connection pools, rather than being terminated by the firewall.
An optional set of session pool settings.
This link provides a panel of optional connection pool properties, common to all J2C connectors.
The application server pools connections and sessions with the JMS provider to improve performance. This is independent from any WebSphere MQ connection pooling. You 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.
Sessions that are running under a WebSphere MQ JMS connection create individual connections to the WebSphere MQ queue manager. Therefore, the same considerations apply when tuning the session pool as when tuning the connection pool. Refer to the Connection pool and Enable MQ Connection Pooling sections for more information.