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

About Fault Handling

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

• Oracle Real-Time Scheduler 2.1 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 2.1. For example, if Oracle Real-Time Scheduler 2.1 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 2.1 sends messages to it through Oracle Fusion Middleware.

  Oracle Real-Time Scheduler 2.1 attempts multiple times to access the Siebel application through Oracle Fusion Middleware to make sure that the information is delivered when the Siebel application is available.