Supported Environments

Run ASEE Flow in every Java-runnable environment. ASEE Flow is supported with our QA infrastructure in the following environments.

​

Container/Application Server for Runtime Components

​

Application-Embedded Process Engine

• All Java application servers
• ASEE Flow Spring Boot Starter: Embedded Tomcat
  • Supported versions
  • Deployment scenarios
• ASEE Flow Engine Quarkus Extension
  • Supported versions
  • Deployment scenarios

​

Container-Managed Process Engine and ASEE Flow Cockpit, Tasklist, Admin

• Apache Tomcat 10.1 (the Tomcat distribution ships 10.1.60)
• WildFly Application Server 39 (the WildFly distribution ships 39.0.1)

The javax variants — the WildFly 26 modules and subsystem, the javax web application, and Spring 5.3 (engine-spring) — are still built, for users coming from javax servers, but receive no security fixes. They are removed in ASEE Flow 2.0.

​

Databases

​

Supported Database Products

• MySQL 8.0
• Oracle 19c / 23ai
• IBM DB2 11.5 (excluding IBM z/OS for all versions)
• PostgreSQL 14 / 15 / 16 / 17
• Amazon Aurora PostgreSQL compatible with PostgreSQL 14 / 15 / 16
• Microsoft SQL Server 2017 / 2019 / 2022 (see Configuration Note)
• Microsoft Azure SQL with ASEE Flow-supported SQL Server compatibility levels (see Configuration Note):
  • SQL Server on Azure Virtual Machines
  • Azure SQL Managed Instance
  • Azure SQL Database
• H2 2.3 (not recommended for Cluster Mode - see Deployment Note)

​

Database Clustering & Replication

Clustered or replicated databases are supported given the following conditions. The communication between ASEE Flow and the database cluster has to match with the corresponding non-clustered / non-replicated configuration. It is especially important that the configuration of the database cluster guarantees the equivalent behavior of READ-COMMITTED isolation level.

​

Web Browser

• Google Chrome latest
• Mozilla Firefox latest
• Microsoft Edge latest

​

Java

• Java 17 / 21 (Compatibility is tested with Eclipse Temurin JDK)

The engine JARs are compiled for Java 11, so the engine can be embedded in a Java 11 application, but Java 11 is not tested. Java versions after 21 are not supported on the 1.x line: on Java 25 the bundled JavaScript engine (GraalJS 21.3) fails as soon as it is used — for example when the invoice example deploys, which stops ASEE Flow Run’s default configuration from starting.

​

Camunda Modeler

Supported environments for Camunda Flow Modeler have moved to docs.camunda.io.

​

Adding Environments

Whenever a new version of one of the following environments is released, we target support of that new version with the next minor release of ASEE Flow. A new released environment has to be available three months before the next ASEE Flow minor release to be considered.

• Java Language (LTS)
• Spring Boot
• Wildfly Application Server
• Oracle Database (LTS)
• PostgreSQL

The exact release in which we support a new environment depends on factors such as the release date of the environment and the required implementation effort. Version support for other environments is decided case by case, much of which is based on the demand in our user base.

​

Removing Environments

Whenever a new version of one of the following environments is supported, we usually discontinue support of the oldest version with the same release:

• Wildfly Application Server

Note that we may decide to deviate from this policy on a case-by-case basis.