3. Automation Module

The Automation Module comprises the control logic on a dedicated batch server (the “RED server”), which interacts with the RED database repository. This module is an integral part of the core logic and a mandatory prerequisite for every other module.

The RED-PSS Guide describes the processes on the RED server.

3.1. Scheduling

Since the Exasol database comes without a scheduling mechanism, the RED framework adds all these features. There is no need for an external scheduler.

3.2. Monitoring

See Monitoring.

3.3. Deployment

The RED framework tracks two types of versions:

Technical Version (TV)

The version of the RED framework itself. See the RED TV Deployment Guide.

Business Version (BV)

The version of the metadata, i.e. of loaders, tables, application marts, etc. See the RED BV Deployment Guide.

The version history (TV and BV) can be seen in the view REDSYS.ADM_VERSION_HISTORY.

A business version must be opened before the Application Manager can make any change. When a BV is to be propagated to a higher environment (test or production), the BV must be closed and all changes should be committed to a version control system such as Git.

3.3.1. Transaction Brackets

Changes made by API calls are usually committed as soon as the call has finished successfully. If you run a script with multiple calls in sequence (as happens during a deployment), each change is committed immediately. If something goes wrong, the previous changes cannot be rolled back.

Transaction brackets guarantee an atomic transaction over all single API calls: an error occurring in the middle of the deployment triggers a rollback of the complete deployment.

Important

Only users with a private sandbox can use transaction brackets.

Example: Transaction Bracket

1EXECUTE SCRIPT API_REDSYS.TRX_BEGIN();
2
3-- all API calls of the deployment
4
5EXECUTE SCRIPT API_REDSYS.TRX_COMMIT();

TRX_BEGIN starts the bracket. Note that it commits any pending work of the current session first.

Within the bracket the API calls are only recorded. They are executed at TRX_COMMIT in their original order within a single database transaction, which is why TRX_COMMIT may take some time.

TRX_ABORT discards all recorded calls without executing them. Use it as well to close the bracket if TRX_COMMIT ended with an error.

Note

API calls via the REST API cannot be enclosed in transaction brackets.