Running Multiple Transaction Router Processes

You must run at least one Transaction Router on each Siebel Server. To improve performance, it is recommended that you start multiple Transaction Router processes on the same Siebel Server. This configuration increases the throughput of transactions to the user outbox:

• Each Transaction Router process can simultaneously route transactions from the server database to a different remote client. For example, if you start four Transaction Router processes, then these four processes can simultaneously route transactions to four different remote clients.

• Using multiple Transaction Router processes reduces the total time that Siebel Remote requires to route transactions to remote clients.

You can start as many concurrent Transaction Router processes as the server database and the Siebel Server can support:

• Monitor the server database and Siebel Server to make sure the concurrent Transaction Router processes do not overload the Siebel application.

• Start with two Transaction Router processes, and then increase the number of processes.

• You typically run multiple Transaction Router processes for each server.

For more information, see Optimizing Server Components.