As Activiti is , it can be embedded in any Java environment: with swing or on a Tomcat, JBoss, Web Sphere, etc.Or you could very well choose to run Activiti as a typical, standalone BPM server.
As said in the one minute demo setup, the Activiti Explorer runs an in-memory H2 database by default.However, if the user guide mentions those classes as configuration values, they are supported and can be considered stable.After downloading the Activiti Explorer WAR file from the Activiti website, follow these steps to get the demo setup running with default settings.You’ll need a working Java runtime and Apache Tomcat installation (actually, any web container would work since we only rely on the servlet capability. Note that the Activiti Explorer demo setup is a way of showing the capabilities and functionality of Activiti as easily and as fast as possible.This does however, not mean that it is the only way of using Activiti.To run the Activiti Explorer with a standalone H2 or another database the db.properties in the WEB-INF/classes of the Activiti Explorer web application should be changed.
In addition, be aware that the Activiti Explorer generates demo user and groups, process definitions and models by default.
To disable this, the engine.properties file in the WEB-INF/classes folder should be changed.
Activiti runs on a JDK higher than or equal to version 6.
Go to Oracle Java SE downloads and click on button "Download JDK".
There are installation instructions on that page as well.
To verify that your installation was successful, run in the package name are internal implementation classes and cannot be considered stable.