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

Configuring Mutually Exclusive Source Systems for Incremental Deployment

Every Siebel Customer-Centric Enterprise Warehouse table has a Source ID (SOURCE_ID) column. This column identifies what source system a record originates from. For example OAP11I is the value for the Oracle 11i source system. The data sources in the Siebel Customer-Centric Enterprise Warehouse are separated by the value of the Source ID column.

The following procedure provides information on loading the Siebel Customer-Centric Enterprise Warehouse for mutually exclusive data sources.

To configure mutually exclusive source systems

1. Import both the applications into a new repository.

   For more information on importing applications, see About the Incremental Deployment of the Siebel Business Analytics Repository.

2. Create multi-application Post Load Initial and Post Load Incremental workflows.

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

   For example, for Siebel Enterprise Sales Analytics (Oracle 11i) and Siebel Enterprise Contact Center Analytics (universal source), create workflows called PLP_EnterpriseSales_ContactCenter_Application_INIT and PLP_EnterpriseSales_ContactCenter_Application_INCR.

3. Start the application workflows.

   For example, for a full ETL load for Siebel Enterprise Sales Analytics (Oracle 11i) and Siebel Enterprise Contact Center Analytics (universal source), run the following workflows:

   1. The INITIALIZE workflow in the Siebel Applications folder.
   2. ORACLE11i_EnterpriseSales_Application workflow in the Configuration for Oracle Applications v11i folder.
   3. Universal_All_Applications_Common_Initialize workflow in the Configuration for Universal Source folder.
   4. Universal_EnterpriseContactCenter_Application workflow in the Configuration for Universal Source folder.
   5. PLP_EnterpriseSales_ContactCenter_Application_INIT in the Configuration for Post Load Processing folder.

      This workflow is created in Step 2.

4. Change the source system parameter file (for example, file_parameters_ora11i.csv) and provide an incremental value in the PARM_NVALUE_1 column.

   For more information on modifying session parameters for parameter files, see About Modifying Session Parameters for Initial and Incremental Loads.

5. Start the incremental ETL runs.

   For example, for an incremental ETL load for Siebel Enterprise Sales Analytics (Oracle 11i) and Siebel Enterprise Contact Center Analytics (universal source), run the following workflows:

   1. ORACLE11i_EnterpriseSales_Application workflow in the Configuration for Oracle Applications v11i folder.
   2. Universal_EnterpriseContactCenter_Application workflow in the Configuration for Universal Source folder.
   3. PLP_EnterpriseSales_ContactCenter_Application_INCR in the Configuration for Post Load Processing folder.

      This workflow is created in Step 2.