WAS v8.5 > Administer applications and their environment > Welcome to administering Messaging resources > Manage messaging with the WebSphere MQ messaging provider > Configure JMS resources for the WebSphere MQ messaging providerMigrating a listener port to an activation specification for use with the WebSphere MQ messaging provider
For WebSphere Application Server v7 and later, listener ports are stabilized. You must therefore plan to migrate your WebSphere MQ message-driven bean deployment configurations from using listener ports to using activation specifications.
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.We can continue to configure EJB 3, EJB 2.1, and EJB 2.0 message-driven beans against a listener port. You might want to do this for compatability with existing message-driven bean applications. However, listener ports are stabilized, and you should plan to migrate all your message-driven beans to use JCA 1.5-compliant or 1.6-compliant resources. For more information about when to use listener ports rather than activation specifications, see Message-driven beans, activation specifications, and listener ports. For WAS v7 and later, listener ports are stabilized. For more information, read the article on stabilized features. You should plan to migrate your WebSphere MQ message-driven bean deployment configurations from using listener ports to using activation specifications. However, you should not begin this migration until you are sure the application does not have to work on application servers earlier than WAS v7. For example, if we have an application server cluster with some members at v6.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.
Note 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 WebSphere 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 WebSphere MQ and WebSphere Message Broker information centres.
- Start the dmgr console.
- In the navigation pane, expandServers > Server Types > WebSphere application servers->server_name > [Communications] Messaging > Message listener service > [Additional Properties] Listener Ports > listener_port
The Message listener port page panel is displayed.
- Select the listener port to work with by selecting the check box to the left of the listener port name.
- Click Convert to activation specification to start the "Convert listener port to activation specification" wizard.
- On the "Step1: Supply activation specification name" page, enter the following information then click Next to continue:
- The name of the new activation specification to be created.
- The JNDI name of the new activation specification.
- The scope of the new activation specification (Server, Node, Cluster, Cell). Note that Cluster only appears when the server is in a cluster.
- On the "Step2: Summary"page, click Finish to complete the creation of the new activation specification.
- Stop then restart the application server.
- To complete the configuration of the activation specification, see Configure an activation specification for the WebSphere MQ messaging provider.
Related
Configure an activation specification for the WebSphere MQ messaging provider
Reference:
migrateWMQMLP command
WebSphere MQ messaging provider activation specification settings
createWMQActivationSpec command
deleteWMQActivationSpec command
listWMQActivationSpecs command
modifyWMQActivationSpec command
showWMQActivationSpec command
WebSphere Message Broker library