Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Remote and Replication Manager Administration Guide > Configuring the Siebel Server > Options for Configuring the Siebel Server > Optimizing the Transaction Router Server ComponentThe Transaction Router server component takes transactions from the 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 ProcessesYou 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:
You can start as many concurrent Transaction Router processes as the server database and the Siebel Server can support:
For more information, see Optimizing Server Components. Routing Transactions from the Siebel ServerOnly one Transaction Router process can route transactions from the Siebel Server to a remote client at any one time:
Modifying Routing RulesA 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 TransactionsYou 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. To set the threshold that Siebel Remote uses to route transactions
|
![]() ![]() |
Siebel Remote and Replication Manager Administration Guide | Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |