user/schema "jbpm" with password "jbpm" (which will be used to persist all entities)

jbpm-installer/db/jbpm-persistence-JPA2.xml

Application server configuration

Disable H2 default database and enable MySQL database in build.properties

# default is H2
# H2.version=1.3.168
# db.name=h2
# db.driver.jar.name=${db.name}.jar
# db.driver.download.url=http://repo1.maven.org/maven2/com/h2database/h2/${H2.version}/h2-${H2.version}.jar
#mysql
db.name=mysql
db.driver.module.prefix=com/mysql
db.driver.jar.name=mysql-connector-java-5.1.18.jar
db.driver.download.url=https://repository.jboss.org/nexus/service/local/repositories/central/content/mysql/mysql-connector-java/5.1.18/mysql-connector-java-5.1.18.jar
        

You might want to update the db driver jar name and download url to whatever version of the jar matches your installation.

db/jbpm-persistence-JPA2.xml:

This is the JPA persistence file that defines the persistence settings used by jBPM for both the process engine information, the logging/BAM information and task service.

In this file, you will have to change the name of the hibernate dialect used for your database.

The original line is:

<property name="hibernate.dialect" value="org.hibernate.dialect.H2Dialect"/>

In the case of a MySQL database, you need to change it to:

<property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>

For those of you who decided to use another database, a list of the available hibernate dialect classes can be found here.

standalone-full-wildfly-8.1.0.Final.xml:

Standalone.xml and standalone-full.xml are the configuration for the standalone JBoss application server. When the installer installs the demo, it copies these files to the standalone/configuration directory in the JBoss server directory. Since the installer uses Wildfly8 by default as application server, you probably need to change standalone-full-wildfly-8.1.0.Final.xml.

We need to change the datasource configuration in standalone-full.xml so that the jBPM process engine can use our MySQL database. The original file contains (something very similar to) the following lines:

<datasource jta="true" jndi-name="java:jboss/datasources/jbpmDS" pool-name="H2DS" enabled="true" use-java-context="true" use-ccm="true">
    <connection-url>jdbc:h2:tcp://localhost/~/jbpm-db;MVCC=TRUE</connection-url>
    <driver>h2</driver>
    <security>
       <user-name>sa</user-name>
    </security>
</datasource>
<drivers>
    <driver name="h2" module="com.h2database.h2">
        <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
    </driver>
</drivers>

Change the lines to the following:

<datasource jta="true" jndi-name="java:jboss/datasources/jbpmDS" pool-name="MySQLDS" enabled="true" use-java-context="true" use-ccm="true">
    <connection-url>jdbc:mysql://localhost:3306/jbpm</connection-url>
    <driver>mysql</driver>
    <security>
       <user-name>jbpm</user-name>
       <password>jbpm</password>
    </security>
</datasource>

and add an additional driver configuration:

<driver name="mysql" module="com.mysql">
    <xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>
</driver>

To install driver jars in JBoss application server (Wildfly8, EAP6, etc.), it is recommended to install the driver jar as a module. The installer already takes care of this mostly: it will copy the driver jar (you specified in the build.properties) to the right folder inside the modules directory of your server and put a matching module.xml next to it. For MySQL, this file is called db/mysql_module.xml. Open this file and make sure that the file name of the driver jar listed there is identical the driver jar name you specified in the build.properties (including the version). Note that, even if you simply uncommented the default MySQL configuration, you will still need to add the right version here.

Starting the demo

We've modified all the necessary files at this point. Now would be a good time to make sure your database is started up as well!

The installer script copies this file into the jbpm-console WAR before the WAR is installed on the server. If you have already run the installer, it is recommended to stop the installer and clean it first using

ant stop.demo

and

ant clean.demo

before continuing.

Run

ant install.demo

to (re)install the wars and copy the necessary configuration files. Once you've done that, (re)start the demo using

ant start.demo

Problems?

If this isn't working for you, please try the following:

Configuring the jBPM datasource in standalone.xml:

You need to change the dialect in persistence.xml to the dialect for your database, for example:

<property name="hibernate.dialect" value="org.hibernate.dialect.PostgreSQLDialect"/>

In order to make sure your driver will be correctly installed in the JBoss application server, there are typically multiple options, like install as a module or as a deployment. It is recommended to install the driver as a module for AS7, EAP6 and Wildfly8. For example, for AS7 both ways are explained here.

If you choose to install driver as JBoss module (recommended), please do the following: