Siebel Remote and Replication Manager Administration Guide > Monitoring and Reporting > Monitoring and Logging for Siebel Remote >

Automatic Notification of Critical Conditions


A critical condition might occur during processing on the Siebel Server that is related to the Transaction Router, Transaction Processor, or Transaction Merger. You can configure the Siebel Server so that if one of these conditions occurs, then the Siebel Server creates a notification alert and automatically sends an email message to you. The purpose of this notification alert is to reduce the amount of time that is required to detect and reply to these problematic conditions. The following conditions can create this notification message:

  • A server component fails to start.
  • A typical system failure occurs, such as the component failing or exiting abnormally.
  • The Siebel Server cannot write event logs because no more disk space is available on this server.
  • Siebel CRM reaches a critical throughput threshold for Siebel Remote during the Monitor Data Calculate Period, which is the number of transactions that occurs in a time period that you specify. This period can include the following items:
    • Visible event transactions. Transactions that affect the amount of visible data and who can view that data, such as the addition of an Account.
    • Position rule transactions. Visible event transactions that affect who can view specified data, such as assigning a user to an Account.
    • Combined transaction types.
    • Routing throughput of the Transaction Router.

To configure the email notification alert, you define the Monitor Data Calculate Period and other alert notification settings. For more information, see Siebel System Administration Guide.

Siebel Remote and Replication Manager Administration Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.