Académique Documents
Professionnel Documents
Culture Documents
4. CONFIGURATION FILE
5. EIM PROCESS
6. DATA IMPORTING
7. IMPORTING AN ACCOUNT
The Enterprise Integration Manager (EIM) manages the bi-directional data transfer between
the Siebel base tables and the Siebel interface tables. The process of data movement between
base tables and the interface tables is very complex. Hence a manager is required for this
process of data movement. We must use EIM to perform bulk import, export, merge, and
delete operations because Siebel Systems do not support using native SQL to load data directly
into the Siebel base tables.
• Siebel interface tables are intermediate database tables that act as a staging area
between the base tables in the Siebel Database and other databases
• EIM tables are required to perform major EIM functions: import, delete, merge and
export since the direct process of data movement from external data base to Base tables
is very complex.
Where data
ends up
Source
(external)
How to
get there
Interface
(EIM)
For e.g.
While performing data movement activities, it is necessary to know which interface table will
be loading data into which base table and vice versa. In other words, understanding data
mapping becomes a necessity.
In order to find out which Interface table is populating which base table, it is possible to do so
using Siebel Tools.
Another method of finding out the relationship is through viewing the bookshelf.
CONFIGURATION FILE:
For all EIM processes to function, the Enterprise Integration Manager requires a configuration
file to be present in the admin subdirectory of the Siebel Server. This file contains various
parameters which define what operations the EIM is required to perform. The file is an ASCII
text file and has an .ifb extension.
(a)Header Section:
The header section consists of parameters given at the beginning of the .ifb file.
• [Siebel interface Manager] : This keyword must be present at the beginning of
the .ifb file.
• PROCESS : This provides the manager with information on the
activity to be performed. For e.g. Import Everything
Other Parameters Include
EIM PROCESS:
Once the interface tables have been populated, the EIM process is run. The EIM is submitted
as a Siebel Server Batch Component Task either through the Server Administration screens or
from the Server Manager Command Line Interface. On each pass, EIM processes one interface
table and performs a particular action on all rows in that table for that batch.
In the Component Request Parameters list, add or change the various component
parameters for the EIM process.
Add a new record
Select the Appropriate name from the job parameters window
Select the appropriate Value field
In the Component Request form, click the submit button in the menu options
The EIM server task can also be run through the command line interface. The ‘srvrmgr’
command is used to invoke the Siebel server manager for batch mode processing through
running scripts.
Flags used:
-g gateway server
-e enterprise server
-u username
-p password
-s Siebel server
-c executes the single command
-i gets command from input file
-o logs information into the specified file
As shown in the example, the server manager is invoked with the parameters of gateway
server, Siebel application Server, userid, password and the command
Account S_ORG_EXT
Contact S_CONTACT
Opportunity S_OPTY
Service Request S_SRV_REQ
Activity S_EVT_ACT
Products S_PROD_INT
Position S_POSTN
• Identify the User Key columns and make sure they are populated uniquely:
The User key is a column or a combination of columns which ensure that the
records entered into the base tables are unique. Hence, it is necessary to specify
values to these columns while importing data.
• Identify the Foreign Key column: The foreign key columns are used to create
functional dependency in the database. They should be used only when there is a
need to directly link the data being imported with data already present in the
database. In such cases, additional data may have to be entered for the parent
table.
Each table that is loaded with data requires the filling up of the foreign key
field so as to connect the entered data with the other database tables. The
• Required Fields: Apart from the dependencies and foreign key columns, there
are some fields which are required for successful importing. They mainly
comprise of setting various flags.
• Identify the mandatory column for EIM processing: There are various
mandatory columns that have to be filled for data import.
These include:
• Memory Resources: The database memory area needs to be large enough to hold
most of the frequently accessed data in the cache.
• Database Resources: EIM uses database server space for the interface tables,
target base tables, secondary tables, and work areas. To make sure that an import
process runs smoothly to completion, you must anticipate and plan for these space
requirements.
4. Backup your existing database: Before importing data and making changes in
the application, it is necessary to create a backup of your data.
5. Load the Interface Tables: Data is loaded first onto the interface tables after which they
populate the base tables. Data loading is done through SQL queries.
values ('1000',1001,'FOR_IMPORT' …)
8. Test the import Process: Test the import process for a small batch of records before
larger records are imported.
9. Run the EIM process: Call the server manager either through the GUI or through the
command line interface.
10.Verify Results: Once data has been imported successfully, there is a need to verify the
results. Query the appropriate records for viewing the results.