Default Parameters for AppChecksumTest

This test creates a checksum by calculating the binary values (using a pre-defined algorithm) of every file configured for monitoring and storing the results. Each time the test runs, a new checksum is calculated and compared with the existing checksum. If there is a non-match, the test promptly alerts administrators to it, as it could be because of errors in the file.

This page depicts the default parameters that need to be configured for the AppChecksumTest test.

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

• Provide a comma-separated list of the full path to directories and/or files that you want the test to monitor in the DIRECTORY PATH text box. For example, your specification can be: /usr/logs/err.log,/Oracle/logs where /usr/logs/err.log is a file and /Oracle/logs is a directory. Where a directory is provided, all files within that directory will be monitored and will appear as descriptors of the test.

  Your specification can also be of the following format: DisplayName@Path_to_Directory_or_File. For example: Error@/usrlogs/err.log. Multiple such specifications can be provided as a comma-separated list – for instance, Error@/usrlogs/err.log,Oracle@/Oracle/logs,Web@/web/weblogs. In this case, the DisplayNames such as Error, Oracle, and Web will be displayed as the first-level descriptors of this test, and the files in each configured directory will be displayed as the second-level descriptors.
  Note:
  • When you provide the path to a directory as part of the DIRECTORY PATH specification, only those files available within that directory will be monitored; sub-directories inside that directory and files within the sub-directories will not be considered.
  • If your DIRECTORY PATH specification includes the path to individual files, make sure that you provide the file extensions along with the file names.

• If you do not want the test to monitor specific patterns of files in the configured directories, then provide a comma-separated list of file name patterns to be excluded from monitoring, in the following format: DisplayName@FileNamePattern. The DisplayNames you use here should be the same as the DisplayNames you use as part of your DIRECTORY PATH specification. For instance, if your DIRECTORY PATH specification is, Oracle@/Oracle/logs,Web@/web/weblogs, then, your EXCLUDE PATTERN configuration may be: Oracle@*info*.log,Web@gen*.log,Web@*minor.log. This configuration holds that in the /Oracle/logs directory, all files with names that embed the string info should be configured and in the /web/weblogs directory, all files with names that begin with the string gen and all files with names that end with string minor should be ignored.

  If your DIRECTORY PATH specification does not include DisplayNames and instead includes a comma-separated list of directory paths - eg., /usr/logs,/agent/logs - then your EXCLUDE PATTERN specification should be of the following format: DirectoryPath@FileNamePattern. For instance, if your DIRECTORY PATH specification is /usr/logs,/agent/logs, then your EXCLUDE PATTERN configuration may be:/usr/logs:*minor*.log,/agent/logs:info*.log,/agent/logs:*warn.log. According to this configuration, the test will ignore all files with names that embed the string minor in the /usr/logs directory. In the /agent/logs directory, the test will ignore the files with names that begin with info and the files with names that end with warn.
  By default, the EXCLUDE PATTERN is set to none, indicating that no files are excluded from monitoring, by default. This is the ideal setting if your DIRECTORY PATH specification does not include any directories, and is instead configured with the path to individual files.

• The USE EXE flag is applicable to Windows platforms only. By default, this flag is set to No. This implies that, by default, the test uses a predefined Java class named Message Digest to compute the checksum of configured files. In some flavors of Windows, this Java class may not work. In such cases, you can instruct the test to use an executable named exf.exe to compute checksum. For this, set the USE EXE flag to Yes.

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

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz” and $port will be changed to “80” when configuring a test.