Enable the Derby database

It is not mandatory to configure the Derby database during the installation. If you later find that you need to use the reporting feature and do not have access to a production database, you will need to enable the Derby database.

Note:

The Derby database is not supported for any production clusters.

  1. Navigate to the EGO service directory.

    For example,

    Linux/UNIX: cd EGO_TOP/eservice/esc/conf/services

    Windows: cd EGO_TOP\eservice\esc\conf\services

  2. Edit the derby_service.xml service configuration file.
  3. In the
    <ego:ResourceRequirement>
    tag, replace
    @EMBEDDED_DB_HOST@
    with the name of the host in which you intend to run the Derby database.

    For example, if you intend to run the Derby database in hostM,

    <ego:ResourceRequirement>select('hostM')</ego:ResourceRequirement>

  4. Launch the database configuration tool.
    • In UNIX (X-Windows only), run dbconfig.sh.

    • In Windows, run dbconfig.

    1. In the User ID and Password fields, use
      app
      as both the user name and password for the Derby database.
    2. Verify that the correct JDBC driver is selected for the Derby database. It should be org.apache.derby.jdbc.ClientDriver
    3. Verify the database URL. It should resemble the following: jdbc:derby://hostname:1527/app:
    4. Click Test to test the database connection.
    5. Click OK to save the configuration and exit the utility.
  5. In the command console, stop the Derby service.

    egosh service stop derbydb

    Note:

    This step is necessary because the derbydb service may run even without explicitly enabling the Derby database.

  6. In the command console, restart EGO on the master host to activate these changes.

    egosh ego restart master_host_name