Process Flow Between EIM and Other Database  

Posted by Rajesh

Figure., illustrates the following processes:
■ How a non-Siebel database uses an SQL ancillary program utility to receive or send data to Siebel EIM tables.
■ How Siebel EIM is used to move data between Siebel EIM tables and Siebel base tables.

-------------------------------------------------------------------------------------
For each EIM process, you need to complete the following sequence of steps.

1 Prepare the EIM tables. For delete, merge, or import operations, the EIM tables require loading with representative data that allows EIM to identify the specific Siebel base table on which to operate. You can use either an SQL ancillary program utility or native SQL to perform this function. The structure of the EIM tables has the required mappings for the primary (or target) base table and other base tables that are serviced by the EIM table. The EIM export processes require minimal preparation of the EIM tables. When an export operation takes place, the EIM tables are populated with data from the Siebel base tables. Therefore, you can use either an SQL ancillary program or native SQL to transfer data from the Siebel application to a non-Siebel application...

2 Edit the EIM configuration file. An ASCII or Unicode (binary) text file of extension type .IFB that resides in the Siebel Server/admin directory allows you to define the type of EIM processes to be performed: Export, Delete, Merge, or Import.

3 Run EIM. EIM is submitted as a Siebel Server batch component task either from the
Administration - Server Management views or from the Server Manager command line interface.

4 Check results. The EIM component task produces a log file, which provides tracing information about the process. The tracing information produced is variable dependent upon the EIM component task parameters used and the Siebel Server event logging deployed for the EIM component. As always, during testing operations you should check the EIM processes using
increased tracing information, and then reduce tracing when the process is deployed to
production.

This entry was posted on Monday, June 16, 2008 at 2:26 AM . You can follow any responses to this entry through the comments feed .

0 comments

Post a Comment