Siebel Remote and Replication Manager Administration Guide > About Siebel Remote > Locks, Concurrency, and Conflicts >

Locking and Concurrency

Concurrency rules and behaviors in Siebel Remote include the following items:

• The Transaction Processor server component can run while any other server component runs.
• There can be only one Transaction Processor for each Siebel Server.
• Only one instance of the Transaction Router, Transaction Merger, Synchronization Manager, or Database Extract can process a given remote client at any one time:
  • Two Transaction Router server processes cannot route transactions to the same remote client at the same time.
  • Two Transaction Merger processes cannot merge transactions from the same remote client at the same time.

    To improve performance, multiple instances of these server components can run on one Siebel Server.

• The following server components cannot process a remote client while a database extract is in progress for that client:
  • Transaction Router
  • Transaction Merger
  • Synchronization Manager
• If a Transaction Router, Transaction Merger, or Synchronization Manager resides on the same server, then they can process the same remote client at the same time.
• Multiple instances of Database Extract that run at the same time allow Siebel Remote to extract multiple lists of users. This configuration reduces the duration of the overall extract.