Index Changes

ETL Siebel Integration

Siebel database structure

The Siebel application uses relational databases to store data. Nevertheless, the data model is controlled directly by the Siebel application (and not by the RDBMS) using a repository. The repository contains, among other things, the description of the database objects, such as tables, indexes, and control information, to manage referential integrity and dependency between data.

Using ETL to migrate/export/import from Siebel

When migrating the Siebel database from one RDBMS to another (such as Oracle to DB2), or moving the same RDBMS to a different hardware platform (such as Oracle/DB2 for NT to DB2 for OS/390), the issue of moving data presents itself. During a database migration, three categories of data need to be addressed:

*Repository data *Seed data *User data

Migrating repository data

Migrating repository data does not present any challenges. Direct table-to-table mapping can be used in eTL collaborations to migrate data from one platform to other.

Migrating seed data

Seed data doesn’t get moved unless you migrate the database. Seed data refers to data that maps “users to responsibilities”, version information, and other control data used by the Siebel database to manage itself. Basic seed data is moved into specific seed data tables, named S_xxx etc, during the Siebel installation process.

Seed data also evolves and changes over time. Therefore, when you are migrating the database, you must also migrate the seed data to the new target RDBMS using direct mapping ETL collabs.

Migrating user data

Moving user data presents the biggest challenge due to its large volumes. Sun SeeBeyond ETL Integrator & proposed Siebel EIM Adapter can be used to migrate, export, or import the data and is suitable for small or large volumes of data. The proposed architecture will enable ETL to provide solution to migrate, export or import data to/from Siebel eBusiness System.

ETL Integrator can load data to interface tables for import to Siebel or extract data from interface table for export from Siebel to/from flat files or database tables.

The Siebel EIM Adapter need to be implemented that will have provision to generate Siebel eScript which will in turn either pick up the data from the interface table populated by eTL and load the data to base tables (import) or pick up the data from base table to populate the interface table (export) that will eventually be picked up by eTL. Siebel EIM Adapter will also be responsible to generate scripts by using basic primitives or execute existing script. Siebel EIM Adapter will also have the following web services:

*Start: Invoke Siebel EIM Manager to run the generated/existing script *Monitor: Monitor the Siebel task for import/export *Report: Report the completion status (completed successfully or with error)

ETL Integrator then can generate report based the status column in the interface tables which should have been populated by Siebel EIM manager. The various operation (e.g. ETL source data to staging/interface table -> invoke Siebel EIM Manager to run generated/existing Siebel Script -> Monitor/Report Status -> generate Report) can be orchestrated using BPEL Editor.

Back to ETLSE

JSPWiki v2.4.100
« Home Index Changes Prefs
This page (revision-4) was last changed on 27-Feb-07 03:10 AM, -0800 by karthikeyan