Siebel Remote and Replication Manager Administration Guide > Configuring the Remote Client > Creating a Remote Client >

Using EIM to Create Multiple Siebel Remote Clients

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.

Using Transaction Logging with EIM or Assignment Manager

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.

To use transaction logging with EIM or Assignment Manager

1. Disable transaction logging.

   For more information, see Disabling Transaction Logging

2. Use EIM to load data or use Assignment Manager to assign data.

   Make sure you limit batch sizes for EIM to 1000 or fewer records.

3. Enable transaction logging.

   For more information, see Step 1.

Using Set-Based Logging for EIM

EIM logs transactions differently according to the following value of the LOG TRANSACTIONS TO FILE parameter:

• TRUE. EIM logs transactions in the following folder with only one marker logged in the S_DOCK_TXN_LOG table:

  FileSystem\eim

• FALSE. EIM logs transactions in sets to reduce database contention in the S_DOCK_TXN log. It only records one transaction for each EIM set in the S_DOCK_TXN_LOG table.

Avoiding Transaction Processor Failures That Are Caused by Moving the File System

The Transaction Processor might fail with an error that is similar to the following:

Unable to open User Txn Log file for reading or writing in FileSystem\eim\*.dx.

The following situation can cause this error:

1. EIM runs with the LOG TRANSACTIONS TO FILE parameter set to the default TRUE to collect EIM transactions in the FileSystem\eim folder.
2. You move the file system from the FileSystem\eim folder to another folder, such as NewFileSystem\eim.
3. You delete the FileSystem\eim folder.
4. You start the Transaction Processor.

The master transaction in the S_DOCK_TXN_LOG table indicates that the EIM log exists in the FileSystem\eim, folder. The Transaction Processor fails when it cannot open the FileSystem\eim\*.dx file. For more information, see Modifying the S_DOCK_TXN_LOG Table.

To avoid Transaction Processor failures that are caused by moving the file system

1. Make sure the Transaction Processor finishes processing all transaction that exist in the following folder before you move the file system:

   FileSystem\eim

2. If you already moved the file system, then do the following:
   1. Create the FileSystem\eim folder.
   2. Copy all DX files from the NewFileSystem\eim folder to the FileSystem\eim folder.
3. Start the Transaction Processor.