Siebel Email Response Administration Guide > Completing Basic Setup Tasks >

How Real-Time Events Flow Through the Communications Inbound Receiver

When the CIR is started, it loads the media drivers required by the response groups it will be processing. Each response group may use multiple communication profiles. Each communication profile requires a media driver. The media driver is responsible for retrieving messages and passing them to CIR in the proper format.

The media drivers pass tag/value pairs to the CIR, which define the content of the incoming messages. Any attachments associated with the incoming message are stored on the email server. References to these attachments are included in the name/value pairs passed to the CIR. It is the responsibility of the workflows invoked by CIR to delete all file attachments when these attachments are no longer needed.

The CIR takes the incoming message data and serializes it to a disk based queue. The disk is used instead of memory for several reasons as follows:

• Persistence - if the computer crashes, the queued events are not lost.
• Memory - storing on disk reduces CIR memory requirements.
• Capacity - disk space is essentially unlimited so the queue size is unbounded.

Events are stored in folders underneath the "queued" directory. The folders are named after the response group that generates the events. Events are in Universal Transformation Format, which translates 16-bit Unicode characters into 8-bit characters. Each event always has a file name prefix of "CIR77". The CIR can process events that are left over from a Communications Inbound Manager 7.04 or 7.5 install.