Configuring Shared or Separate Logging
An administrator can review log files for the Communications Outbound Manager component to monitor its performance and to monitor user activities that invoke this component.
Depending on how you configure the Communications Outbound Manager server component, a single log file might be generated for all requests, or a separate log file might be generated for each request (the default). The parameter that modifies this setting is called LogUseSharedFile.
Log files are written to the log subdirectory
of the Siebel Server installation directory.
Set LogUseSharedFile according to how the server component is generally used as follows:
For miscellaneous uses, including supporting the Send commands, sending auto-acknowledgement messages and replies for Siebel Email Response, and sending several outbound requests to a small number of recipients, you can set LogUseSharedFile to TRUE to reduce clutter in your
logdirectory.For high-volume outbound communication requests, however, you can leave this parameter set to FALSE to generate a single log file for each request that you can analyze. LogUseSharedFile is FALSE by default.
The log file names vary according to how you set LogUseSharedFile as follows:
When a single log file is generated for all requests, the file name is in the form CommOutboundMgr_xxx.log, where xxx is the ID number for the main Communications Outbound Manager task.
When a separate log file is generated for each request, the file names are in the form CommOutboundMgr_xxx.log, where xxx is the ID number for the Communications Outbound Manager task applicable to the specific communication request.
The Outbound Communications Manager business service, run on the Siebel Server, uses the same naming convention to generate log files in the same location.