Siebel Field Service Guide > Scheduling Using Oracle Real-Time Scheduler Version 1.0 >

About Fault Handling

The following situations for fault handling apply to Siebel Field Service Integration to Oracle Real-Time Scheduler 1.0:

• Oracle Real-Time Scheduler 1.0 is unavailable, and the Siebel application sends messages to it.

  An issue is passed back to the Siebel application and presented to the user as an error message. An administrator can access a monitoring screen to track errors.

  For synchronous processes, changes in the Siebel application are not recognized until the changes are synchronized with Oracle Real-Time Scheduler 1.0. For example, if Oracle Real-Time Scheduler 1.0 or Oracle Fusion Middleware is unavailable when a user updates the status of an activity, then the Siebel application displays an error message and does not recognize the update.

  For asynchronous processes, a table in the Siebel database contains Sync status flags. If an error occurs, then the table is updated with a value of N for the Sync status flag and an error description for the Sync Failure Description.

• The Siebel application is unavailable, and Oracle Real-Time Scheduler 1.0 sends messages to it through Oracle Fusion Middleware.

  According to the fault policy configured in Oracle Fusion Middleware, Oracle Fusion Middleware attempts multiple times to access the Siebel application and then terminates if the Siebel application is unavailable. You can set the number of attempts to any number, and you can also configure an interval if the Siebel application might be unavailable for a long time.

  The error message is stored in Oracle Fusion Middleware, and an administrator for Oracle Service-Oriented Architecture can view the error console in Oracle Fusion Middleware.

• Oracle Real-Time Scheduler 1.0 is unavailable, but its database is available. Oracle Fusion Middleware picks records from the DESPATCHES and INVALID tables of the database for Oracle Real-Time Scheduler 1.0, and Oracle Fusion Middleware returns to Oracle Real-Time Scheduler 1.0 for additional information.

  The fault policy configured in Oracle Fusion Middleware applies to this situation. After Oracle Fusion Middleware picks records from the database for Oracle Real-Time Scheduler 1.0, it attempts multiple times to get information from Oracle Real-Time Scheduler 1.0. It stops these attempts when Oracle Real-Time Scheduler 1.0 is available.