How Siebel Remote Makes Sure Server Components Can Run Concurrently

Siebel Remote uses the following rules and behaviors to make sure server components can run successfully in a concurrent environment:

• The Transaction Processor server component can run while any other server component runs.

• Each Siebel Server can use only one Transaction Processor.

• Only one instance of the Transaction Router, Transaction Merger, Synchronization Manager, or Database Extract server components can process a 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 Siebel 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.