Skip navigation.
Downloads | Product Documentation | Support

WebLogic Server Command Reference

## MIGRATE

Migrates a JMS service or a JTA Transaction Recovery service to a targeted server within a server cluster.

For more information about migrating services, refer to "Migration for Pinned Services" in the Using WebLogic Clusters guide.

### Syntax

To migrate JMS resources:

>     java [ SSL Arguments ] weblogic.Admin
>          [-url URL]
>          [ User Credentials Arguments ]
>       MIGRATE -migratabletarget "serverName (migratable)"
>       -destination serverName [-sourcedown] [-destinationdown]

To migrate JTA resources:

>     java [ SSL Arguments ] weblogic.Admin
>          [-url URL]
>          [ User Credentials Arguments ]
>       MIGRATE -jta -migratabletarget serverName
>       -destination serverName [-sourcedown] [-destinationdown]

Argument | Definition
--- | ---
{-url [`protocol``://`]`listen-address:listen-port``}` | Specify the listen address and listen port of the Administration Server. If you specify a secure listen port, you must also specify a secure protocol. If you do not specify a value, the command assumes `t3://localhost:7001`. For more information, refer to the -url entry in Table 1-3 on page 11 and Protocol Support.
`-jta` | Specifies that the migration is a migration of JTA services. If you do not specify this argument, the `MIGRATE` command migrates JMS services.
`-migratabletarget` | Names the server from which the service will migrate. The syntax for the server name varies depending on the type of service you are migrating: For JMS, specify `"``servername``(migratable)"` For example, `"myserver (migratable)"` For JTA, specify `servername` For example, `myserver`
`-destination` | Names the server to which the service will migrate.
`-sourcedown` | Specifies that the source server is down. This switch should be used very carefully. If the source server is not in fact down, but only unavailable because of network problems, the service will be activated on the destination server without being removed from the source server, resulting in two simultaneous running versions of the same service, which could cause corruption of the transaction log or of JMS messages.
`-destinationdown` | Specifies that the destination server is down. When migrating a JMS service to a non-running server instance, the server instance will activate the JMS service upon the next startup. When migrating the JTA Transaction Recovery Service to a non-running server instance, the target server will assume recovery services when it is started.

### Examples

In the following example, a JMS service is migrated from myserver2 to myserver3.

>     java weblogic.Admin -url AdminHost:7001 -username weblogic
>        -password weblogic
>        MIGRATE -migratabletarget "myserver2 (migratable)"
>       -destination myserver3

In the following example, a JTA Transaction Recovery service is migrated from myserver2 to myserver3.

>     java weblogic.Admin -url AdminHost:7001 -username weblogic
>        -password weblogic
>         MIGRATE -jta -migratabletarget myserver2
>        -destination myserver3 -sourcedown