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

Optimizing the Transaction Processor Server Component

Only one Transaction Processor can run for each database installation in a Siebel Enterprise that includes more than one Siebel Server. At startup, the Transaction Processor verifies that another Transaction Processor is not running on the same Siebel Server. This configuration makes sure that the Transaction Processor is not kept from running because it cannot find a valid node during synchronization. For example, assume two Siebel Servers run in the same Siebel Enterprise and reference the same database. Siebel Remote extracts a remote client for one of the Siebel Servers during synchronization, and then correctly applies all the updates from the local database to the server database. It does not apply any server updates to the local database and the Siebel application creates an error similar to the following:

Transaction Processor determined that this node does not have any mobile clients or regional servers that need to receive transactions. Please do a DB extract on one of these nodes before restarting this component.

In this situation, Siebel Remote does not apply any server updates to the local database during synchronization. To correct this problem, you can reextract and reinitialize the remote client on the Siebel Server where it failed. To avoid the problem entirely, you must use only one transaction process for each database installation.

For more information, see the following topics:

• Transaction Processor Server Component
• Optimizing Server Components
• Parameters of the Transaction Processor Server Component