System Monitoring and Diagnostics Guide for Siebel Business Applications > Querying System Log Files >

Configuring the Log File Analyzer


Configure the Log File Analyzer (LFA) by accessing and editing the LFA configuration file, which has the default name logreader.cfg. The LFA uses the LFA configuration file when launched to reference Siebel Server locations, Siebel Web Server Extension (SWSE) plug-in locations, and other run-time details.

This task is the first step in Process for Analyzing Log Files with LFA. Once the LFA is configured, this step is optional unless further changes are necessary.

The default location for the LFA configuration file is the binary subdirectory of the Siebel Server root directory (for example, /siebsrvr/bin).

The LFA configuration file contains sections that configure which log files are analyzed by the utility and what content is reviewed. Edit the appropriate sections in the configuration file with a text editor. See Table 26 for LFA configuration file parameters and their descriptions. See Example of a Log File Analyzer Configuration File for an example of a typical configuration file.

Table 26. Log File Analyzer Configuration File Sections and Parameters
Section
Parameter
Description

[elements]

Siebel Server Identification Tag

Under the [elements] section, list Siebel Servers searchable by the LFA. Use the following format: Siebel Server Identification Tag = server, where Siebel Server Identification Tag is a unique tag name identifying the Siebel Server of interest. This tag can be the actual Siebel Server name, but can also be any other configurable value. For example:

[elements]

SiebelServer1=server

 

Siebel Web Server Extension Identification Tag

Under the [elements] section, list SWSE plug-ins searchable by the LFA. Use the following format: Siebel Web Server Extension Identification Tag = plug-in, where Siebel Web Server Extension Identification Tag is a unique tag identifying the SWSE plug-in of interest. This tag can be the actual SWSE plug-in name, but can also be any other configurable value. For example:

[elements]

SiebelSWSE1=plugin

[Siebel Server Identification Tag]

Path

Each Siebel Server identification parameter listed in the [elements] section has a respective section of its own with its name in square brackets. The path parameter of each Siebel Server section denotes the location of the associated log files for that Siebel Server. For example:

[SiebelServer1]

Path = //SiebSrv1/siebsrvr/log

[Siebel Server Identification Tag.Siebel Server Component Name]

shortname

List Siebel Server component display names in square brackets to allow the LFA to search for component references in log files. Add the Siebel Server component alias as the value for the shortname parameter. For example:

[SiebelServer1.Server Request Broker]

shortName=SRBroker

For a listing of Siebel Server components and their aliases, see Siebel System Administration Guide.

[Siebel Web Server Extension Identification Tag]

Path

Each SWSE plug-in identification parameter listed in the [elements] section has a respective section of its own with its name in square brackets. The path parameter of each SWSE plug-in section denotes the location of the associated log files for that SWSE plug-in. For example:

[SiebelSWSE1]

Path = //SWSE1/eappweb/log

[Render]1

event

Displays information on log events if enabled. Set to 1 to enable; set to 0 to disable.

 

subevent

Displays information on log sub events if enabled. Set to 1 to enable; set to 0 to disable.

 

loglevel

Displays information on log level of event subtypes. Set to 1 to enable; set to 0 to disable.

 

time

Displays log timing information in enabled.Set to 1 to enable; set to 0 to disable.

 

file

Displays log file path information if enbabled.Set to 1 to enable; set to 0 to disable.

1The parameter information in the [render] section is also controlled by using commands during the running of the LFA. See About Running Log File Analyzer Commands for further information.

NOTE:  Do not modify the sections entitled [schemes], [user], and [session].

Example of a Log File Analyzer Configuration File

The following example Log File Analyzer (LFA) configuration file is intended for a Siebel application with two Siebel Servers, named SiebSrv1 and SiebSrv2, and three Web servers with three Siebel Web Server Extensions (SWSE), named SWSE1, SWSE2, and SWSE3. The LFA configuration file also contains alias information on two Siebel Server components, Server Request Broker and Call Center Object Manager. Using this configuration file, the LFA searches all Siebel Server and SWSE log files, has the ability to search on the two Siebel Server components listed, and displays all information except log level and the log file path.

See Configuring the Log File Analyzer for descriptions of the individual sections and parameters.

[elements]

SiebSrv1=server

SiebSrv2=server

SWSE1=plugin

SWSE2=plugin

SWSE3=plugin

[SiebSrv1]

Path = //SiebSrv1/siebsrvr/log

[SiebSrv2]

Path = //SiebSrv2/siebsrvr/log

[SiebSrv1.Server Request Broker]

shortName=SRBroker

[SiebSrv2.Call Center Object Manager (ENU)]

shortName=SCCObjMgr

[SWSE1]

Path = //SWSE1/eappweb/log

[SWSE2]

Path = //SWSE2/eappweb/log

[SWSE3]

Path = //SWSE3/eappweb/log

[Render]

event=1

subevent=1

loglevel=0

time=1

file = 0

System Monitoring and Diagnostics Guide for Siebel Business Applications