Siebel Communications Server Administration Guide > Administering Siebel Communications Server > Administering Communications Inbound Receiver >

Event Processing for Real-Time and Nonreal-Time Modes

In each mode, inbound email is saved as event data to the local disk, in a file with extension .evt. (Message content and attachments are also saved to the Siebel File System, as described in Activity Attachments Stored for Inbound Email.) How the inbound event is then processed depends on whether you are using real-time mode or nonreal-time mode.

• Real-time mode. In real-time mode, where all event processing is done by Communications Inbound Receiver, additional files are created on the local disk that represent different states of processing or represent error conditions. Such file extensions include:
  • .xevt - Events ready for processing by the worfklow process.
  • .error - Events that generated known errors and that can be retried.
  • .crash - Events that failed for unknown reasons and should not be retried.

    For more information about the processing of these files, see Siebel Email Response Administration Guide.

• Nonreal-time mode. In nonreal-time mode, Communications Inbound Receiver writes event data to the Siebel Database (in the S_CM_INBND_EVT table) and to the Siebel File System, and submits a request to Server Request Processor and Server Request Broker. Communications Inbound Processor picks up this request and processes the event.

  Nonreal-time events that have been submitted to Communications Inbound Processor can be tracked using the Communications Inbound Events view in the Administration - Communications screen (unlike events in real-time mode). Events that could not be fully processed due to transient errors can be resubmitted manually from this view.

  Valid status for events in the Communications Inbound Events view include:

  • Queued. Communications Inbound Receiver has submitted the event for processing by Communications Inbound Processor.
  • CIP Processing. Communications Inbound Processor has received the event and is currently processing the event.
  • Error. Event processing has failed due to a known error. You can resubmit the event for processing using the Submit Request command in the applet menu.
  • Fatal. Event processing has failed due to an unknown error and should not be resubmitted.

    For more information about using the Communications Inbound Events view, see Siebel Email Response Administration Guide.