The SiebelErrLogTest monitors Siebel web server error log files for new errors.

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed. 

• In the HOST text box, the host name of the server for which the test is to be configured has to be specified.

• Specify the PORT at which the HOST listens.

• In the LINES text box, specify two numbers in the format x:y. This means that when a line in the log file matches a particular pattern, then x lines before the matched line and y lines after the matched line will be reported in the detail diagnosis output (in addition to the matched line). The default value here is 0:0. Multiple entries can be provided as a comma-separated list.

  If you give 1:1 as the value for LINES, then this value will be applied to all the patterns specified in the SEARCHPATTERN field. If you give 0:0,1:1 as the value for LINES and if the corresponding value in the SEARCHPATTERN field is like Gen_errors:Generic*,Critical_errors:*Error* then:

  0:0 will be applied to Gen_errors:Generic* pattern
  1:1 will be applied to Critical_errors:*Error* pattern

• By default, the ROTATINGFILE parameter is set to FALSE. To instruct the eG Enterprise to monitor newer log files also, set this parameter to TRUE. Otherwise, set it to FALSE . 

• In the ALERTFILE text box, specify the path to the log file to be monitored. For eg., C:/sea703/SWEBApp/LOG/Siebel_Web_log.txt. Multiple log file paths can be provided as a comma-separated list.

  Also, instead of a specific log file, the path to the directory containing log files can be provided - eg., C:/sea703/SWEBApp/LOG. This ensures that eG Enterprise monitors the most recent log files in the specified directory. If while monitoring a log file in a directory a newer log file gets added to that directory, then eG will first finish monitoring the original log file and then start monitoring the new one. Specific log file name patterns can also be specified, so that the log file(s) monitored are restricted to files that match the specified patterns. For example, to monitor the latest log files with names containing the strings 'siebel' and 'log', the parameter specification can be, C:/sea703/SWEBApp/LOG/*siebel*,C:/sea703/SWEBApp/LOG/*log*. Here, '*' indicates leading/trailing characters (as the case may be).

  The eG monitor interface will report one set of measurements for every configured path. You can also configure the path in the following format:Name@logfilepath. Here, Name represents the display name of the path being configured. Accordingly, the parameter specification for the 'siebel' and 'log' example discussed above can be: siebel@C:/sea703/SWEBApp/LOG/*siebel*,log@C:/sea703/SWEBApp/LOG/*log*. In this case, the display names 'siebel' and 'log' will alone be displayed as descriptors of this test, and not the individual paths.

• In the SEARCHPATTERN text box, enter the specific patterns of errors to be monitored. The pattern should be in the following format: {PatternName}:{Pattern}, where {PatternName} is the pattern name that will be displayed in the monitor interface and {Pattern} is an expression of the form - *expr* or expr or *expr or expr*, etc. A leading '*' signifies any number of leading characters, while a trailing '*' signifies any number of trailing characters.

  For example, say you specify Gen_errors:Generic* in the SEARCHPATTERN text box. This indicates that "Gen_errors" is the pattern name to be displayed in the monitor interface. "Generic*" indicates that the test will monitor only those lines in the log file which start with the term "Generic".

  A single pattern may also be of the form e1+e2, where + signifies an OR condition. That is, the {PatternName} is matched if either e1 is true or e2 is true.

  Multiple search patterns can be specified as a comma-separated list. For example: Gen_errors:Generic*,Critical_errors:*Error*.

  If the ALERTFILE specification is of the format Name@logfilepath, then the descriptor for this test in the eG monitor interface will be of the format: Name:PatternName. On the other hand, if the ALERTFILE specification consists only of a comma-separated list of log file paths, then the descriptors will be of the format: LogFilePath:PatternName.

• Provide a comma-separated list of patterns to be excluded from monitoring in the EXCLUDEPATTERN text box. For example, *critical*,*generic*. By default, this parameter is set to 'none'.

• By default, the UNIQUEMATCH parameter is set to FALSE, indicating that, by default, the test checks every line in the log file for the existence of each of the configured SEARCHPATTERNS. By setting this parameter to TRUE, you can instruct the test to ignore a line and move to the next as soon as a match for one of the configured patterns is found in that line. For example, assume that Pattern1:*Generic*,Pattern2:*Error* is the SEARCHPATTERN that has been configured. If UNIQUEMATCH is set to FALSE, then the test will read every line in the log file completely to check for the existence of messages embedding the strings 'Generic' and 'Error'. If both the patterns are detected in the same line, then the number of matches will be incremented by 2. On the other hand, if UNIQUEMATCH is set to TRUE , then the test will read a line only until a match for one of the configured patterns is found and not both. This means that even if the strings 'Generic' and 'Error' follow one another in the same line, the test will consider only the first match and not the next. The match count in this case will therefore be incremented by only 1. 

• Once the above value is provided, click on the UPDATE button to register the changes made.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.