Running the Configuration Analyser

Each probe that supports the Configuration Analyser is supplied with a JAR file (probe_name.check.jar). This file contains details of the tests to be performed and a set of predefined messages library. Using this JAR file, the analyser runs the tests against the probe configuration test file, and writes the related messages taken from the messages library to the probe log file.

When the probe launches the Configuration Analyser, the analyser runs a series of checks on the probe. The resultant output is stored in $OMNIHOME/log/probe_name.check.log (the test file).

The Configuration Analyser checks the syntax of the test file against the rules defined in the $OMNIHOME/probes/arch/ConfigAnalyser.xsd file.

The Configuration Analyser then runs sequentially through all the tests detailed in the xml file inside $OMNIHOME/probes/arch/probe_name.check.jar, outputting any appropriate suggestions from the internationalized message file also in the jar file.

Checks performed by the Configuration Analyser

The Configuration Analyser performs the following checks for all probes:

  • Whether the primary ObjectServer is running.
  • Whether the rules and properties files are present.
  • Whether a secondary ObjectServer is configured.
  • Whether the Probes Rules Syntax Checker is installed.
  • Whether the rules file is syntactically correct.
  • Whether there is space for log files.

All other tests that the analyser performs are specific to each individual probe.

Running the Configuration Analyser on UNIX and Linux operating systems

To run the Configuration Analyser on UNIX and Linux operating systems, run the probe from the command line using -check as an additional argument.

Note: You can specify additional arguments on the command line along with -check; these will override any equivalent settings found in the properties file.

Running the Configuration Analyser on Windows operating systems

The way you run the Configuration Analyser on Windows operating systems depends on how you run the probe.

If you run the probe using a batch file, run the following command:

probe_batch -check

Note: You can specify additional arguments on the command line along with -check; these will override any found in the properties file.

Where probe_batch is the name of the batch file that you use to run the probe.

If you run the probe directly, without using a batch file, run the following command:

run_analyser.bat -probebin probe_script -probename probe_name

Where probe_script is the probe binary name or the launcher script and probe_name is the name of the probe binary without the nco_p_ prefix.

Note: You can specify additional arguments on the command line along with -check; these will override any found in the properties file. For example, the following command runs the Configuration Analyser on the ODBC Probe specifying that the server is set to RAG:

run_analyser.bat -probebin nco_p_odbc -probename odbc -server RAG

Configuration Analyser Log file

On completion of these tests, the Configuration Analyser outputs a status message. This status message states that either all the tests were successful, or that details of any configuration errors or suggestions have been written to the probe log file $OMNIHOME/log/probe_name.check.log.

Consult the log file for information about how to correct or improve the configuration of the probe.