Bookshelf v7.5: Administering Communications Inbound Manager

Siebel Communications Server Administration Guide > Administering Siebel Communications Server >

Administering Communications Inbound Manager

This section describes how to administer the server component Communications Inbound Manager. The short name for this component is CommInboundMgr.

The Communications Inbound Manager processes inbound work items, such as inbound email messages received with Siebel eMail Response implementations.

This server component uses generic configuration parameters and does not need to be configured. However, some parameters belonging to the SMTP Subsystem can optionally be specified for the server component, as described in Configuring Parameters for Communications Inbound Manager.

Running Communications Inbound Manager

When the Communications Management component group is enabled, the Communications Inbound Manager component is started automatically. For any machine on which you do not want to run Communications Inbound Manager, configure the Siebel Server not to start it.

Communications Inbound Manager is a request-mode server component. It relies on the services of the Server Request Broker server component. This component must be running on the Siebel Server for communications to be processed successfully.

NOTE: If a messaging server, such as an email server, is restarted, then the Communications Inbound Manager server component that connects to it must also be restarted.

As a request-mode component, Communications Inbound Manager is subject to the requirements described in Synchronizing Request-Mode Server Components.

For more information about configuring, starting, and stopping Siebel Server components, refer to Siebel Server Administration Guide.

Configuring Parameters for Communications Inbound Manager

You can specify values for parameters for the Communications Inbound Manager server component. The parameters listed here, which belong to the SMTP Subsystem, can optionally be specified for the server component, the Siebel Server, or the enterprise. Each higher-level specification provides a default value that can be used if the parameter is not set at a lower level.

Administrator Email Address. Specify a value for the Administrator Email Address parameter, to provide an administrator email address to send messages to in case of inbound communications processing errors, when no such address is defined for the response group. (This parameter is specific to CommInboundMgr.)

Default Administrator Address. Specify a value for the Default Administrator Address parameter, to provide an administrator email address to send messages to in case of server errors, such as when the database connection has been broken. (This parameter is part of the SMTP Subsystem.)

Event Queue Directory. Specify a value for the Event Queue Directory parameter, to provide the name of the directory in which to store queued events. Use this parameter to specify a value to override the default location in the "bin/queued" directory. (This parameter is specific to CommInboundMgr.)

SMTP Server Name. Specify a value for the SMTP Server Name parameter, to provide the name of the SMTP server that will be used to send email to the administrator. (This parameter is part of the SMTP Subsystem.)

Activity Attachments Stored for Inbound Email

For each inbound email message that has been processed by Communications Inbound Manager, an activity record is created, using activity type Email - Inbound. The original content of the email is saved in the form of one or more attachments to this activity record.

The text parts of the original email message are saved in an attachment file named OriginalMsg.txt. For a plain-text message or the text component of a multipart MIME alternate message, OriginalMsg.txt includes the message headers and message body text. For an HTML-only email message (not multipart), OriginalMsg.txt contains the message headers and message body text extracted from the HTML.

Embedded messages cause the creation of attachment files that contain the embedded message's header and any text parts. These files are named EmbeddedMsgpartspecifier.txt, where partspecifier represents the file's placement in the message's embedding structure—for example, EmbeddedMsg01.txt, EmbeddedMsg3.4.txt, and so on.

For an HTML email message, all HTML components are saved in one or more attachment files. These files are named texthtmlpartspecifier.htm, where partspecifier represents the file's placement in the message's embedding structure—for example, texthtml01.htm, texthtml3.4.htm, and so on.

Any attachments to the original email message are also saved as attachments to the activity record, using their original file names.

If the original message is more than 15,000 characters long (including any HTML markup), then the full message is saved as another attachment, named SiebelLongEmailBody.txt (for plain-text messages) or SiebelLongEmailBody.htm (for HTML messages).