For information about each of the available
fields, see the
WebSphere MQ messaging provider activation specification settings form.
Note: There are
four other WebSphere MQ connection properties that affect the activation
specification:
- maxConnections
- The maximum number of the connections to a WebSphere MQ
queue manager.
- The default value is 10.
- connectionConcurrency
- The maximum number of the message-driven beans that can be supplied
by each connection. This property must always be set to 1, as documented
in APAR IC76463.
- The default value is 5.
- reconnectionRetryCount
- The maximum number of the attempts that are made by the resource
adapter to reconnect to a WebSphere MQ queue manager if
a connection fails.
- The default value is 5.
- reconnectionRetryInterval
- The time, in milliseconds, that the resource adapter waits before
it makes another attempt to reconnect to a WebSphere MQ
queue manager.
- The default value is 300000 ms.
Although these properties control
the behavior of the WebSphere MQ activation specification, they are
configured as custom properties of the WebSphere MQ messaging provider.
For more information about these four connection properties, and how
to configure them, see
Configuring custom properties for the WebSphere MQ resource adapter.
Restriction: Before Fix Pack 5, if this activation specification is used to connect to a queue manager or queue-sharing group on a WebSphere MQ for z/OS system, enter the value 6.0.0.0 in the Provider version property. The connection factory must use this provider version value regardless of the version of WebSphere MQ for z/OS to which it connects. The Provider version property is in the Advanced section of the General Properties.For Fix Pack 5 or later, if this activation specification is used to connect to a queue manager or queue-sharing group on a WebSphere MQ for z/OS Version 7 system, enter the value 6.0.0.0 in the Provider version property.
For Fix Pack 7 or later, the restriction on the provider version is lifted.