...
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 Liquibase/Datical Before Starting | |||||
You need to set up accounts on Datical web sites | Get access to these sitesthis site:
| ||||
Database clients |
| ||||
Installation Resources | |||||
Datical provides the following resources for installation. | All SoftwareThe Liquibase/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.
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.
|
...