The FlexDeploy Siebel plugin makes it easy to migrate Siebel repository objects from one environment to another. Migrations can utilize either a full Siebel repsoitory migration or the incremental migrations can be used. This migration provides the same flexibility as the Siebel Migration Tool but provides the added value of being able to incorporate the migration of Siebel objects with other projects of different technologies in the same release.
Supported Versions
- Siebel 17 or higher
Key Features
- Leverages incremental repository change migrations by using Siebel Watermark file technology
- Leverages full repository migrations to aid in syncronizing enviornments
Workflow Considerations
For Siebel incremental and full deploy workflows, the operations would normally be organized like this:
| Workflow Step/plugin operation | Workflow Type | Endpoint Selection |
|---|---|---|
| siebelIncrementalBuild | Build | Siebel Source or Any |
| createWatermark | PreDeploy or Deploy | Siebel Target |
| siebelIncrementalExport | PreDeploy or Deploy | Siebel Source |
| siebelIncrementalImport | Deploy | Siebel Target |
| siebelFullBuild | Build | Siebel Source |
| siebelFullDeploy | Deploy | Siebel Target |
A PreDeploy workflow can be utilized in cases where the content that was exported from the source Siebel needs to be validated prior to importing that to the next environment.
To set the Endpoint selection, select the appropriate resource type (Siebel Source or Siebel Target) when adding the workflow step like this:
When selecting/defining the endpoints in the topology, a target environment will most like have two endpoints defined. Make sure to set the resource type on the endpoints appropriately. The workflow step assigned to this resource type will be the endpoint that this workflow step executes on.
Project setup considerations
When setting up the project configuration, the SCM Type is set to none but the stream name will still be utilized. The stream name will correspond to the WorkSpace branch name of either the main branch or integration workspace within Siebel Tools.
Example:
In Siebel Tools, there is the MAIN workspace and an integration workspace called int_test1:
In FlexDeploy, the associate Stream names would be added:
Depending on which stream name and workspace version is picked on the Build operation, will determine which branch/workspace and workspace version are migrated.
The Siebel workspace and child workspaces must be in a delivered status before the build/deploy process will migrate the Siebel objects.