Setting-Up an External Database¶
The Solution Manager server and the License Manager server store their information on a database:
- Solution Manager: environments, clusters and servers.
- Promotions: load balancing variables, revisions and deployments.
- 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).
Only global administrators and Solution Manager administrators can do this change.
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:
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.
Copy the jar file(s) of the JDBC driver of the database to the folder
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.
Open the Configuration menu (at the top) and click Solution Manager Database. In the new tab, enter the following parameters:
Database: select the database. The supported ones are: Derby, Oracle 11g, Oracle 12c, SQL Server, MySQL and PostgreSQL.
Driver Class: class name of the JDBC driver. E.g. for Oracle
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.
Click the save button . 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
Stop the License Manager server, Solution Manager server and Solution Manager administration tool.
Start these components again. The license information is automatically inserted into the external database (it is automatically read from a local file reflecting the most recently loaded Solution Manager license).
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.