This page contains important announcements from Camunda’s Enterprise Support. In the following section we list information about changes to the supported environments and scheduled end of maintenance dates for specific versions of the Camunda BPM platform. The announced end of maintenance dates are based on our standard support period of 18 months.

Camunda BPM Announcements

Camunda BPM 7.12

Release Date: scheduled for 30th of November 2019

End of Maintenance: 31st of May 2021

Changes in Supported Environments:

• Support for Java 13
• Support for Wildfly Application Server 17 / 18
• End of Support for Java 7
• End of Support for JBoss Application Server 7
• End of Support for JBoss EAP 6.1 / 6.2 / 6.3
• End of Support for Wildfly Application Server 8.2
• End of Support for Oracle 10
• End of Support for PostgreSQL 9.1 / 9.3
• End of Support for DB2 9.7 / 10.1
• End of Support for Microsoft SQL Server 2008

Camunda BPM 7.11

Release Date: 31st of May 2019

End of Maintenance: 30th of November 2020

Changes in Supported Environments:

• Support for Java 12
• Support for Postgres 10.7, 11.1 and 11.2
• Support for Amazon Aurora PostgreSQL compatible with PostgreSQL 9.6 / 10.4 / 10.7
• Support for Oracle 18c
• Support for Microsoft SQL Server 2017
• Support for JBoss EAP 7.2
• Support for Wildfly Application Server 15 / 16

Camunda BPM 7.10

Release Date: 30th of November 2018

End of Maintenance: 31st of May 2020

Changes in Supported Environments:

• Support for the latest Version of the Wildfly Application Server
• Support for Java Version > 8
• Support for Database PostgreSQL 10.4
• Support for Database MariaDB 10.3
• End of Support for Application Server IBM WebSphere 8.0
• End of Support for Java 6

Camunda BPM 7.9

Release Date: 31st of May 2018

End of Maintenance: 30th of November 2019

Changes in Supported Environments:

• Support for Application Server Tomcat 9
• Support for Application Server Wildfly 11
• Support for Application JBoss EAP 7.1
• Support for Database MariaDB 10.2
• Support for Spring Boot 2.0

Camunda BPM 7.8

Release Date: 30th of November 2017

End of Maintenance: 31st of May 2019

Changes in Supported Environments:

• Support for Database Microsoft SQL Server 2016
• Support for Microsoft Edge
• End of Support for Internet Explorer 9 and 10

Camunda BPM 7.7

Release Date: 31st of May 2017

End of Maintenance: 30th of November 2018

Changes in Supported Environments:

• Support for Application Server IBM WebSphere 9.0
• Support for Database IBM DB2 11.1
• Support for Database PostgreSQL 9.6

Camunda BPM 7.6

Release Date: 25th of November 2016

End of Maintenance: 31st of May 2018

Changes in Supported Environments:

• Support for Application Server JBoss EAP 7.0
• Support for Database MariaDB Galera Cluster

Camunda BPM 7.5

Release Date: 31st of May 2016

End of Maintenance: 30th of November 2017

Changes in Supported Environments:

• Support for Application Server Wildfly 10.0
• End of Support for Application Server WildFly 8.1
• End of Support for Application Server GlassFish 3.1
• End of Support for Database MySQL 5.1 / 5.5
• End of Support for Java Runtime Vendor OpenJDK 6

Camunda BPM 7.4

Release Date: 30th of November 2015

End of Maintenance: 31st of May 2017

Changes in Supported Environments:

• Support for Application Server Apache Tomcat 8
• Support for Application Server Oracle WebLogic Server 12c (12R1,12R2)

Camunda BPM 7.3

Release Date: 28th of May 2015

End of Maintenance: 30th of November 2016

Changes in Supported Environments:

• Support for Application Server Wildfly 8.1 / 8.2
• Support for Database MariaDB 10.0
• Support for Database MySQL 5.5 / 5.6
• Support for Database Oracle 12c
• Support for Database IBM DB2 10.1 / 10.5
• Support for Database PostgreSQL 9.4
• Support for Database Microsoft SQL Server 2014
• Support for Runtime Environment OpenJDK 6 / 7
• Support for Runtime Environment IBM® J9 virtual machine (JVM) 8
• Support for Runtime Environment Sun / Oracle Hot Spot 8

Camunda BPM 7.2

Release Date: 28th of November 2014

End of Maintenance: 31st of May 2016

Changes in Supported Environments:

• Support for Application Server JBoss EAP 6.3 / 6.4
• Support for Database PostgreSQL 9.3
• Support for Runtime Environemt Java 8 (if supported by your application server / container)

Product Change: With Camunda BPM 7.2.0, Camunda BPM Cycle is no longer bundled in the distribution of our platform. We provide Camunda BPM Cycle in an own distribution. Since the separation, Camunda BPM Cycle is only provided and supported for the Apache Tomcat application server. You can download Cycle here.

Camunda Optimize Announcements

Camunda Optimize 2.7

Release Date: scheduled for 20th of December 2019

End of Maintenance: 30th of June 2021

Changes in Supported Environments:

• Minimum required Elasticsearch version is raised to 6.4.0
• End of Support for Elasticsearch 6.2.X, 6.3.X releases

Camunda Optimize 2.6

Release Date: 2nd of October 2019

End of Maintenance: 31st of March 2021

Changes in Supported Environments:

Camunda Optimize 2.5

Release Date: 28th of June 2019

End of Maintenance: 31st of December 2020

Changes in Supported Environments:

• Support for Elasticsearch 6.6.0+, 6.7.0+, 6.8.0+
• Support for Java 12

Camunda Optimize 2.4

Release Date: 29th of March 2019

End of Maintenance: 30th of September 2020

Changes in Supported Environments:

• Support for Elasticsearch 6.2.0+, 6.3.1+, 6.4.0+, 6.5.0+
• End of Support for Elasticsearch 6.0.0

What does End of Maintenance Mean?

End of maintenance means that Camunda will not perform any maintenance or release any bug fixes and patch releases related to the mentioned version after the specified date. In case you are planning to migrate to a more recent version of Camunda BPM, check our Update & Migration Guide.

Please let us know if you have any concerns or if you need help migrating to a new version.

Why is Camunda Changing the Support for Environments?

Camunda is committed to delivering improvements and bug fixes as fast as possible. We are also committed to providing world class support for our software running in different environments. However, as new versions of databases, web browsers, etc, are released, the cost of supporting multiple environments grows exponentially, making it harder to provide the level of support our customers have come to expect from us. Therefore, we no longer support environments marked as end-of-life by the vendor, or very old versions that are no longer widely used.