2. RED BV Deployment Guide¶

This document describes the deployment, installation, and lifecycle processes for the Business Version (BV) of the RED framework on target host environments.

While the Technical Version (TV) represents the RED framework infrastructure, the Business Version encapsulates tenant-specific or project-specific business logic. This includes custom data transformations, localised schema changes, client-specific reporting schemas, and business rules.

2.1. The Business Version Lifecycle¶

The Business Version lifecycle transitions logic from a development environment into version control, and subsequently into target test or production environments. This process relies on the redbvctl (Business Version Control) utility.

2.1.1. 1. Development and Export¶

Developers build and test their business logic directly in a development Exasol database. Once ready, they use redbvctl to serialise this logic to the local filesystem.

redbvctl export

The tool queries the database metadata to extract the Business Layer schema structures and generates the DDL files within the local src/bv/ directory.

Note

Targeted Exports: You can restrict exports to specific schemas or objects using the -s <schema> and -o <object> flags.

2.1.2. 2. Version Control¶

A critical principle of the RED framework is that the database state must always reflect source control. The generated src/bv directory must be committed to a Version Control System (VCS), such as Git, to track changes and enable deployments.

2.1.3. 3. Target Environment Deployment¶

To deploy the Business Version to another environment (such as TEST or PROD), the target environment pulls the latest src/bv code from the version control system. The codebase is then installed into the target database.

# Switch into your environment context first
<env_name>

# Install the Business Version
redbvctl install -u <db_user> -p <db_password> -v <version>

2.2. Environment Restrictions and Security¶

Unlike technical framework installations (which often run with highly privileged SYS access), Business Version deployments are restricted by design:

Principle of Least Privilege: During install, the script requires a standard application database username (-u), preventing the Business Version from making unauthorised structural changes outside its scope.
Environment Instance Checks: The redbvctl utility performs strict checks to detect its runtime environment context before executing.