|Bookshelf Home | Contents | Index | PDF|
You can use EIM (Enterprise Integration Manager) to do a batch load if Siebel Remote must load a significant amount of data, such as when it creates a large number of remote clients. If you use EIM to import records to the server database, then Siebel Remote logs transactions in the file system to improve performance. If a remote client possesses read and write access to the records that EIM imports during an EIM session, then it is strongly recommended that you use row by row logging. For more information, see Siebel Enterprise Integration Manager Administration Guide.
If your deployment includes Replication Manager, then Siebel CRM supports this EIM functionality only on the Siebel Server of the headquarters node. For more information about headquarters nodes, see Overview of Replication Manager. For more information on how to load data in interface tables, and then populate base tables, see Siebel Enterprise Integration Manager Administration Guide.
If you use EIM or Assignment Manager, and if the Enable Transaction Logging check box contains a check mark, then Siebel Remote logs modifications in the S_DOCK_TXN_LOG table, and then synchronizes them to the remote clients. If a large amount of data exists, then the Transaction Processor and Transaction Router might require a significant amount of time to process the modifications for each remote client. It might take so long that it is faster to reextract the remote client, and then apply the extract remotely.
It is recommended that you turn off transaction logging while EIM runs to avoid a rapid expansion of the S_DOCK_TXN_LOG table. After EIM finishes loading data, you must turn on transaction logging and reextract the remote clients. This configuration also prevents the risk of overloading the Transaction Processor and the Transaction Router.
A larger batch typically improves performance for EIM but can also cause problems for Siebel Remote. If you use EIM and Siebel Remote, then it is recommended that you limit batch sizes to 1000 or fewer records.
For more information, see Modifying the S_DOCK_TXN_LOG Table.
The master transaction in the S_DOCK_TXN_LOG table indicates that the EIM log exists in the
|Siebel Remote and Replication Manager Administration Guide||Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.|