Executing a Migration Plan

You can execute a migration plan for your migration by sending an HTTP POST request to the Siebel Migration Application.

Depending on the migration service that you selected in your migration plan, you must provide the following additional information in your REST API request:

• If you selected a Schema Service with Export & Import or Import only for your migration plan, then you must provide the following parameter and value in your REST API request:

  • schemaPassword. The password for the schema user. The schemaPassword must be encrypted by using base64 in the REST API request if pre-Encrypted is not used.

    Note: If you want to use a pre-encrypted Schema Owner Password encrypted using the encryptstring.exe utility, don't use the base64 encoded password. Use your pre-encrypted password, add the parameter pwdPreEncrypted and set its value to true. This tells the migration process that your password has already been encrypted using encryptstring and you don't need to encrypt it again during the process. Leaving the parameter out or setting it to false indicates that you are using a base64 encoded password for the REST call.

• If you selected the Incremental Runtime Repository or the Incremental Application Workspace Data Service or the File Prepare and Deploy Service with Export only for your migration plan, then you must provide the watermarkFilename parameter and value in your REST API request.

• If you want to only migrate a specific version when run the Incremental Runtime Repository (Export & Import or Export only) migration, then you must provide the irrEndVersion parameter and value in the REST API request. If you do not provide the irrEndVersion parameter and value, then, the migration migrates up to the latest version.

• For all Export only or Import only migration plans, you must provide the packageFilename parameter and value in the REST API request.

The following details are for a request to execute a migration plan:

• URI: https://{hostname}:{port}/siebel/v1.0/migration/execution/{planName}

• HTTP Method: POST

• Content-Type: application/json

• Authorization: Basic

• Request Body:

  {
  "schemaPassword":"RA8c4/CVDs9KOsrHmzW+xwX4kXwi",
  "pwdPreEncrypted":"true",
  "watermarkFilename":"",
  "irrEndVersion":"",
  "packageFilename":"",
  }
  

Note: If schemaUser or isUnicodeDatabase (which are part of the Input payload) are provided in the Request Body, then they will be ignored. Instead, schemaUser and isUnicodeDatabase will be read from the Target connection. If neither schemaUser nor isUnicodeDatabase are specified in the Target connection, then an error will be returned.

The following are the details for the response to a successful request:

• HTTP Code: 200

• Content-Type: application/json

• Response Body:

  {  
     "id":"88-1V5YFC",
     "planName":"Data Mig",
     "description":"Data Mig",
     "status":"Running",
     "startDate":"2018-07-24 09:50:20",
     "endDate":"",
     "source":"Dev",
     "target":"Prod",
     "packageName":"",
     "resources":[  
        {  
           "id":"88-1V5YFD",
           "name":"",
           "operation":"Export",
           "sequenceNumber":"1",
           "mode":"Asynchronous",
           "status":"Not Started",
           "startTime":"",
           "endTime":"",
           "resourceType":""
        },
        {  
           "id":"88-1V5YFE",
           "name":"",
           "operation":"Import",
           "sequenceNumber":"2",
           "mode":"Asynchronous",
           "status":"Not Started",
           "startTime":"",
           "endTime":"",
           "resourceType":""
        }
     ]
  }