Setting-Up an External Database

The Solution Manager server and the License Manager server store their information on a database:

  1. Solution Manager: environments, clusters and servers.
  2. Promotions: load balancing variables, revisions and deployments.
  3. License: global license and license usages.

They all use the same database to store this. By default, this is a local database included with the installation (Apache Derby). You can configure them to use an external database (all this information is stored in the same database).

Note

Only global administrators and Solution Manager administrators can do this change.

Note

When you do this change, only the global license is moved to the new database. The other information remains on the local database.

To do this, follow these steps:

  1. If you already defined environments/clusters/servers in the Tree Area, export them to a file. To do this, right-click on the root of this tree (on Solution Manager) and click Export.

    The information about revisions and deployments cannot be exported.

  2. Copy the jar file(s) of the JDBC driver of the database to the folder <SOLUTION_MANAGER_HOME>/lib/solution-manager-extensions.

  3. Restart these components:

    • License Manager server
    • Solution Manager server
    • Solution Manager administration tool

    You do not need to restart these components if the jar files of the driver were already in that folder.

  4. Open the Configuration menu (at the top) and click Solution Manager Database. In the new tab, enter the following parameters:

    • Database: select one of the supported databases:
      • Derby
      • Microsoft SQL Server
      • Oracle 11g
      • Oracle 12c
      • MySQL. Select this for the MySQL database or for the MySQL-compatible edition of Amazon Aurora.
      • PostgreSQL. Select this for the PostgreSQL database or for the PostgreSQL-compatible edition of Amazon Aurora.
    • Driver Class: class name of the JDBC driver. E.g. for Oracle oracle.jdbc.OracleDriver.
    • URL: JDBC URL to connect to your database server.
    • User and Password: credentials to connect to the database. This user account needs privileges to create tables and insert/update/delete rows in these tables.
Database configuration panel

Database configuration panel

Note

  • When you select the database Derby Embedded, the fields Driver Class, URI, Username and Password are not editable. It represents a connection to the Derby database included with the Solution Manager.

  • When you select the database MySQL, add the following parameters to the URL: useUnicode=true&characterEncoding=UTF-8. For example: jdbc:mysql://mysql.acme.com:3306/denodo_solution_manager?useUnicode=true&characterEncoding=UTF-8.

    That way, if you have views or other elements with non-ASCII characters, they will be stored in the database correctly. Note that the schema where this is stored needs to have these options: Default Charset = utf8 and Collation = utf8_unicode_ci.

  1. Click the save button save-btn. The Solution Manager checks that it can reach this database. You will be prompted to create the necessary tables. If you click Yes, they will be created automatically. Alternatively, you can create them manually using the scripts of the directory <SOLUTION_MANAGER_HOME>/conf/solution-manager/sql.

  2. Stop the License Manager server, Solution Manager server and Solution Manager administration tool.

  3. Start the License Manager.

    The License Manager will automatically store the license information in the external database.

  4. Start the Solution Manager server and the Solution Manager administration tool.

    Important

    It is important that you start the License Manager before the other components of this installation because first, the License Manager has to store the license on the external database. If you do not do it in this order, the Solution Manager will not start because it will not find a valid license.

  5. Log into the Solution Manager. If you already had defined environments, clusters and servers, now they are not there. The reason is that only the license is automatically copied to the new database.

    To restore the environments, clusters and servers, right-click on the root of tree and click Import. Select the file you exported on step #1.