Real-Time and Nonreal-Time Processing

Depending on your business requirements, you can process email in one of the following ways:

Real-Time Processing.
Nonreal-Time Processing.

The following figure provides examples of different configurations for Communications Inbound Receiver and Communications Inbound Processor in your Siebel Enterprise, as follows:

Configuration A. Shows real-time processing for Communications Inbound Receiver on one Siebel Server.
Configuration B. Shows Communications Inbound Receiver on one Siebel Server and Communications Inbound Processor divided between two Siebel Servers.
Configuration C. Shows Communications Inbound Receiver and Communications Inbound Processor on two Siebel Servers.

Examples of Configurations for Communications Inbound Receiver and Communications Inbound Processor. This image is described in surrounding text.

Real-Time Processing

Real-time email processing uses only one server component, the Communications Inbound Receiver. Communications Inbound Receiver both receives and processes inbound messages. Communications Inbound Processor is not used in real-time processing. This type of processing is best for businesses with a low volume of email customers or businesses that primarily use phone events because these events always use real-time processing.

The following figure describes the architecture for real-time email processing. This figure shows that Communications Inbound Receiver (CIR) pulls email from the email server. CIR includes the Workflow Process Manager (WPM) and Server Request Broker (SRB), and CIR communicates with the Siebel File System (SFS) and with other entities, such as the driver and the user interface. For information about how to enable real-time email processing, see Enabling Real-Time Email Processing. For more information about processing email in real time, see Events and Communications Inbound Receiver.

Real-Time Email Processing. This image is described in surrounding text.

Nonreal-Time Processing

Nonreal-time email processing has two server components, the Communications Inbound Receiver and the Communications Inbound Processor, running as separate server components. This type of processing enables you to have multiple instances of Communications Inbound Receiver and Communications Inbound Processor on different Siebel Servers, providing a distributed architecture that is more scalable and reliable.

The following figure describes the architecture for nonreal-time email processing. This figure shows that Communications Inbound Receiver (CIR) pulls email from the email server. CIR includes Server Request Broker (SRB), and Communications Inbound Processor (CIP) includes the Workflow Process Manager (WPM). CIR and CIP communicate with each other, with the Siebel File System (SFS), and with other entities, such as the driver and the user interface. For information about how to enable nonreal-time email processing, see Enabling Nonreal-Time Email Processing.

Nonreal-Time Email Processing. This image is described in surrounding text.