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

About Real-Time and Nonreal-Time Processing Modes

You can process inbound communications events in one of two modes, real-time and nonreal-time.

Real-time mode is the default setting for each response group. To specify nonreal-time mode for a response group, you add the input argument RealTime, with a value of FALSE.

Each mode has implications for how you deploy Siebel Server components, as follows:

• Real-time mode. In this mode, Communications Inbound Receiver both receives and processes inbound messages. Communications Inbound Processor is not used. Real-time mode may be deployed in the following cases:
  • Real-time mode is required for handling voice work items (using Siebel CTI with Siebel Universal Queuing, in order to route calls).
  • Real-time mode may be appropriate if you have a relatively low volume of messages. In such a case, you can use real-time mode in order to perform all inbound processing through a single component (Communications Inbound Receiver).
• Nonreal-time mode. In this mode, Communications Inbound Receiver receives inbound messages and queues them for further processing by Communications Inbound Processor. You can determine how many instances of each component you will require.

Inbound processing for Siebel Email Response or Siebel Wireless Messaging (that is, using two-way messaging) can use either real-time or nonreal-time mode, according to your business requirements.

NOTE:  Nonreal-time mode may be most appropriate for Siebel Email Response deployments with a high volume of messages, because of the greater degree of scalability and availability provided.