Transaction Processor Server Component

The Transaction Processor server component (alias TxnProc) scans the master transaction log of the Siebel database, and then prepares transactions for the Transaction Router server component. A single Transaction Processor process runs on each Siebel Remote server where there are active nodes to be routed. The prepared transactions are saved as DX files in the docking\txnproc folder.

Note: After you have enabled the Disconnected Mobile Synchronization component group (alias MobileSync), the component group has the state Partly Offline. The reason for this is that the Transaction Processor component has the state Not Online. After you run the Database Extract component (alias DbXtract), then you can start TxnProc. After this, the component group has the state Online.

Note: However, when the Enable Incremental Indexing system preference is set to True, the Transaction Processor component (alias TxnProc) runs automatically. The TxnProc component has the status Running and the MobileSync component group has the status Online. In this case, you must stop TxnProc before you run the DbXtract for the first time. After DbXtract has completed, then you can restart TxnProc. If you do not follow these steps, then some transactions might not be routed to remote clients. See also Requirements for Extracting the Server Database.