Siebel Innovation Pack 2017: About REST API Used for Migration Discovery and Execution

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, those services will be invoked to migrate the data.

Table Table 21 lists the migration resources that are available in the Siebel Migration.

Table 21. Migration Services
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 TableOwner UserName and the TableOwner Password.	The supported methods for the Schema Service include: Export Import GetWatermark IsSchemaChanged GetStatus
Design Repository Data Service	Migrates the design time repository and the runtime repository from the source environment to the target environment. In the target environment, the migrated repository is named Migrated Repository. You must run the Schema Service and the Application Workspace Data Service along with the Design Repository Data Service. After the Siebel Migration is complete, you must change the Migrated Repository to Siebel Repository in the S_REPOSITORY table.	The supported methods for the Schema Service include: Export Import DBChck GetStatus
Runtime Repository Data Service	Migrates only the runtime repository from the source environment to the target environment. The migrated repository is named Migration Repository in the target environment. The user must select the name and version of the Workspace Branch. The default version will be the latest version. You must run the Schema Service and the Application Workspace Data Service along with the Runtime Repository Data Service. After the Siebel Migration is complete, you must change the Migrated Repository to Siebel Repository in the S_REPOSITORY table.	The supported methods for the Schema Service include: GetRRInfo GetWatermark Export Import DBCheck GetStatus
Application Workspace Data Service	Migrates the seed records from the source environment to the target environment. You must run the Schema Service and the Runtime Repository Service along with the Application Workspace Data Service.	The supported methods for the Schema Service include: GetSeedCopyWatermark GetFullSeedWatermark SeedCopyExport GetStatus SeedCopyImport FullSeedExport FullSeedImport
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. You must run the Schema Service along with the Incremental Runtime Repository Data Service. The Schema Service only runs if there is a change detected as part of the incremental migration. Otherwise, the Schema Service will not run even though it is part of the selection.	The supported methods for the Schema Service include: Export Import GetWatermark DBCheck GetStatus
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.	The supported methods for the Schema Service include: GetWatermark Export Import GetStatus
Application Data Service	This service migrates the data from the source environment to the target environment based on the tables listed in datamig.inp file on the source environment.	The supported methods for the Schema Service include: Export Import GetStatus
Application Data Service With Transformation	Migrates the data from the source environment to the target environment based on the tables listed in the datamig.inp on the source environment. While exporting the data, this service uses the rule defined in the datamig.rul file and performs the transformation. The transformed data will be migrated to the target environment.	The supported methods for the Schema Service include: Export Import GetStatus
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 supported methods for the Schema Service include: Prepare Deploy GetStatus

Siebel Database Upgrade Guide for DB2 for z/OS		Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices.

About REST API Used for Migration Discovery and Execution

Related Topics