Move to a production database

  • 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.

  • Download 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 JDBC driver for SQL Server (jdbc-sqlserver.jar) is available from the following URL:

      http://msdn2.microsoft.com/en-us/data/aa937724.aspx

  1. To create the SOAM and EGO database schemas, change to the applicable schema directory on the master host and run the script. Refer to the following table for the location of schema directories.

    For example, for Oracle,


    Database Schema

    O/S

    Location

    SOAM

    Linux/UNIX

    EGO_TOP/perf/soam/version_number/DBschema/Oracle

    Windows

    EGO_TOP\perf\soam\version_number\DBschema\Oracle

    EGO

    Linux/UNIX

    EGO_TOP/perf/ego/version_number/DBschema/Oracle

    Windows

    EGO_TOP\perf\ego\version_number\DBschema\Oracle


    • For Oracle databases, use sqlplus to run the scripts.

      EGO database schema:

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

      SOAM database schema:

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

      where
      • user_name is the user name on the database.

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

      • 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 index tablespace of the reporting database.

    • For SQL Server databases, use osql to run the scripts.

      osql ‑U user_name ‑P password ‑d db_name ‑i @update_script

      where

      • user_name is the user name on the database

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

      • db_name is the name of the reporting database

      • update_script is the name of the script

  2. Stop the reporting services.

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

    egosh service stop purger plc derbydb

  3. If you are using the Derby demo database, disable automatic startup of the derbydb service; refer to Disable automatic startup of the reporting services.
  4. Copy the JDBC driver (which you downloaded) into the PERF and GUI library directories on all management hosts that are expected to run PERF and PMC services.
    You need to copy the JDBC driver to the following directories:
    • Linux/UNIX:

      • 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.

    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.

    egosh service start plc purger

  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. Note that some of your custom reports may not be compatible with the production database if you used non-standard SQL code.