Siebel Remote and Replication Manager Administration Guide > Implementing Siebel Remote Server > Setting Siebel Remote System Preferences >

Docking: Transaction Logging

This preference enables or disables docking transaction logging. The default value is TRUE. This value is case sensitive.

You must set this value to TRUE when performing a database extract. Transaction logging must be enabled during extraction to log changes to the local database. The following procedures provide detailed instructions for disabling and enabling transaction logging.

CAUTION:  Disabling Transaction Logging will prevent Siebel Remote from working.

To disable transaction logging

1. From the application-level menu, choose Navigate > Site Map > Administration - Application > System Preferences.
2. In the System Preferences list, select the Docking: Transaction Logging record and set System Preference Value to False.
3. Restart the Siebel server.

To enable transaction logging

1. From the application-level menu, choose Navigate > Site Map > Administration - Application > System Preferences.
2. In the System Preferences list, select the Docking: Transaction Logging record and set System Preference Value to TRUE.

   The following steps must also be completed whenever the value of Docking: Transaction Logging is changed from FALSE to TRUE:

3. Restart the Transaction Processor with TS DB Recreate set to True.

   This restores transaction logging and rebuilds the dobjinst.dbf file to make sure that correct, up-to-date information about the data in the database is cached. For information about starting the Transaction Processor, see Starting Siebel Remote Server Components.

   CAUTION:  If the dobjinst.dbf file is not rebuilt when Transaction Logging is enabled, Mobile Web Clients may experience data discrepancies or visibility problems.

4. For each active Mobile Web Client in your system (that is, any Mobile Web Client who has no End Date set), reextract and reinitialize that client's local database to make sure that it contains up-to-date data.

   This is necessary because any transactions that occur while Transaction Logging is set to False are not logged, and thus are not routed to the Mobile Web Clients that would otherwise receive them, even after Transaction Logging is set to True again.

When using the Assignment Manager or EIM and Docking: Transaction Logging is set to TRUE (default), all the changes will be logged and the appropriate ones will be propagated to the Remote clients. The changes are all logged into the S_DOCK_TXN_LOG table.

With a large volume of data, it may take quite a long time for the Transaction Processor and Router tasks to process the changes for each of the Remote clients. It may take so long that it would be faster to reextract the Mobile Web Client and apply the extract remotely.

Therefore, it is recommended that you turn off transaction logging when loading data using EIM to avoid the rapid expansion of the S_DOCK_TXN_LOG table. After, the data has been loaded and assigned, turn on transaction logging and reextract the mobile clients. This will also prevent the risk of overloading of the Transaction Processor and Router processes.

In general, bigger batches tend to enhance performance for EIM, but cause problems for Siebel Remote. If you are using both EIM and Siebel Remote, it is recommended that you limit batch sizes to 1000 or fewer records.