Migrating a listener port to an activation specification for use with the IBM MQ messaging provider
For WebSphere® Application Server Version 7 and later, listener ports are stabilized. You must therefore plan to migrate your IBM MQ message-driven bean deployment configurations from using listener ports to using activation specifications.
Before you begin
EJB 2.0 message-driven beans cannot be configured against JCA 1.5-compliant resources. If your bean is an EJB 2.0 application, upgrade it to EJB 3 or EJB 2.1 before you complete this task.
About this task
For WebSphere Application Server Version 7 and later, listener ports are stabilized. For more information, read the topic about stabilized features. Plan to migrate your WebSphere MQ message-driven bean deployment configurations from using listener ports to using activation specifications. However, do not begin this migration until you are sure the application does not have to work on application servers earlier than WebSphere Application Server Version 7. For example, if you have an application server cluster with some members at Version 6.1 and some at a later version, you should not migrate applications on that cluster to use activation specifications until after you migrate all the application servers in the cluster to the later version. Also, when you migrate to activation specifications on the z/OS® platform, you must enable the Control Region Adjunct (CRA) process of the application server (either by selecting Enable JCA based inbound message delivery on the JMS provider settings panel, or by using the manageWMQ command to include starting the CRA process as part of starting an application server).
Note that the Maximum retries listener port setting is not migrated to the new activation specification as there is no exact equivalent.
When you are migrating a listener port associated with a message-driven bean (MDB) that has the subscriptionDurability activation configuration property set to Durable, and that MDB already has an active durable subscription, the durable subscription is not migrated. This is because listener ports and IBM MQ activation specifications use incompatible forms of subscription name. As a result there can be two active durable subscriptions subscribed to the relevant topic for the same MDB. As part of the migration process, you must delete the old durable subscription that was associated with the listener port and manually clean up any messages associated with it. For information on how do to this see the IBM MQ and IBM Integration Bus documentation.