LSF Version 7.3 - Administering Platform LSF

Disable the Reporting Feature
650 Administering Platform LSF
Disable the Reporting Feature
Prerequisites: You mus t h ave root or lsfadmin access in the master host.
1 Disable the LSF events data logging.
a Define or edit the
ENABLE_EVENT_STREAM parameter in the lsb.params
file to disable event streaming.
ENABLE_EVENT_STREAM = N
b In the command console, reconfigure the master host to activate these
changes.
badmin reconfig
2 If your cluster is EGO-enabled, disable the EGO allocation events data logging.
a Define or edit the
EGO_DATA_ENABLE parameter in the ego.conf file to
disable data logging.
EGO_DATA_ENABLE = N
b In the command console, restart EGO on the master host to activate these
changes.
egosh ego restart master_host_name
3 Stop the reporting services.
Stop the
derbydb (if you are using the Derby demo database), jobdt, plc, and
purger services as described in Stop or restart reporting services on page 494.
4 Disable automatic startup of the
derbydb (if you are using the Derby demo
database),
jobdt, plc, and purger services as described in Disable automatic
startup of the reporting services on page 494.
Move to a Production Database
Move the reporting feature to a production database.
Prerequisites: The commercial database is properly configured and running:
❏ You have a user name, password, and URL to access the database server.
❏ There is appropriate space in the database allocated for the reporting feature.
The Derby demo database is not supported for any production clusters. To produce
regular reports for a production cluster, you must use a supported commercial
database. The reporting feature supports Oracle 9i, Oracle 10g, and MySQL 5.x
databases.
All data in the demo database will not be available in the production database. Some
of your custom reports may not be compatible with the production database if you
used non-standard SQL code.
1 Create a database schema for your commercial database.
❖ If you are using an Oracle database, create a database schema as described
in Create an Oracle database schema on page 651.