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

Events and Communications Inbound Receiver

When Communications Inbound Receiver is started, it loads the communications drivers that its processing response groups require. Each response group can use multiple communications profiles. Each communications profile requires a communications driver. The communications driver retrieves messages and passes them to Communications Inbound Receiver in the proper format.

The communications drivers pass tag-value pairs, which define the content of the incoming messages, to Communications Inbound Receiver. Any attachments that are associated with the incoming message are stored on the email server. References to these attachments are included in the name-value pairs that the communications drivers pass to Communications Inbound Receiver. The workflows that Communications Inbound Receiver invoke delete all file attachments when these attachments are no longer needed.

Communications Inbound Receiver takes the incoming message data and serializes it to a disk-based queue. The disk is used instead of memory for the following reasons:

• Persistence. If the computer fails, then the queued events are not lost.
• Memory. Storing on disk reduces Communications Inbound Receiver 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 the UTF-8 character set, which translates 16-bit Unicode characters into 8-bit characters. Each event always has a file name prefix of CIR.

If necessary, then you can shut down the Communications Inbound Receiver and the Communications Inbound Processor components. For information about shutting down Siebel Server components, see Siebel System Administration Guide.

Related Topics

Event States

State Transitions

Event Processing

Errors Encountered While Processing Events

Logged Event Types and Subtypes