migrateWMQMLP command

Use the migrateWMQMLP command to migrate a IBM MQ message listener port definition to an activation specification definition.

如果要執行這個指令,請使用 wsadmin Scripting 用戶端的 AdminTask 物件。

[IBM i]wsadmin Scripting 用戶端是從 Qshell 執行的。 如需相關資訊,請參閱「配置 Qshell 執行 WebSphere® Application Server Script」主題。

只有在搭配 WebSphere Application Server 第 7 版及版本更新的應用程式伺服器時,這個指令才有效。請勿搭配較舊的版本來使用它。

如需可用的 IBM MQ 傳訊提供者管理指令清單,以及每個指令的簡要說明,請在 wsadmin 提示下,輸入下列指令:

print AdminTask.help('WMQAdminCommands')

如需給定指令的概觀說明,請在 wsadmin 提示下,輸入下列指令:

print AdminTask.help('command_name')

使用該指令之後,將您所做的變更儲存到主要配置。例如,使用下列指令:

AdminConfig.save()

Purpose

Use the migrateWMQMLP command to migrate a IBM MQ message listener port definition to an activation specification definition. After the activation specification has been created, you 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 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.

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 that contains 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 that contains 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)
  • Using 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)

指出主題類型的圖示 參照主題



時間戳記圖示 前次更新: July 9, 2016 11:13
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=rmj_wmq_jmswmqmlp_migrate
檔名:rmj_wmq_jmswmqmlp_migrate.html