Liquibase Business was formerly known as Datical DB.
Installation Scenarios | |
Where are you in your adoption of Liquibase Business? | Evaluation: Evaluation of Liquibase Business on the way to automation |
Installation for a User - install on a system (typically Windows) that an individual will use to define release pipelines and move database changes through them. Typically used in contexts where some of the following conditions are true:
| |
Automation System: Testing and usage of Liquibase Business in an automation environment | |
Installation for an Automation System - install on a system (typically Linux). An automation system (Jenkins or other) runs scripts to perform operations. Typically used in contexts where some of the following conditions are true:
| |
Expansion: Large-scale expansion of Liquibase Business Usage | |
Automated Installation of Liquibase Business - Use an automation system to install Liquibase Business on many systems (either user installations or automation installations). Delivers Liquibase Business for either or both:
| |
What You Need from Datical Before Starting | |
You need to set up accounts on Datical web sites | Get access to these sites:
|
Database clients |
See the client page for your database platform: |
Installation Resources | |
Datical provides the following resources for installation. | All SoftwareThe Datical Electronic Software Distribution site (software.datical.com) contains installation files and PDF documentation files for each release.
RepositoriesRepositories are used to install or update Liquibase Business.
|
What You Install | |
Liquibase Business Components |
|
What Directories are Created on a System | |
| Installation Directory - DaticalDB |
This directory contains all executables and support files.
Location: You can choose the installation directory during installation. The default locations are the following directories:
| |
Project Workspace directory - datical | |
The project workspace contains files for each project you create in Liquibase Business. Note The workspace directory is not removed or changed when you upgrade or re-install Liquibase Business When you create a project, the project definition is stored in the workspace. As you perform operations on the project (package, forecast, deploy, rollback), files in the workspace are created, updated, moved, and removed. Location: This is a fixed location.
|
Sample Installation Steps
The actual steps vary depending on your choice of system, installation tool (GUI or CLI), and installation repository (Update Site repository or Composite Repository).
These samples give you a quick overview of the steps involved in the sample cases.
Use Case: Individual User
Windows is the most common platform for individual users.
The following scenario is for a user system that has access to the internet (Update Site Repository)
- Download the Liquibase Business installer for Windows (.exe)
- Run the GUI installation to install the clients (GUI and CLI)
- Start the GUI.
- Configure the GUI to add Update Site repositories
- Install the JDBC drivers
- Install the SCM plugins (optional)
Use Case: Automation System
Linux is the most common platform for use by automation systems. Typically hosts that are part of automated processes do not have access to the internet.
- From a host that has access to the internet, download the Liquibase Business composite repository, which contains installation files for the Liquibase Business clients and JDBC drivers.
- Move the composite repository to the host where you want Liquibase Business to run.
- Run the installation from the command line.
- Test the installation using the CLI
- Create scripts for the automation system that call Liquibase Business commands
Sample Installation Steps for Automated Installation of Liquibase Business
- Package Liquibase Business installation resources into an artifact.
- Deliver the artifacts to target systems.
- Extract the installation resources from the artifact.
- Run scripts to install Liquibase Business on each target system.
Alternative Installations
Instructions are provided for alternative types of installation. They are typically when installing for an automation system.
- Headless Linux (must use the CLI to install) - see Accessing Remote Linux Systems
- Shared Linux Installation (multiple users or automations can use the same installation) - see Installation on a Shared Workspace on Linux
Administering the Installation
If your site requires it, you may also need to refer to Administering the Installation for additional information on several topics, including the following:
- Configure Liquibase Business to use a specific version of Java - see Java Version Use
- Configure Liquibase Business to use a proxy server to access the internet (necessary to download drivers and plug-ins) - see Use a Proxy Server with Datical DB
- Attend to IT security requirements - see Security and Liquibase Business Components