Routing Transactions from the Siebel Server

Only one Transaction Router process can route transactions from the Siebel Server to a remote client at any one time:

• The Transaction Router locks the following folder on the remote client to prevent other Transaction Router processes from routing transactions to the same remote client:

  outbox
  

• If another Transaction Router process is already processing a remote client, then other Transaction Router processes skip this remote client.

• The Transaction Router finishes routing transactions to the remote client, and then it releases the lock and searches for another unlocked remote client to process.