Siebel Performance Tuning Guide > Tuning Siebel Communications Server >

Guidelines for Siebel Email Response Tuning

Using your hardware resources optimally, and configuring your system appropriately, can help you to achieve your performance goals. Consider your resources and requirements carefully, and test and monitor system performance on a continual basis.

Review information presented in Siebel Email Administration Guide, Siebel CTI Administration Guide, relevant third-party documentation, and other sources.

Configuring CommInboundRcvr Threads

Each CommInboundRcvr task runs multiple threads to process inbound email. To determine the number of threads, set the parameters MinThreads and MaxThreads. If extra CPU capacity exists on a given server computer, then you can run more threads for each applicable CommInboundRcvr task.

Managing Email Processing Directories

By default, CommInboundRcvr temporarily writes the content of inbound email messages into subdirectories of the Siebel Server installation directory, until the messages can be processed by the applicable response group and workflow process.

You can use parameters for the Internet SMTP/POP3 Server or Internet SMTP/IMAP Server communications driver to specify alternative directory locations for incoming email, processed email, sent email, and email messages representing certain other processing statuses. You can also set certain driver parameters to specify whether to save or delete processed email messages, for example.

• You must consider the resource requirements for temporary email processing directories when you set up your system.
• Do not delete messages from incoming or queued email directories. Email messages written to processed or sent directories can subsequently be deleted or saved, according to your needs.
• Because of the frequency by which CommInboundRcvr processing writes to temporary email processing directories, the disk must be defragmented regularly.

For more information about email processing directories, see Siebel CTI Administration Guide and Siebel Email Administration Guide.

Reviewing Performance Impact of Activity Creation

For each email work item, an activity record is created in the S_EVT_ACT table and related tables.

Attachments to such activity records, for inbound and outbound messages, are stored in the Siebel File System.

As you plan your deployment, you must consider how such records are created and managed, review the indexing and layout of applicable database tables, and review the performance impact of generating activity records.

In addition, you must consider the resource requirements for the Siebel File System for storing activity attachments.

The FSMSrvr server component generally runs on the same Siebel Server computers where you are running CommInboundRcvr and CommOutboundMgr.

NOTE:  Because of the frequency by which Siebel Email Response processing writes to the Siebel File System, the disk must be defragmented regularly.

For more information about activity attachments stored for inbound email, see Siebel CTI Administration Guide and Siebel Email Administration Guide.

Configuring Logging for Siebel Email Response

Logging data can be analyzed as part of performance monitoring or tuning, as described in Monitoring Siebel Application Performance with Siebel ARM.

Higher levels of logging provide more data to help you resolve system errors or performance issues; this is appropriate for system testing. For production systems, however, logging levels must be reduced to improve performance.

For the Internet SMTP/POP3 Server or Internet SMTP/IMAP Server communications driver, an applicable parameter is LogDebug. For details, see Siebel CTI Administration Guide.

Applicable event log levels for Siebel Email Response include those for task execution, workflow step execution, workflow process execution, and workflow performance.