1. Siebel 8.0 Module 2: Overview of EIM Processing Integrating Siebel Applications

2. Module i: Integrating Siebel Applications Training 2 Siebel 8.0 Module Objectives After completing this module you will be able to:  To define EIM and related EIM components  To identify the Enterprise Integration Manager (EIM) operations that can be used to integrate applications  To understand the role of EIM, what EIM can do and can’t do  To understand why you can update the tables directly using SQL  To understand the role of user keys in EIM Why you need to know:  EIM allows the importing and exporting of data between Siebel and other applications

3. Module i: Integrating Siebel Applications Training 3 Siebel 8.0 Overview of EIM EIM is a server component in the Siebel EAI component group EIM is used for data transfers between other data sources and the Siebel database. EIM is the only process allowed by Siebel for bulk batch data imports, exports and deletes into Siebel base tables. The exchange of data is accomplished through EIM tables, also called interface or staging tables EIM internally executes thousands of steps to deliver this functionality

4. Module i: Integrating Siebel Applications Training 4 Siebel 8.0 What EIM does not do EIM does not copy data from the source system into the base tables EIM does not load data into the EIM table(s) EIM does not batch the data. EIM does not recognize on its own that data is available, where that data is, and that it needs to start and process that data. EIM does not report status about the success or failure of data records to anything beyond Siebel server administration screens and the EIM log file. EIM does not clean up the data in an EIM table after an EIM task/job has completed. The EIM process does not do and does not have the capability to do the following activities:  Transformations  Data cleanup  Standardization Since these activities are a required part of EIM-based interfaces, and EIM does not do them, these activities must therefore be executed by other programs and/or processes.

5. Module i: Integrating Siebel Applications Training 5 Siebel 8.0 Changes will not be routed out to remote users You cannot use SQL to populate user data in base tables  Relationships between tables are complex  Referential integrity is maintained programmatically through ROW_IDs, not using constraints on the database  SQL statements cannot generate Siebel ROW_IDs Why not load directly into base tables FK PK S_ORG_EXT S_ADDR_ORG SQL

6. Module i: Integrating Siebel Applications Training 6 Siebel 8.0 User Data User data is populated and managed by the users  Installation populates seed data and repository data, not user data Database User-supplied data such as account information

7. Module i: Integrating Siebel Applications Training 7 Siebel 8.0 Populating and Managing User Data Use the client application to enter, update, or delete small amounts of data directly in the base tables Use server tasks to:  Import or update large amounts of data from external sources through interface tables  Delete large amounts of data Database Base table Interface table External data Server task

8. Module i: Integrating Siebel Applications Training 8 Siebel 8.0 Base Tables User data is stored in one or more base tables in the Siebel database  Relationships between base tables (referential integrity) rely upon primary and foreign keys based on ROW_IDs ROW_ID is the system primary key for every base table ROW_ID is a system-generated value PK S_ORG_EXT S_ADDR_ORG FK PK S_BU FK

9. Module i: Integrating Siebel Applications Training 9 Siebel 8.0 Base tables use the Siebel ROW_ID values on each record to relate to each other in foreign key relationships. EIM maintains data integrity and resolves foreign key relationships during the import process  EIM Interface tables do NOT use these ROW_ID values to relate to the base tables  Instead, EIM uses User Key fields to relate to the base tables. Relationship between Base and EIM Tables

10. Module i: Integrating Siebel Applications Training 10 Siebel 8.0 User Key fields exist for every EIM table to base table mapping. EIM uses these fields to match a record in the EIM table to a record in the base table.  If the user keys match, then the base table record is updated.  If the user keys do not match, then a new base table record is inserted. User Key Columns NAME User key EIM_ACCOUNT S_BU LOC BU_ID S_ORG_EXT NAME LOC BU_ID 1-8D FK (ROW_ID) PK (ROW_ID) 1-8D NAME User key EIM_ACCOUNT S_BU LOC BU_ID S_ORG_EXT NAME LOC BU_ID 1-8D FK (ROW_ID) PK (ROW_ID) 1-8D

11. Module i: Integrating Siebel Applications Training 11 Siebel 8.0 Referential Integrity User key column mappings in interface tables are used to resolve ROW_IDs for base tables, maintaining referential integrity 1-8D User key Interface Table Base Table ACME Boston USA S_ORG_EXT FK to BU (USA) ACME Boston PK (ROW_ID)

12. Module i: Integrating Siebel Applications Training 12 Siebel 8.0 User Keys Can be found in Siebel Tools  Siebel standard User Key – U1 Fields when combined uniquely identify a record Example: The user key for Account data is Name, Loc and Organization

13. Module i: Integrating Siebel Applications Training 13 Siebel 8.0 Base Tables  Actual database tables containing the data the application uses  Table names start with S_ (ex. S ORG EXT) EIM  Enterprise Integration Manager  Siebel batch processing used to load data to base tables EIM (Interface) Tables  Staging area between Siebel base tables and external data  Table names start with EIM_ (ex. EIM ACCOUNT) IFB File  The EIM configuration file  Provides instructions to the EIM Process  Tells EIM what data to load from which EIM tables and to which base tables EIM Log File  Results of EIM process EIM Server Component  Process needs to be configured which will control actually running the EIM job on the server Terms & Definitions

14. Module i: Integrating Siebel Applications Training 14 Siebel 8.0 EIM or Interface Tables EIM tables store external data inside the Siebel database  A staging area for data to be: Imported, updated, or merged into base tables Exported from base tables Deleted from the base table EIM_ACCOUNT S_ORG_EXT S_ADDR_ORG External data Interface Table Base Tables

15. Module i: Integrating Siebel Applications Training 15 Siebel 8.0 EIM Processing EIM reads a configuration file to determine:  Whether data should be imported, merged, deleted, or exported  Which interface table(s) and base table(s) are used and affected Siebel Server EIM Configuration file (.ifb) Import, merge, delete, or export

16. Module i: Integrating Siebel Applications Training 16 Siebel 8.0 Summary This module showed you how to:  Describe how Enterprise Integration Manager (EIM) supports Siebel referential integrity while importing external data  Describe how user key columns maintain referential integrity  Describe why direct SQL statements cannot be used to insert user data