Move to a production database for LSF

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.

For more detailed information, see the Platform LSF documentation.

  1. Create a database schema for your commercial database.
  2. Stop the reporting services.

    Stop the derbydb (if you are using the Derby demo database), jobdt, plc, and purger services.

  3. If you are using the Derby demo database, disable automatic startup of the derbydb service.
  4. If you are in UNIX, copy the Oracle JDBC driver into the PERF and GUI library directories.
    You need to copy the Oracle JDBC driver to the following directories:
    • LSF_TOP/perf/version_number/lib

    • LSF_TOP/gui/version_number/tomcat/common/lib

  5. Configure your database connection.
  6. Restart the reporting services.

    Restart the jobdt, plc, and purger services.

  7. Restart the Platform Management Console.
    Note:

    The Platform Management Console will be unavailable during this step.

    1. In the command console, stop the WEBGUI service.

      egosh service stop WEBGUI

    2. Restart the WEBGUI service.

      egosh service start WEBGUI

The report data will now be loaded into the production database and the Console will use the data in this database.