Move to a production database for EGO

The commercial database must be properly configured and running:

  • You have a user name, password, and URL to access the database server.

  • Your database server account has access to create triggers, sequences, tables, and stored procedures.

  • There is appropriate space in the database allocated for the reporting feature.

  • You installed the latest JDBC driver for the commercial database.

    The JDBC driver for an Oracle database (ojdbc14.jar or newer) is available from the following URL:

    http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html

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 and 10g databases for production clusters.

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 an Oracle database schema for your commercial database.
    1. Navigate to the database schema directory.

      For example,

      Linux: cd EGO_TOP/perf/ego/version_number/DBschema/Oracle

      Windows: cd EGO_TOP\perf\ego\version_number\DBschema\Oracle

    2. Run the scripts to create a database schema.

      sqlplus user_name/password@connect_string @egodata.sql data_tablespace index_tablespace

      where
      • user_name is the user name on the database server.

      • password is the password for this user name on the database server.

      • connect_string is the named SQLNet connection for this database.

      • data_tablespace is the name of the tablespace where you intend to store the table schema.

      • index_tablespace is the name of the tablespace where you intend to store the index.

  2. Stop the reporting services.

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

  3. If you are using the Derby demo database, disable automatic startup of the derbydb service.
  4. Copy the Oracle JDBC driver into the PERF and GUI library directories.
    You need to copy the Oracle JDBC driver to the following directories:
    • Linux:

      • EGO_TOP/perf/version_number/lib

      • EGO_TOP/gui/version_number/tomcat/common/lib

    • Windows:

      • EGO_TOP\perf\version_number\lib

      • EGO_TOP\gui\version_number\tomcat\common\lib

  5. Configure your database connection.
    1. Launch the database configuration tool.
      • In UNIX (X-Windows only), run EGO_TOP/perf/version_number/bin/dbconfig.sh.

      • In Windows, run EGO_TOP\perf\version_number\bin\dbconfig.bat.

    2. In the User ID and Password fields, specify the user account name and password with which to connect to the database and to create your database tablespaces.
      Note:

      This user account must have been defined in your database application, and must have read and write access to the database tables. In general, this is the name you used to create your Oracle tablespaces.

    3. In the JDBC driver field, select the driver for your commercial database.
    4. In the JDBC URL field, enter the URL for your database.

      This should be similar to the format given in Example URL format.

    5. In the Maximum connections field, specify the maximum allowed number of concurrent connections to the database server.

      This is the maximum number of users who can produce reports at the same time.

  6. Restart the reporting services.
  7. Restart the Platform Management Console.
    Note:

    The Platform Management Console will be unavailable during this step.

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

      egosh service stop WEBGUI

      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.