The FlexDeploy Siebel plugin makes it easy to migrate Siebel repository objects from one environment to another. Migrations can utilize either a full Siebel repository migration or incremental migrations. This migration provides the same flexibility as the Siebel Migration Tool, enabling automation through FlexDeploy workflows and pipelines. This 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 synchronizing environments
Workflow Considerations
This plugin provides several operations to enable both full repository migrations, as well as incremental repository migrations. The following table identifies the plugin operations, the type of workflow that they will be utilized in, and the endpoint in which they should be executed on.
| Workflow Step/plugin operation | Workflow Type | Endpoint Selection |
|---|---|---|
| siebelIncrementalBuild | Build | Siebel Source or Any |
| createWatermark | Pre-deploy or Deploy | Siebel Target |
| siebelIncrementalExport | Pre-deploy or Deploy | Siebel Source |
| siebelIncrementalImport | Deploy | Siebel Target |
| siebelFullBuild | Build | Siebel Source |
| siebelFullDeploy | Deploy | Siebel Target |
Pre-deploy workflows
A Pre-deploy 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.
Endpoint Selection
When adding plugin operations to the workflow, select the resource type (Siebel Source or Siebel Target) to identify the type of resource that the step should execute on.
When the endpoints are mapped to the environment/instance in topology they will be identified as either a source or a target.
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.