Configuring an activation specification for the WebSphere MQ messaging provider

Configure a JMS activation specification to enable a message-driven bean (MDB) to communicate with the WebSphere® MQ messaging provider.

1. In the navigation pane, click Resources > JMS->Activation specifications.
   A list of existing activation specifications, with a summary of their properties, is displayed in an Activation specification collection form.
2. Select the Scope setting corresponding to the scope of the activation specifications that you want to view or change.
3. Select the name of the activation specification that you want to view or change.
   Configuration details for the activation specification are displayed in an WebSphere MQ messaging provider activation specification settings form.
4. Under General Properties make modifications as necessary.

   For information about each of the available fields, see WebSphere MQ messaging provider activation specification settings.

   Note: There are four WebSphere MQ connection properties that are used to configure the WebSphere MQ resource adapter used by the WebSphere MQ messaging provider. These properties affect the connection pool that is used by activation specifications:

   • maxConnections
   • connectionConcurrency (Setting this property only affects WebSphere Application Server 7 nodes. The property has no effect for WebSphere Application Server Version 8 or later nodes.)
   • reconnectionRetryCount
   • reconnectionRetryInterval

   For more information about these four properties, and how to configure them, see Resource adapter properties.
5. Click Apply to save the configuration.
6. Optional: Click Advanced properties to display or change the list of advanced properties of your activation specification.
7. Optional: Click Broker properties to display or change the list of broker properties of your activation specification.
8. Optional: Click Custom properties to display or change the list of custom properties of your activation specification.
   For example, you would use this option to set the custom property WAS_EndpointInitialState for an activation specification. WAS_EndpointInitialState determines whether or not message consumption begins from the JMS destination as soon as the activation specification is used for a message-driven bean to connect with the destination.
9. Optional: Click Client transport properties to display or change the list of client transport properties of your activation specification. This link is only present on the explicitly-defined variation of this panel, where you enter all information required to connect to WebSphere MQ. This link does not appear for the CCDT-based variation.
10. Click OK.
11. Save your changes to the master configuration.
12. If you use activation specifications with WebSphere MQ message-driven beans (MDBs) on the z/OS® platform, you must enable the control region adjunct (CRA) process of the application server. Either select Enable JCA based inbound message delivery on the JMS provider settings panel, or by use the manageWMQ command to include starting the CRA as part of the process for starting an application server.
13. To have the changed configuration take effect, stop then restart the application server.