3. Automation Module

The automation module includes control logic located on an external batch server (“RED-server”) interacting with the RED database repository. This module is an integral part of the core logic and mandatory prerequisite for every other module.

RED-PSS guide describes the process part 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 vtypes of versions:

  • the technical version (TV): This is the version of the RED framework itself.

  • the business version (BV): This is the version of the metadata, i.e. the version of loaders, tables, application marts, tec.

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

A business version must be opened before the application manager can do any change. When a BV should be propagated to a higher environment (test or production), the BV must be closed and all changes should be put to some source code versioning system like GIT.

3.3.1. Transaction Brackets

Changes within API calls usually are committed as soon as the call is finished successfully. If you run a script with multiple calls in sequence (as it happens during a deployment) each change would be committed immediately. If something goes wrong the previous changes cannot be rolled back. Transaction brackets guarantee an atomic transaction over all singe API calls hich means that 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.

Start a transaction by issuing the following command:

1EXECUTE SCRIPT API_REDSYS.TRX_BEGIN();

The exceute all your API calls and in the end terminate the transaction by calling:

1EXECUTE SCRIPT API_REDSYS.TRX_COMMIT();

Note

TRX_COMMIT may take some time because only at this point in time the changes are applied physically within a single database transaction.