Siebel Customer-Centric Enterprise Warehouse Installation and Configuration Guide > Deploying Multiple Siebel Customer-Centric Enterprise Warehouse Applications >

Setting Up Incremental Deployment

Incremental deployment allows you modify an existing Siebel Business Analytics configuration by adding new applications.

The following procedure incrementally deploys Siebel Enterprise Sales Analytics for Oracle 11i to an running Siebel Financial Analytics for Oracle 11i production environment. The full ETL run is completed by Siebel Financial Analytics and it is successfully running daily incremental ETL runs. The Siebel Enterprise Sales Analytics needs to complete a full ETL run and join Siebel Financial Analytics in future incremental ETL runs.

NOTE:  It is recommended that you backup your production repository and make a snapshot of your data warehouse before using the following procedure.

To set up incremental deployment

1. Import the Siebel Enterprise Sales Analytics workflows into the Siebel Business Analytics repository.

   For more information on importing application workflows into the repository, see Importing Application Workflows into the Repository.

2. Start the Workflow Manager, connect to your development repository, and note the new reusable worklets, under the non-reusable shell worklets, that are specific to the ORACLE11i_EnterpriseSales_Application workflow.
3. Create the combined Siebel Enterprise Sales Analytics and Siebel Financial Analytics workflow:
   1. Rename the ORACLE11i_Finance_Application workflow to ORACLE11i_Finance_And_Sales_Application.
   2. Add the reusable worklets from Step 2 to the non-reusable shell worklets in the ORACLE11i_Finance_And_Sales_Application workflow.

      For information on Siebel Business Analytics workflows and their dependent worklets, see Process of Building Multi-Application Workflows for the Siebel Business Analytics.

   3. For all the new reusable worklets, check the dependencies, and note all the unique sessions that they use.
   4. On the repository navigator, right-click the worklets in these sessions, and click Dependencies.
   5. In the Dependencies dialog box, select only Sessions as object types, and deselect all others.
4. Open the file_parameters_ora11i.csv parameter file using Notepad, and edit this file to perform a full ETL run for all the new sessions:
   1. Change the PARM_DVALUE_1 column value to 19700101000000,
   2. Change the PARM_NVALUE_1 column value to 0.
5. Run the ORACLE11i_Finance_And_Sales_Application workflow.
6. Open the file_parameters_ora11i.csv parameter file using Notepad, and change the PARM_NVALUE_1 column value to 1, 2, or 3, depending on your incremental window choice.
7. Run the Siebel Enterprise Sales Analytics PLP initial workflow:
   1. Open the Siebel Enterprise Sales Analytics initial workflow, PLP_EnterpriseSales_Application_INIT.
   2. Disable all the reusable worklets that are present in the Finance Initial Workflow, PLP_Finance_Application_INIT.
   3. Run the PLP_EnterpriseSales_Application_INIT initial workflow.
8. Create the PLP incremental workflow for the two applications:
   1. Rename the PLP_Finance_Application_INCR workflow to PLP_Finance_And_EnterpriseSales_Application_INCR.
   2. Add the Siebel Enterprise Sales Analytics reusable worklets to the PLP_Finance_And_EnterpriseSales_Application_INCR.

      For more information on building multi-application workflows, see Process of Building Multi-Application Workflows for the Siebel Business Analytics.

9. Run the merged workflows:
   1. ORACLE11i_Finance_And_Sales_Application from the base folder.
   2. PLP_Finance_And_EnterpriseSales_Application_INCR from the Post Load Processing folder.

      NOTE:  You can run these workflow frequently to verify the data before you move the repository and the data warehouse to production.