This package substitues the obsolete logService. A new requirement whereby database technologies other than ORACLE had to be dropped came in around spiring 2007. This new requirement meant the re-writing of the logService package, which was higly dependent on MySQL. This opportunity was taken to refactorize the code, especially the log manager, which was never very user friendly. Currently, the database access in C++ code is written using CORAL, which hides the underlying technology. For the log manager, JAVA was the language chosen, since it brings in the flexibility requiered to make this tool more intuitive. The resulting java application can be run from the console, or remotely using the Java Web Start technology.
The ls package has been used in the M5 with positive feedback. Issues that raised have been fixed. It would be interesting to run a few tests for the M6 to acquire statistics and performance on the lsReceiver and the database side.
Add an option to display statistics, internal and from IS.
The Database schema has changed. Whereas before a table per partition was created, in this version only on table is used. This table is internally segmented by Oracle - the segments are partition based. Furthermore, the user name, session ID and severity are configured as indexes to speed up access. Initial reports from users confirm that this new schema is 'faster' than the previous. Changing the database schema means that backward compatibility is not provided.
Usage: log_manager
Instruction on how to use to be written.
The Log Manager can also be run using Java Web Start technology from the link:
If possible, it is preferrable to launch this tool as a Java application rather than from the link above.
Usage: lsReceiver -p partitionName -u userName -n ISserverName -c connectionString
Options/Arguments:
-p partitionName Partition name
-u userName User name
-n ISserverName Name of the Information Service to publish the message rate into.
-c connectionString Database connection string.
"The log receiver subscribes to the MRS service to receive and log on a database messages produced by TDAQ applications."
Usage: logTest -p partitionName -l level -c connectionString
Options/Arguments:
-p partitionName Partition name
-l level Level of Complexity of the test [1: open/close - 2: tests the Log Service Infrastructure].
-c connectionString Database connection string.
"Test binary for the Log Receiver application."
Usage: logSelect -p partitionName -xyz searchCriteria -c connectionString
Options/Arguments:
-p partitionName Partition name
-xzy searchCriteria Combination of argument options to define the search criteria. Do a logSelect -h for further information.
-c connectionString Database connection string.
"Application to retrieve log messages for a given partition according to the command arguments. By default, messages are dumped on std::cout"
Usage: logDelete -p partitionName -xyz searchCriteria -c connectionString
Options/Arguments:
-p partitionName Partition name
-xzy searchCriteria Combination of argument options to define the search criteria. Do a logSelect -h for further information.
-c connectionString Database connection string.
"Application to remove log messages for a given partition according to the command arguments."
Usage: logCleanDatabase -c connectionString
Options/Arguments:
-c connectionString Database connection string.
"Application to clean the database by removing all the existing tables."