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

Configuring Communications Outbound Manager

For Communications Outbound Manager, you can configure a parameter that specifies how Siebel bookmarks are generated, configure a parameter that specifies whether logging must use shared or separate files, and configure logging levels. For more information about configuring logging for server components, see Siebel System Administration Guide.

Configuring Siebel Bookmarks

To support the Attach Bookmark setting for advanced communications templates, the Siebel administrator must specify a value for the WebServer server component parameter for Communications Outbound Manager.

This parameter specifies a string that identifies the Web server and Application Object Manager to include in the URL. The URL has the following form:

http://web_server/application_object_manager

To access the bookmarked record, the recipient users must have access to the specified Web server and Application Object Manager. For more information about using the Attach Bookmark setting for advanced templates, see Fields for Templates.

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 log directory.
• 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.

Configuring Log Levels for Communications Outbound Manager

An administrator can set logging levels for Communications Outbound Manager to specify the degree of detail captured in the logs. Logging levels include:

• CommSrvrError (level 1). Lowest level of logging. The most severe errors are logged. Level 1 is the default.
• CommSrvrWarning (2). Moderate level of logging. More detail than level 1 is logged. Use this level for production.
• CommSrvrTrace (3). Moderately high level of logging. More detail than level 2 is logged.
• CommSrvrDebug (4). Highest level of logging. All errors and warnings and other events are logged. Use this level for testing purposes.

To configure log levels for Communications Outbound Manager

1. Navigate to the Administration - Server Configuration screen, then the Servers view.
2. Specify the Siebel Server on which Communications Outbound Manager runs.
3. In the Components list, select the record for the Communications Outbound Manager component.
4. Click the Events tab.
5. Select the record for the CommServer event type.
6. Specify one of the values described in this topic.