Database

The following databases are officially supported and tested with Flowable Engage:

Flowable Engage uses a standard JDBC connection and database interfaces so other database implementations may also work but they are not officially supported or tested by Flowable.

The database schema is created by the Flowable Engage on its initial startup via Liquibase. If Liquibase finds an empty database schema it initializes the database by creating all the needed tables, sequences, etc. For this process to work, the application needs schema editing permissions on the database.

The following table shows the recommended virtual memory (VM) specifications per node type of the database servers when files are persisted on a separated file store:

It is also possible to store documents and attachments directly in the database. This approach is NOT RECOMMENDED as it heavily affects performance and maintainability of the overall system.

If files are persisted as BLOBs in the database, the following specifications are applicable: