Mobile Web Client Requirements

Due to the complexity of table relationships and Mobile Web Client requirements, you must use EIM to import data into Siebel base tables.

Caution: Do not attempt to modify data directly in the physical tables. Oracle does not support performing this activity for the reasons that follow. The logical relationships that exist within the Siebel base tables are many and complex, as governed by the Siebel repository metadata. Direct modification of Siebel base tables is not supported because there is a high risk of data integrity corruption. EIM maintains data integrity and resolves foreign key relationships during the import process. In addition, EIM data inserts, updates, or deletions are routed to mobile users with Siebel Remote local databases or Siebel replicated nodes.

The only exception is when you are migrating the entire Siebel schema from one database to another. In this case, you may select to use a tool provided by the database vendor to migrate the data.

In other rare cases where EIM cannot be used, it may be possible to use Siebel Visual Basic (VB) to insert, update, or delete large amounts of data. For information on VB methods, see Siebel VB Language Reference.

For initial data loading, you should consider set-based operations for all EIM processes. To maximize performance, you should also consider running EIM processes in parallel.

For ongoing operations, if you are using Mobile Web Clients within your architecture, you should consider EIM in row-by-row operations for the data that is required of the Mobile Web Clients. Running large EIM processes and set-based operations usually requires performing a database extraction for Mobile Web Clients, if the data being manipulated affects them.