Process Developer

Back Next

Input and Output for Migrate

The input for the migrate operation requires a pid. For your process request message that passes data to this operation, you can look up the pid on the Active Processes list or obtain it programmatically. Basically you can use the

getProcessList

API call (or a report) to bring back the set of process ids matching the ones you want to migrate. If you have a large number to migrate, you can migrate many instances in parallel.

The following example show sample data:

<migration:migrateRequest xmlns:migration="http://docs.active-endpoints/wsdl/migration/2011/04/migration.xsd">
<!--The string comes from the Create Map operation: -->
   <migration:migrationMap>string</migration:migrationMap>
   <migration:pid>850</migration:pid>
   <!--Optional. If not used, defaults to the online plan of the pid. If used, must match with toPlan in migrate operation:-->
   <migration:toPlanId>145</migration:toPlanId>
   <!--Optional. Defaults to false:-->
   <migration:createBackup>false</migration:createBackup>
</migration:migrateRequest>

The following is a sample migrate response message:

 <migrateResponse xmlns="http://docs.active-endpoints/wsdl/migration/2011/04/migration.xsd">
         <response>MIGRATION_WARNING Errorcode:3001. Migration Warning: The empty activity is being marked as Finished when it is not. This might result in invalid output for the pid 850. (location path /process/sequence/empty)</response>
         <backupPid>851</backupPid>
      </migrateResponse>

Migration Service

Download Guide

Watch

Comments

Cloud Application Integration Homepage