Siebel Performance Tuning Guide > Tuning Siebel Remote for Performance > Tuning Siebel Remote Server Components >

Tuning the Transaction Router Component

This section describes how to resolve or avoid performance issues for the Transaction Router component that arise from the following sources:

• Visibility-Related Transactions
• Docking Rules and Data Distribution
• Slow-Running Queries
• Increasing Transaction Router Throughput

For further information on Transaction Router performance issues, consult the following documents on Siebel SupportWeb:

• Troubleshooting Steps 8

  This document describes how to diagnose and resolve Transaction Router performance issues.

• Troubleshooting Steps 38

  This document describes how to monitor and manage the transaction backlog for a Siebel Remote implementation.

Visibility-Related Transactions

If you diagnose the root cause of the Transaction Router performance issue to be visibility-related transactions, consider the following two possible solutions:

• Reextract all mobile users and regional nodes

  For more information, see the Siebel Remote and Replication Manager Administration Guide.

• Allow the Transaction Router component tasks to continue processing until they clear the backlog

  Once the Transaction Router has processed all visibility-related transactions, the backlog should be processed more quickly. Starting additional Transaction Router tasks can also improve performance, but do not start more tasks than the Siebel Server or database engine can support.

Docking Rules and Data Distribution

If you diagnose the root cause of the Transaction Router performance issue to be docking rule related transactions, log a service request with Siebel Technical Support and provide the following pieces of information:

• RDBMS trace of the Transaction Router task
• Transaction Router log files
• .dx files the Transaction Router is processing from the SIEBEL_ROOT\siebsrvr\Docking\txnproc directory
• The results from executing the visrule script

  For more information about the visrule script, see Troubleshooting Steps 8 on Siebel SupportWeb.

Slow-Running Queries

If you diagnose the root cause of the Transaction Router performance issue to be slow-running queries, consult your database administrator to determine the following:

• All indexes are present and valid on the tables involved in the poor performing queries.

  To determine if all indexes are valid and present, see the Siebel Data Model Reference.

• Check if the tables and indexes involved in the poor-performing queries require de-fragmentation.

Increasing Transaction Router Throughput

The following factors can impact throughput for the Transaction Router component:

• Large batch sizes for Siebel Enterprise Manager (Siebel EIM)

  It is recommended that, where possible, you reduce the size of the batch that Siebel EIM processes when it imports data. In addition, it is recommended that you log transactions to the Siebel File System rather than the Master Transaction Log (S_DOCK_TXN_LOG).

  For more information, see the Siebel Enterprise Integration Manager Administration Guide.

• Large batch size for Siebel Assignment Manager

  Where possible, reduce the batch file size for Siebel Assignment Manager as large batch files can impact the performance of the Transaction Router component. For information, see the Siebel Assignment Manager Administration Guide.

In both cases described above, you need to decide if an increase in throughput for the Transaction Router component is more important than a decrease in throughput for the Siebel EIM and Siebel Assignment Manager components before you make changes.