Hardware, Software and Database Requirements
Datical DB runs on the following platforms and software.
Hardware Requirements
- Processor: Intel® Core™ i5 or better, 4 CPUs or more.
- Memory: 4 GB - 8 GB or more. When working with large databases, 16 GB or more may be required due to high memory requirements during packaging.
- Disk Space: 1 GB (for Datical Client) + 2-10 GB (for files) or more
Software Requirements
Operating System
- Windows
- Windows 7, 8, 10
- Windows Server 2008, 2012, 2016, 2019, 2022
- Linux
- CentOS 6, 7, 8
- Red Hat Enterprise Linux (RHEL) 6, 7, 8, 9
- Note that CentOS 8 and RHEL 8 are only supported with Datical DB versions 7.16 or higher.
Software
- Java
- For Enterprise versions 8.0 and later:
- Java 11 is required
- OpenJDK Version 11.0.15_10 (Java 11) is installed and used by default
- For Enterprise versions 7.18 and lower:
- Java 8 is required
- You can configure Datical DB to use a specific version (within the major version requirement). See Overriding Java Use.
- For Enterprise versions 8.0 and later:
- JDBC drivers: set up during installation
- Source Configuration Management (SCM)
Internet Access
You normally need internet access from the hosts where you install Datical DB. If you access the internet through a proxy server you need to configure your browser and Datical DB to use it.
- Browser: See browser instructions to set it up to use a proxy server. Use a browser to download the Datical DB installation package.
- Datical DB: See Use a Proxy Server with Datical DB. After installation you use Datical DB to set up Datical DB updates, download JDBC drivers, and install plugins for Source Code Management (SCM).
If you do not have internet access from the hosts where you want to install Datical DB, you can download files to use for installation and updates. Move them to where those hosts have network access to it.
Database Requirements
The following databases are supported.
| Database | Versions | Notes |
|---|---|---|
| IBM DB2 | ||
| IBM DB2 LUW |
| Support for 11.5 was added in release 7.12 |
| DB2 z/OS |
| Support for 12.1.5 was added in the 8.2 release |
| Microsoft SQL Server | ||
| Microsoft SQL Server |
| JDBC driver supports TLS 1.0, 1.1, and 1.2 (Support for 2017 & 2019 was added in 7.9 release) (Support for 2012 was dropped in 8.5 release) (Support for 2022 was added in 8.5 release) |
| Azure SQL Database | Latest Compatibility Level
| As of the 7.9 Release |
| Azure SQL Managed Instance | Latest Compatibility Level | As of the 7.10 Release |
| Oracle | ||
| Oracle |
| |
| Oracle on Amazon RDS |
| Oracle on Amazon RDS has some different behaviors than on-prem Oracle. The permissions required for the Datical user are slightly different and the backup configuration is different. |
| Postgres | ||
| EDB Postgres Advanced Server |
| Support for 13 was added in the 8.2 release Support for 14 and 15 was added in the 8.5 release |
| PostgreSQL Community |
| Support for 12 & 13 was added in the 7.15 release Support for 15 was added in the 8.5 release |
| PostgreSQL on Amazon RDS |
| Support for 12 & 13 was added in the 7.17 release Support for 14 was added in the 8.2 release Support for 15 was added in the 8.5 release |
| PostgreSQL on Amazon Aurora |
| Support for 12 & 13 was added in 7.17 release Support for 14 and 15 was added in the 8.5 release |
| PostgreSQL on Azure Database (single server) |
| Support for 11 was added in the 8.2 release Note: Azure Database for PostgreSQL - Single Server is on the retirement path and is scheduled for retirement by March 28, 2025. Learn more here |
Database Setup
For a general overview of the schema or databases required for a release pipeline, see Overview of the Database Components Used by Liquibase Enterprise.
You typically need to create the following objects:
- REF database - Serves as the first step in any release pipeline. It is the CI deployment target when Datical DB packages SQL scripts and refactors them into changesets.
- Tracking database or schema - Tracks the changes deployed to each database in the pipeline. A tracking database or schema is needed for each database in the release pipeline.
- DMC Database - Records operations for Datical DB release pipelines. DMC (Deployment Monitoring Console) provides you a centralized location to view status and reports across Datical projects.
For instructions on setting up Datical DB to work with your database, see the section for your database type in Configuring Databases for Liquibase Enterprise Release Pipelines.
You typically need to do the following tasks:
- Install a database client.
- Create a DATICAL USER and DATICAL PACKAGING. Give them the required permissions. Datical DB operates as those users to deploy changes to the databases in the release pipeline.
SCM Requirements and Features
The Datical Project must have its own repository.
If the Datical Project is in a repository that contains other work, automatic commits run by Datical may commit other pending work.
SCM Solution | SCM Versions |
Git | 1.8.2-1.9.x, 2.x. Note: requires the Git command line client be installed and in the system path for all servers where Deploy Packager will run (example: git.exe). |
Git
Datical DB supports SSH, HTTP and HTTPS protocols with Git.
SCM Environment Variables (Git only)
Use environment variables to store credentials for the Deployment Packager to use when accessing Git and Subversion repositories.
Environment Variable | Description |
SQL_SCM_USER | User name and password for the repository that manages the SQL code for the Deployment Packager. |
DDB_SCM_USER | User name and password for the repository that manages the Datical project for the Deployment Packager. |
Environment Variable Usage & Deployment Packager Behavior
Deployment Packager is only available with Liquibase Enterprise product
- The environment variables must be set before you start the Deployment Packager.
- Specify both the username and password.
- Deployment Packager checks the environment variables before it attempts to connect to the SCM.
- If the SCM user and password variables are set, Deployment Packager uses them to connect.
- If the SCM user and password variables are NOT set, the Packager attempts to connect without using a username or password. This is the legacy connection method, which required that you use persistent external authentication methods before running Deployment Packager.
- If only one of the variables is set. the Deployment Packager halts and reports an error.