|
Configuration of BobiDbdLogTest
Logs related to the Dashboards Processing and Dashboards Cache servers are periodically checked by this test, so that problem events can be quickly captured and resolved.
The default parameters associated with this test are:
The LOG DIRECTORY is the directory to which logs from various nodes installed on a host are written. Typically, these logs are written to ‘*.glf’ files in the ‘logging’ directory of the BOBI installation. If SAP BOBI is installed in the C drive of a Windows host, the logging directory will be available in the following location by default: C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\
Log file names are generally of the following fomat : <server abbreviation>_<node name>.<server type>*.glf’ For e.g., cms_SAPBOBI.CentralManagementServer_trace.001284 is one of the log trace files from the Central Management Server running in the node called SAPBOBI. Server abbreviation in this case is cms. The default value for this parameter has hence been set as a comma separated list of server descriptions and their abbreviations as follows : <server description>:<server abbreviation>. For trace files of the Dashboards Processing and Cache servers, this parameter has been by default set as: Dashboard Processing servers:xcproc,Dashboard cache servers:xccache.
Enter the specific patterns of messages 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 ORA:ORA-* in the SEARCHPATTERN text box. This indicates that “ORA” is the pattern name to be displayed in the monitor interface. “ORA-*” indicates that the test will monitor only those lines in the log file which start with the term “ORA-”. Similarly, if your pattern specification reads: offline:*offline, then it means that the pattern name is offline and that the test will monitor those lines in the log file which end with the term offline.
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: ORA:ORA-*,offline:*offline*,online:*online.
Each of these patterns will be searched for in every log file that is present in the configured LOG DIRECTORY.
Specify two numbers in the format x:y in the LINES text box. 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,2:1 as the value for LINES and if the corresponding value in the SEARCHPATTERN field is like ORA:ORA-*,offline:*offline*,online:*online then:
0:0 will be applied to ORA:ORA-* pattern
1:1 will be applied to offline:*offline* pattern
2:1 will be applied to online:*online pattern
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:*fatal*,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 ‘fatal’ 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 ‘fatal’ 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.
The ROTATINGFILE flag governs the display of descriptors for this test in the eG monitoring console.
If this flag is set to true, the descriptors of this test will be displayed in the following format: <Full_Path_to_LogDirectory>:<ServerAbbreviation>. For instance, if the LOG DIRECTORY parameter is set to c:\SAPBOBI\logs and ROTATINGFILE is set to true, then, your descriptor will be of the following format: c:\SAPBOBI\logs:<ServerAbbreviation>. On the other hand, if the ROTATINGFILE flag had been set to false, then the descriptors will be of the following format: <LogDirectory>:<ServerAbbreviation> &$45; i.e., logs:<ServerAbbreviation> in the case of the example above.
If UTF-8 encoding is to be used for reading the log files in the configured LOG DIRECTORY, then, set the USEUTF8 flag to true. By default, this flag is set to false.
If UTF-16 encoding is to be used for reading the log files in the configured LOG DIRECTORY, then, set the USEUTF16 flag to true. By default, this flag is set to false.
By default, the ENCODEFORMAT flag is set to none, indicating that no encoding format applies by default. However, if the test has to use a specific encoding format for reading from the log files in the LOG DIRECTORY, then you will have to provide a valid encoding format here - eg., UTF-8.
PROVIDER parameter appears only if the Mode is set to JMX. This test uses a JMX Provider to access the MBean attributes of the target Java application and collect metrics. Specify the package name of this JMX Provider in the PROVIDER textbox. By default, this parameter is set to default indicating that this test automatically discovers the JMX provider and report metrics.
The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY.
To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the DETAILED DIAGNOSIS capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.
The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
- The eG manager license should allow the detailed diagnosis capability
- Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
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.
|