LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 637
Reporting
Table 7: LSF reporting directory environment variables in Windows
Reporting services The reporting feature uses the following services.
◆ Job data transformer (jobdt)
◆ Loader controller (plc)
◆ Data purger (purger)
The Derby demo database uses the
derbydb service.
If your cluster has PERF controlled by EGO, these services are run as EGO services.
You need to stop and restart a service after editing its configuration files. If you are
disabling the reporting feature, you need to disable automatic startup of these
services, as described in Disable automatic startup of the reporting services on page
641.
Log files for these services are available in the
PERF_LOGDIR directory. There are
seven logging levels that determine the detail of messages recorded in the log files.
In decreasing level of detail, these are
ALL (all messages), TRACE, DEBUG, INFO, WARN,
ERROR, FATAL, and OFF (no messages). By default, all service log files log messages
of
INFO level or higher (that is, all INFO, WARN, ERROR, and FATAL messages). You can
change the logging level of the
plc service using the loader controller client tool as
described in Dynamically change the log level of your loader controller log file on
page 642, or the logging level of the other services as described in Change the log
level of your log files on page 642.
Job data
transformer
The job data is logged in the relational database in a raw format. At regular
intervals, the job data transformer converts this data to a format usable by the
reporting feature. By default, the data transformer converts the job data every hour
at thirty minutes past the hour (that is, at 12:30am, 1:30am, and so on throughout
the day).
To reschedule the transformation of data from the relational database to the
reporting feature, you can change the data transformer schedule as described in
Change the data transformer schedule on page 645.
If your cluster has PERF controlled by EGO, you can edit the
jobdt.xml
configuration file, but you need to restart the
jobdt service and EGO on the master
host after editing the file. The
jobdt.xml file is located in the EGO service
directory:
$PERF_LOGDIR Log files LSF_TOP/log/perf
$PERF_WORKDIR
Working directory LSF_TOP/log/perf
$PERF_DATADIR Data directory LSF_TOP/work/cluster_name/perf/data
Directory name Directory description Default file path
%PERF_TOP% Reports framework directory LSF_TOP\perf
%PERF_CONFDIR
% Configuration files LSF_TOP\conf\perf\cluster_name\conf
%PERF_LOGDIR% Log files LSF_TOP\log\perf
%PERF_WORKDIR%
Working directory LSF_TOP\log\perf
%PERF_DATADIR%
Data directory LSF_TOP\work\cluster_name\perf\data
Directory name Directory description Default file path