Siebel Remote and Replication Manager Administration Guide > Configuring the Siebel Server > Options for Configuring the Siebel Server >

Optimizing the Transaction Router Server Component

The Transaction Router server component takes transactions from the docking\txnproc folder and constructs DX files. It then sends these DX files to the outbox that corresponds to the user.

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

For more information, see Transaction Router Server Component, and Parameters of the Transaction Router Server Component.

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.

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.

Modifying Routing Rules

A Siebel application includes predefined user routing rules. These routing rules include a combination of implicit security rules, according to responsibility, and assignment rules that determines the information the user can access. For help with configuring routing rules for optimal performance with a large number of objects, such as assets, accounts, or activities, see Getting Help from Oracle.

Setting the Threshold That Siebel Remote Uses to Route Transactions

You can use the Operation Routing Rate Threshold parameter of the Transaction Router to set the number of transactions that Siebel Remote routes in one second. You can adjust this threshold to avoid receiving the following system alert:

Router is experiencing lower performance throughput than expected

This alert is an informational alert. It does not indicate that an error occurred. You can also adjust the threshold to avoid an unnecessary increase in the number of DX files.

To set the threshold that Siebel Remote uses to route transactions

1. Locate the record for the Transaction Router server component.

   For more information, see Disabling Transaction Logging.

2. In the bottom applet, click the Parameters tab, and then query the Parameter field for the following parameter:

   Operation Routing Rate Threshold

3. In the Value on Restart field, enter a numeric value.

   The default value is 2.8. You can increase the value in the Value on Restart field to prevent Siebel Remote from logging excessive messages in the Transaction Router log file. For example, you can enter 5.6. You can also disable notification for the Transaction Router server component.