Supported deployment configurations - bluesoft-rnd/aperte-workflow-core GitHub Wiki
Aperte Workflow is based on well-tested and portable Open Source technologies (Hibernate, Liferay, jBPM, Vaadin, etc.). Therefore, it is easy to make it run on any deployment configuration supported by these technologies.
Even if your favorite database engine or application server isn't listed below, there is still a good chance that Aperte Workflow will run on it!
If you would like to see another technology supported by Aperte Workflow - [https://github.com/bluesoft-rnd/aperte-workflow-core/issues](let us know!).
RDBMS
Aperte Workflow is regularly tested against database engines listed below. Please take note, that there may be some 3rd party plugins that may require seperate tests (e.g. because of too long column names or use of restricted keywords in identifiers - for example on MySQL, column cannot be named key).
| Database | Status | Notes |
|---|---|---|
| HSQL | OK | The same version as Liferay Portal 6.0.6 CE uses |
| PostgreSQL 8 | OK | From 3.0 version min 8.4 version is required JDBC drivers update is necessary |
| PostgreSQL 9 | OK | Requires JDBC driver update for Activiti - unless you are using Liferay 6.1 |
| MySQL 5.1 | OK | |
| Oracle 10g | OK* | *due to a bug in jBPMv4 configuration, you have to change the type of column name_ in table jbpm4_lob to varchar2 |
| Oracle 10g Express Edition | OK* | *due to a bug in jBPMv4 configuration, you have to change the type of column name_ in table jbpm4_lob to varchar2 |
Servlet Containers/Application Servers
Aperte Workflow currently supports only [http://www.liferay.com](Liferay Portal) deployments. Therefore, it should run on any Servlet Container/Application Server listed on [http://www.liferay.com/products/liferay-portal/tech-specs](Liferay Deployment Compatibility) page.
The list below consists servlet containers/application servers that Aperte Workflow is regularly tested against.
| Container | Status | Notes |
|---|---|---|
| Tomcat 6 | OK | |
| Tomcat 7 | OK | |
| Jetty 6.1.24 | needs testing | |
| JBoss AS 5.1 | OK | To run Aperte Modeler in JBoss, you may need to unpack apertemodeler.war file |
| JBoss AS 6.0 | needs testing | |
| JBoss AS 7.1 | needs testing | |
| WebSphere Application Server 7 | OK* | *support for IBM WebSphere AS is not yet available in Open Source version |
| Oracle WebLogic | needs testing | |
| GlassFish | needs testing* | *it is well-known, that fate of GlassFish is at least uncertain |
Portlet Containers
Aperte Workflow is made to run on Liferay Portal (mostly due to Liferay's awesomeness). Liferay gives us a lot of out-of-the-box features and standards and let's users build their intranets around Aperte Workflow deployment.
| Portlet Container | Status | Notes |
|---|---|---|
| Liferay 6.0.6 CE | OK | |
| Liferay 6.0.5 CE | OK | |
| Liferay 6.1 CE | OK | tested on Tomcat version |
| Liferay 6.0.12 EE | OK | tested on Tomcat version |
| Liferay 6.1 EE | POC | Our users has proven that it is possible |
BPM engines
Aperte Workflow and Modeler have been designed to work with many diverse BPM engines. As Aperte Modeler supports BPMN2.0 design even for processes to be run on jBPMv4, you may decide upon BPM technology on stability and maturity basis.
| BPM Engine | Status | Notes |
|---|---|---|
| jBPM4.4 | OK | (From 3.0 beta is not supported) |
| jBPM5.4 | OK | From 3.0 beta version. |
| Activiti | OK | From 1.1 to 2.0 version (From 3.0 beta is not supported) |
Java Development Kits
Aperte Workflow depends mostly on Liferay's and Servlet Container/Application Server JDK compability. It has been tested and verified against:
- Recent version of Oracle JDK 7
- IBM JDK 1.6 - support for IBM JDK is not yet available in Open Source version