License Warning on Startup
If you start Datical DB and a license is not installed, a warning is shown.
Click OK to dismiss the warning. You can proceed to work in the GUI, but you cannot connect to databases until you install a license.
Installing a License from the GUI
- Obtain a license file from Datical Support and place it on the system where you are running an instance of Datical DB.
- Start Datical DB. Dismiss the license warning (click OK).
- In the GUI, choose File > License Manager.
- Select the type of license to install, then click Next.
- Choose (Re)Install a license key, the click Next.
- Use the browser to choose the license file.
- Click Install License Key.
- Click Finish.
Displaying a License Key in the GUI
You can display the license key installation date and expiration date, as well as details about the license.
- Start Datical DB.
- In the GUI, choose File > License Manager.
- Select the type of license to display, then click Next.
- Choose Display the installed license key, the click Next.
- Review the license information. Click Finish when done.
Installing License using the Command Line (CLI)
If you have the repl subdirectory of your Datical installation on your path, you can run these hammer commands from any directory. Or if you don't have it in your path, then you need to be in your "<Datical Installation>/repl" directory to run these commands from the command line:
Just before installing your new license, you can run an uninstall command to uninstall all older licenses:
hammer uninstallLicense
The uninstall command will uninstall all of your Liquibase Enterprise/Datical DB licenses.
Then copy the new license file to the location where you keep your license files.
Run the following command to install your new license:
hammer installLicense <path_to_license_file>
For example:
hammer installLicense /opt/datical/license/<CompanyName>-<ExpirationDate>.lic
To check what license is currently installed run the following command:
hammer show license
Counting Licensed Objects
Datical DB is licensed by the number of DbDefs managed in a database object. The object licensed depends on the type of database.
- Oracle - per instance
- SQL Server - per database
- EDB Postgres - per database
- DB2 LUW - per database
License counting is a routine part of verifying the number of database connections (DbDefs) that you are managing, compared to the number that you are licensed to manage.
The license counter reports on the projects that are installed on a host by inspecting the project files.
When you run the license counter, specify a starting directory. It walks the file system from that point down and reports on all project files that are found in the hierarchy.
To count licenses, do the following:
- Log on to a host where you have created Datical DB projects.
Run the license counter. The output goes to
stdout, so provide a redirection to a file.Linux: hammer licenseCounter ~/datical > DaticalLicenseCount.txt Windows: hammer.bat licenseCounter C:\Datical\Projects > DaticalLicenseCount.txt
Inspect the license file to determine the number of licenses in use on the host. The following example shows the format of the report.
DB2: jdbc:db2://192.168.156.21:50000/int_db jdbc:db2://ec2-35-175-43-211.compute-1.amazonaws.com:50000/REFDB Total Unique DB2 Databases: 2 Oracle: jdbc:oracle:thin:@localhost:1523/orclsid jdbc:oracle:thin:@192.168.156.21:1521/orcl jdbc:oracle:thin:@localhost:1521/orcl.shusak.com jdbc:oracle:thin:@localhost:1523:orclsid jdbc:oracle:thin:@localhost:1521:orcl jdbc:oracle:thin:@localhost:1521/orcl Total Unique Oracle Databases: 6 MSSQL: jdbc:sqlserver://localhost\MSSQLEXPRESS:1433;databaseName=AdventureWorks2014 jdbc:sqlserver://localhost\SQLEXPRESS:49818;databaseName=mydb2 jdbc:sqlserver://localhost\SQLEXPRESS:49818;databaseName=mydb Total Unique MSSQL Instances: 2 Total Unique MSSQL Databases: 3 Total Instances Managed: 10 Total Databases Managed: 11