Siebel Performance Tuning Guide > Tuning Siebel Communications Server > Guidelines for Session Communications Tuning >

Configuring Logging for Session Communications

This topic is part of Guidelines for Session Communications Tuning.

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.

Log-related parameters applicable to session communications are summarized below. The Siebel Application Object Manager component logs activity related to the user's client session, including usage of the communications toolbar, screen pops, and so on. The CommSessionMgr logs activity related to this component, such as commands and events for the communications driver.

The logging for Siebel Application Object Manager and CommSessionMgr are written to separate files for each user. Typically (though not necessarily), these logging mechanisms both write into the same set of files. This makes it easier to monitor or troubleshoot issues related to session communications for a particular user session. For details on these logging parameters, see Siebel CTI Administration Guide.

Siebel Application Object Manager Logging Parameters

Siebel Application Object Manager parameters that log session communications activity include:

• CommLogFile. Specifies the name of the log file (default value is SComm.log). A separate log file is created for each agent session, in the form SComm_username.log.
• CommLogDebug. Specifies whether log files must contain extra detail. Setting to FALSE provides better performance.
• CommMaxLogKB. Specifies the maximum size of log files.
• CommReleaseLogHandle. Specifies that the log file handle must be released periodically. The default setting of TRUE provides better performance.

CommSessionMgr Logging Parameters

CommSessionMgr parameters that log session communications activity include:

• LogFile. Specifies the name of the log file (default value is SComm.log). A separate log file is created for each agent session, in the form SComm_username.log.
• LogDebug. Specifies whether log files must contain extra detail. Setting to FALSE provides better performance.
• MaxLogKB. Specifies the maximum size of log files.
• ReleaseLogHandle. Specifies that the log file handle must be released periodically. The default setting of TRUE provides better performance.