Siebel Email Administration Guide > Administering Siebel Communications Server for Siebel Email Response > Administering Communications Inbound Receiver >

Event Processing for Real-Time and Nonreal-Time Processing

For both real-time processing and nonreal-time processing, inbound email is saved as event data to the local disk in a file with the .EVT file extension. Message content and attachments are also saved to the Siebel File System. For more information, see Activity Attachments Stored for Incoming Messages.

How the inbound event is then processed depends on whether you use real-time processing or nonreal-time processing:

• Real-time processing. In real-time processing, in which Communications Inbound Receiver performs all event processing, additional files are created on the local disk that represent different states of processing or represent error conditions. For more information about the processing of these files, see Events and Communications Inbound Receiver.

  Extensions for these files include the following:

  • XEVT. Events that are ready for workflow processing.
  • ERROR. Events that generated known errors and that can be retried.
  • CRASH. Events that failed for unknown reasons and must not be retried.
• Nonreal-time processing. In nonreal-time processing, 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 retrieves this request and processes the event.

  You can track nonreal-time events that are submitted to Communications Inbound Processor using the Communications Inbound Events view of the Administration - Communications screen. You can manually resubmit events that are not fully processed due to transient errors from this view. You cannot track real-time events.

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

  • Queued. Communications Inbound Receiver submitted the event for Communications Inbound Processor processing.
  • CIP Processing. Communications Inbound Processor received the event and is currently processing the event.
  • Error. Event processing 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 failed due to an unknown error and must not be resubmitted.