Network Deployment (All operating systems), v8.5 > Reference > Commands (wsadmin scripting)
migrateWMQMLP command
Use the migrateWMQMLP command to migrate a WebSphere MQ message listener port definition to an activation specification definition.
To run the command, use AdminTask of the wsadmin scripting client.
The wsadmin scripting client is run
from Qshell. For more information, see the topic "Configure Qshell
to run WAS 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 WebSphere MQ messaging provider administrative commands, plus a brief description of each command, enter the following command at the wsadmin prompt:
print AdminTask.help('WMQAdminCommands')
For overview help on a given command, enter the following command at the wsadmin prompt:
print AdminTask.help('command_name')
After using the command, save your changes to the master configuration. For example, use the following command:
AdminConfig.save()
Purpose
Use the migrateWMQMLP command to migrate a WebSphere MQ message listener port definition to an activation specification definition. After the activation specification has been created, we can delete the listener port.
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 IBM Integration BusWebSphere Message Broker 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 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.
- Using 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) - 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)
Related tasks:
Using the wsadmin scripting AdminTask object for scripted administration
Starting the wsadmin scripting client using wsadmin.sh
Related reference:
createWMQActivationSpec command
deleteWMQActivationSpec command
listWMQActivationSpecs command
modifyWMQActivationSpec command
Mapping of administrative console panel names to command names and WebSphere MQ names
