About REST API Used for Migration Discovery and Execution
Environments: All environments
Platforms: All platforms.
REST API requests are used for migration resource discovery and for migrating data from the source environment by exporting the data, transferring the data to the target environment, and importing the data into the target environment.
Siebel Migration includes the migration discovery service that is available to assist with discovering resources available for migration. The discovered services are listed in the Siebel Migration in the sequence in which they are executed during the migration process.
While creating a Siebel Migration plan, you can choose one or more services that are available. When you execute the Siebel Migration plan, those services are invoked to migrate the data.
The following table lists the migration resources that are available in the Siebel Migration.
| Migration Service | Description | Supported Methods |
|---|---|---|
|
Schema Service |
Migrates the physical Siebel schema from the source environment to the target environment. When you use this service, the Siebel Migration prompts you to enter the Table Owner User Name, the Table Owner Password, and Database Encoding. |
|
|
Runtime Repository Data Service |
Migrates only the Runtime Repository from the source environment to the target environment. The migrated repository is named Migrated Repository in the target environment. This includes Admin Data such as List of Values, Predefined Queries, etc. The user must select the name and version of the Workspace Branch. The default version will be the latest version. The Application Workspace Data Service is typically run along with the Runtime Repository Service. After the Siebel Migration is complete, you must change the Migrated Repository to Siebel Repository in the S_REPOSITORY table. |
|
|
Incremental Runtime Repository Data Service |
Identifies the version of the repository data that was previously migrated. This service takes all the changes from the previously migrated version and the latest version and migrates the data to the target environment. |
|
|
Incremental Application Workspace Data Service |
Identifies the version that was previously migrated. This service takes all the changes from the previously migrated version to the latest version and migrates them to the target environment. |
|
|
Application Data Service |
This service migrates the data from the source environment to the target environment based
on the tables listed in the It is recommended that you review the tables configured in |
|
|
Application Data Service With Transformation |
Migrates the data from the source environment to the target environment based on the
tables listed in the While exporting the data, this service uses the rule defined in the
It is recommended that you review the tables configured in |
|
|
File Prepare And Deploy Service |
Identifies all the new or modified files and migrates the files to the target environment. On the Target environment, the File Prepare And Deploy Service transfers the modified or new files to each Siebel Application Interface node defined in Siebel Management Console (SMC). This service keeps track of the files that are migrated for each target environment. The next time that the user runs this service, the service will check the modified files or newly created files from the previous migration. This service migrates the file artifacts from Siebel Application Interface and the file system. The File Prepare and Deploy Service reads the checksum values for all the web artifact files from the watermark file. The File Prepare and Deploy Service compares the checksum of the files present in the source web artifacts path. The File Prepare and Deploy Service takes files whose checksum does not match and generates an export package. The files that are not included in the watermark file are included in the export package. While importing the export package on the target environment, the existing files will be overwritten. |
|