Author: Clement Joseph (Senior Manager, Siebel CRM Development)
The new, unified REST-enabled Siebel Migration application released in Innovation Pack 2017 (17.0) had several features that empower the customer with additional capability, enriched user interface, better configuration, and manageability.
As a sequel to the recent release of Siebel CRM IP17, key enhancements to the Migration Application are underway to help our customers customize it to their requirements. The details of the same are discussed in this blog.
Key Features of Migration Application in IP2017
Application Deployment Manager (ADM) with Transformation support.
Process Orchestration with Parallel and Sequential execution.
File Prepare and Deploy support for moving files.
Expose Executables as REST Resources.
Unified Logging and Archiving.
REST-enabled Interfaces for Utilities.
Key Planned Enhancements
Segregate Export and Import.
Execute exports in parallel.
Input Activation Date.
Significant Planned Additions
Fetch Watermark for the Target in Connections tab.
Enable the user to create Migration Plan with only Source or Target in the Migration client.
Validate the Manifest file, which contains the list of artifacts to be migrated before import, in case of Import-only Migration Execution.
Add Package file name as a new column in Execution and History tabs.
Resource Flow Enhancement to Segregate Export Import
The Resource Flow would be segregated in to three types based on the choices made while creating the Migration Plan.
Sample Customer Scenario with Resource Flow Enhancements
Figure 1: Sample Customer Scenario with Resource Flow Enhancements.
Watermark Generation for Incremental Runtime Repository (IRR)
Create a Connection to Target in one of the environments using the Migration application.
Select the Target Connection to generate a Watermark and click the Generate Watermark button.
Note: Copy the Watermark file from file system of Target to Source.
Make Repository changes in the Source environment.
Create a Connection to Source in one of the environments using the Migration application.
Navigate to the Migration Plan tab and create a plan with only Source.
Select the required resources.
Navigate to Execution tab and click the Play icon for the Migration plan.
Note: Once the migration completes, copy the exported package file from the file system of Source to Target.
Create Connection to Target in the Migration application
Navigate to the Migration Plan tab and create a plan with only Target named Import IRR.
Select the Incremental Repository Service resource.
Navigate to the Execution tab and click the Play button for the Migration plan.
Once the Migration is complete, Target is ready with new changes.
Additional Changes in the Application Migration Client
Export: After you click the Run button in the Execution tab, enter the Package and Watermark name.
Import: If you select Schema Service, enter the Authentication details of the Target environment. Also, enter Activation Date, which is the date from when the changes will be effective.
The new features enhance the Migration Application for use in diverse migration processes that some of our customers perform. They also ensure that the planning of upgrade and downtime is more accurate and predictable.
THE ABOVE IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION. IT IS INTENDED FOR INFORMATION PURPOSES ONLY, AND MAY NOT BE INCORPORATED INTO ANY CONTRACT. IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL, CODE, OR FUNCTIONALITY, AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISIONS. THE DEVELOPMENT, RELEASE, AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLE’S PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE.