...
- Initial migration of full repository to enable future incremental migrations
- Use build / deploy workflows utilizing the Siebel Incremental plugin operations with the initial export type
- Select project properties to include the two incremental object options and the schema service
- Migrate delivered changes using Siebel incremental migrations
- Use build / deploy workflows utilizing the Siebel Incremental plugin operations with the standard export type
- Select project properties to include the two incremental object options and the schema service
- Migrate delivered changes using Siebel incremental migrations and review export results prior to importing
- Use build / pre-deploy / deploy workflows utilizing the Siebel Incremental plugin operations
- Pre-deploy workflow would contain the steps to create the watermark file and generate the zip file from the export
- Output of the export can be reviewed prior to running the deploy step to import to the target environment
- Select project properties to include the two incremental object options and the schema service
- Migrate delivered changes using Siebel full migrations
- Use build / deploy workflows utilizing the Siebel Full plugin operations
- Select project properties to include any object type except for the two incremental object options
Sample Workflows
Incremental Siebel Build - Use to perform build operation for the Incremental or Full Repository migration.
- Includes the siebelIncrementalBuild siebelBuild operation from the Siebel plugin.
- Sample XML source: Siebel Incremental Build.xml
- Required input is the Siebel workspace version and export type.
- This should execute on the Siebel Source end point because if Initial export type is selected an export is executed.
...
- Includes the createWatermark, siebelincrementalExport, and siebelIncrementalImport operations from the Siebel plugin.
- Sample XML source: Siebel Incremental Deploy - export and import.xml
- No inputs are required
- Recommended that the create Watermark step is executed on the Siebel Target endpoint
- Recommended that the Incremental Export run on the Siebel Source endpoint
Recommended that the Incremental Import run on the Siebel Target endpoint
Full Build - Use to perform build operation for the Full Repository migration.
- Includes the siebelFullBuild operation from the Siebel plugin.
- Sample JSON source: Siebel Full Build.xml
- Required input is the Siebel workspace version.
- Recommended that this be executed on the Siebel Source endpoint.
Full Deploy - Use to perform deploy operation for the Full Repository migration.
- Includes the siebelFullDeploy operation from the Siebel plugin.
- Sample XML source: Siebel Full Deploy.xml
- No inputs are required.
- Recommended that this be executed
on the Siebel Target endpoint
.
| Tip | ||
|---|---|---|
| ||
For all operations, it is recommended that the operation be executed on the end point type indicated because the Siebel Migration tool is expecting the watermark or zip file to be in a specific directory. Normally, that is the Siebel File Systems migration directory but can be whatever directory is configured for the Siebel Migration tool. The only case where the endpoint does not need to be Siebel server is in a case where the file system used by the FlexDeploy plugin operation and the Siebel Migration tool are shared across both the plugin's endpoint and the server running the Siebel Migration tool. The Siebel workspace and child workspaces must be in a delivered status (using Siebel Tools or Siebel Web Tools) before the build/deploy process will migrate the Siebel objects. |
...