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 |
| Tip | ||
|---|---|---|
| ||
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. |
| Tip | ||
|---|---|---|
| ||
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. The workflow step assigned to this resource type will be the endpoint that this workflow step executes on.
|
Primary Use Cases
- Migrate delivered changes using Siebel incremental migrations
- Use build / deploy workflows utilizing the Siebel Incremental plugin operations
- 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 / predeploy / deploy workflows utilizing the Siebel Incremental plugin operations
- PreDeploy 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 Build - Use to perform build operation for the Incremental Repository migration
- Includes the siebelIncrementalBuild operation from the Siebel plugin.
- Sample XML source: Siebel Incremental Build.xml
- Required input is the Siebel workspace version,
- This can run on any endpoint because it does not connect to Siebel.
Incremental Pre-deploy - Use to perform the create watermark on the target and incremental repository export on the source separate from the incremental repository import on the target
- Includes the createWatermark and siebelIncrementalExport operations from the Siebel plugin.
- Requires a step to copy the zip file from the FlexDeploy transfer directory to the Siebel file system directory that is used by the Siebel Migration Tool
- Sample XML source: Siebel Incremental Predeploy.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 copy step be executed on the Siebel Target endpoint
Incremental Deploy with PreDeploy - Use to perform the incremental repository import of the export file produced from the Incremental PreDeploy
- Includes the siebelIncrementalImport operations from the Siebel plugin.
- Sample XML source: Siebel Incremental Deploy - import only.xml
- No inputs are required
- Recommended that the Incremental import step is executed on the Siebel Target endpoint
Incremental Deploy without PreDeploy - Use to perform the create watermark on the target, incremental repository export on the source, and incremental repository import on the target
- Includes the createWatermark, siebelincrementalExport, and siebelIncrementalImport operations from the Siebel plugin.
- Requires a step to copy the zip file from the FlexDeploy transfer directory to the Siebel file system directory that is used by the Siebel Migration Tool
- 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 copy step be executed on the Siebel Target 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. |
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 associated stream names would be added:
Depending on which stream name and workspace version is selected on the Build operation, will determine which branch/workspace and workspace version are migrated.
Plugin Operations
| Child pages (Children Display) |
|---|