Siebel Remote and Replication Manager Administration Guide > Siebel Remote Concepts >

Locking and Concurrency


The following are concurrency rules and behaviors of the Siebel Remote components:

  • A transaction processor can run while any other Siebel Remote server component is running.
  • There can be only one transaction processor for each Applications server.
  • Only one instance of the Transaction Router, Transaction Merger, Synchronization Manager, or Database Extract can process a given Mobile Web Client at any one time. Two transaction routers, therefore, cannot route transactions to the same Mobile Web Client at the same time, nor can two transaction mergers merge transactions from the same Mobile Web Client at the same time. Multiple instances of these components can be running on one Applications server for better performance.
  • The Transaction Router, Transaction Merger, or Synchronization Manager cannot process a Mobile Web Client while a database extract is in progress for that Mobile Web Client.
  • The Transaction Router, Transaction Merger, and Synchronization Manager, on the same server, can process the same Mobile Web Client at the same time.
  • Multiple instances of Database Extract running at the same time allow the extraction of multiple lists of mobile users, thus reducing the overall extract duration.
Siebel Remote and Replication Manager Administration Guide