migrateWMQMLP command
Use the migrateWMQMLP command to migrate an IBM MQ message listener port definition to an activation specification definition.
To run the command, use the AdminTask object of the wsadmin scripting client.
(iSeries) The wsadmin scripting client is run from Qshell. See topic "Configure Qshell to run WebSphere Application Server scripts".
This command is valid only when it is used with WAS v7 and later application servers. Do not use it with earlier versions.
For a list of the available IBM MQ messaging provider administrative commands, plus a brief description of each command, enter at the wsadmin prompt:
print AdminTask.help('WMQAdminCommands')
For overview help on a given command, enter at the wsadmin prompt:
print AdminTask.help('command_name')
After using the command, save the changes to the master configuration. For example.
AdminConfig.save()
Use the migrateWMQMLP command to migrate an IBM MQ message listener port definition to an activation specification definition. After the activation specification has been created, we can delete the listener port.
Note that the Maximum retries listener port setting is not migrated to the new activation specification as there is no exact equivalent.
When we 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, we 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.
Target object
The message listener port to be migrated.
Required parameters
- -asName
- The name of the activation specification to be created.
- -asJNDIName
- The JNDI name of the activation specification to be created.
- -asScope
- The type of scope at which to create the activation specification (server, node, cluster or cell). Note that the cluster option is only supported when the server containing the message listener port is part of a cluster. If not specified this defaults to server. The scopes specified are relative to the message listener port, so node is the node of the server containing the message listener port.
Optional parameters
None.The following example shows how to migrate a message listener port to an activation specification.
- Use Jython:
wsadmin>AdminConfig.list("ListenerPort") lp1(cells/L3A3316Node09Cell/nodes/L3A3316Node10/servers/server1| server.xml#ListenerPort_1211265363796) wsadmin>AdminTask.migrateWMQMLP("lp1(cells/L3A3316Node09Cell/nodes/ L3A3316Node10/servers/server1|server.xml#ListenerPort_1211265363796)", ["-asName migratedFromLP -asJNDIName jms/as1 -asScope node"]) migratedFromLP(cells/L3A3316Node09Cell/nodes/L3A3316Node10| resources.xml#J2CActivationSpec_1211265679078) - Use Jacl:
wsadmin>$AdminConfig list ListenerPort lp1(cells/L3A3316Node09Cell/nodes/L3A3316Node10/servers/server1| server.xml#ListenerPort_1211265363796) wsadmin>$AdminTask migrateWMQMLP lp1(cells/L3A3316Node09Cell/nodes/L3A3316Node10/servers/server1| server.xml#ListenerPort_1211265363796) {-asName migratedFromLP -asJNDIName jms/as1 -asScope node} migratedFromLP(cells/L3A3316Node09Cell/nodes/L3A3316Node10| resources.xml#J2CActivationSpec_1211265679078)
