EIM and ADM

HI.

Every one who ever worked with Siebel knows what EIM is.

EIM is Enterprise Integration Managers.
 It is needed to insert, delete, update data in Siebel database. The main purpose why we use EIM is that it's not recommended to use straight SQL statements to update database (this is another story, because there is people, that thinks it is nothing special, others say that it will broke the Siebel database architecture, to what believe is up to you, I for now believe that it is not recommended, but I have it used (sql) and nothing had happened).
So how we use EIM? Simple we upload data to EIM table (this time with sql by using some data spreadsheet, like Excel if you use Microsoft SLQ Management Studio or just .txt file if you use other data base management program, or just by sql). Then by using the jobs in Siebel we update data in base table with data from EIM table. Siebel do this by him self and manages all the thing that can go wrong by using simple sql. As I already said, there is lot of info about that so there is link to ITToolbox about EIM - http://it.toolbox.com/wiki/index.php/Siebel_EIM
EIM is pretty simple when you understand the mappings and .ifb file structure. Mappings means that there must be one column in base table mapped to one column in EIM table. There already in vanilla is many mappings for vanilla tables like S_CONTACTS and EIM_CONTACTS or EIM_ACCOUNTS and S_ORG_EXT. But some times you have to create your own mappings.
The .ifb file is used by the EIM job as parameter. This file contains the information about what table we need to update, does we need to delete, update or insert data. In one .ifb file you can store many EIM operation and when you need to use some one you just comment or uncomment the section, or use them all together by one job - EIM will do section by section if you have lots of data and tables to update.
As every job in Siebel EIM job can be set to repeat status, so it will run scheduled on time for example once a week. But for that always needs to be sure that data in EIM table is up to date.
Just to know EIM is used for user data (client information), for Siebel data, like active views, LOV's, responsibility or other, import, export we use ADM.

ADM - Application Deployment Manager. It is used to move Siebel entities between the environments. Link - http://siebelunleashed.com/application-deployment-manager-adm-introduction/
Best example is LOV's Views and Responsibilities. As you develop or configure Siebel application in DEV environment and create for your requirement new LOV's or Responsibilities they will not be available in TEST or PRODUCTION environment after you migrate. Because of this there is ADM. In TEST environment we export LOV's in .xml file, and then use it in PRODUCTION environment for import.
The main reason is that the LOV's aren't created in Siebel Tools (again question to argue), but straight in application in Administration - Data. And they are not migrating with .srf file.
There are only few vanilla made projects for ADM, so if you want to migrate something your made, you need to create your own project. For example you want to export Product Catalog with all of it's structure. You can do this with EIM, because for structure there isn't only one table but many. So you create your own ADM project for things like this. But this is very complicated thing so may be some other time.