Siebel Remote and Replication Manager Administration Guide > Administering Siebel Remote > Starting and Stopping Siebel Remote Server Components >

Transaction Router

The Transaction Router takes transactions from DOCKING\TXNPROC and constructs DX files. It then sends these DX files to the outbox corresponding to the appropriate mobile user.

Multiple Transaction Router Processes

You can start multiple Transaction Router processes on the Siebel Remote server to increase the throughput of transactions to mobile user outboxes.

• Each Transaction Router process can simultaneously route transactions from the database server to a different Mobile Web Client. For example, if you start four Transaction Router processes, the four Transaction Router processes can route transactions to four different Mobile Web Clients simultaneously.
• Using multiple Transaction Router processes reduces the total time needed to route transactions to Mobile Web Clients.

NOTE:  The optimal number of Transaction Routers will depend upon the number of mobile users, volume of transactions generated by the system, hardware configuration and other components of the system.

You can start as many parallel Transaction Router processes as the database server and Siebel Remote server can support:

• You should monitor the database server and Siebel Remote server to make sure the parallel Transaction Router processes do not overload the systems.
• Plan to start with two Transaction Router processes and increase the number as needed.
• You will typically run multiple Transaction Router processes per server.

CAUTION:  Do not run a Transaction Router and Ddlsync at the same time. It can cause Transaction Router to shut down.

Also, do not run visutl on the Siebel Server while Transaction Routers are running.

Routing Transactions from the Database Server

Only one Transaction Router process can route transactions from the database server to a Mobile Web Client at any one time:

• The Transaction Router locks the Mobile Web Client's outbox directory to prevent other Transaction Router processes from routing transactions to the same Mobile Web Client.
• Other Transaction Router processes skip the Mobile Web Client if another Transaction Router process is already processing this client.
• After the Transaction Router finishes routing transactions to the Mobile Web Client, the Transaction Router releases the lock and searches for another unlocked Mobile Web Client to process.