db/persistence.xml:

This is the JPA persistence file that defines the persistence settings used by jBPM for both the process engine information and the logging/BAM information. The installer ant script moves this file to the expanded gwt console server war before the server is started.

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.

task-service/resources/META-INF/persistence.xml:

The task service (that the installer starts) uses the JPA Persistence settings described in this file.

The original file contains the following lines:

    <properties>
      <property name="hibernate.dialect" value="org.hibernate.dialect.H2Dialect"/>
      <property name="hibernate.connection.driver_class" value="org.h2.Driver"/>
      <property name="hibernate.connection.url" value="jdbc:h2:tcp://localhost/runtime/task" />
      <property name="hibernate.connection.username" value="sa"/>
      <property name="hibernate.connection.password" value="sasa"/>

Please change these lines so that they look like this:

    <properties>
      <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
      <property name="hibernate.connection.driver_class" value="com.mysql.jdbc.Driver"/>
      <property name="hibernate.connection.url" value="jdbc:mysql://localhost:3306/task" />
      <property name="hibernate.connection.username" value="task"/>
      <property name="hibernate.connection.password" value="task"/>

db/jBPM-ds.xml:

This step is only neccessary if you're using JBoss AS 5.

This file is the configuration for the (JTA) datasource used by the jBoss AS 5 instance for the process engine persistence. The installer ant script moves this file to the jboss server deploy directory.

The original file contains the following lines:

<datasources>
  <local-tx-datasource>
    <jndi-name>jboss/datasources/jbpmDS</jndi-name>
    <connection-url>jdbc:h2:tcp://localhost/runtime/jbpm-demo</connection-url>
    <driver-class>org.h2.jdbcx.JdbcDataSource</driver-class>
    <user-name>sa</user-name>
    <password></password>
  </local-tx-datasource>
</datasources>

Please change these to the following:

<datasources>
  <local-tx-datasource>
    <jndi-name>jboss/datasources/jbpmDS</jndi-name>
    <connection-url>jdbc:mysql://localhost:3306/jbpm5</connection-url>
    <driver-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</driver-class>
    <user-name>jbpm5</user-name>
    <password>jbpm5</password>
  </local-tx-datasource>
</datasources>

standalone.xml:

This step is only neccessary if you're using AS 7.

This file is the configuration for the standalone JBoss AS 7 server. When the installer starts the demo (using jBoss AS 7), it moves this file to the standalone/configuration directory in the jboss server directory

We need to change the datasource configuration in standalone.xml so that the (JTA) datasource for the jBPM process engine and logging/BAM points to our MySQL database

The original file contains the following lines:

        <subsystem xmlns="urn:jboss:domain:datasources:1.0">
            <datasources>
                <datasource jndi-name="java:jboss/datasources/jbpmDS" enabled="true" use-java-context="true" pool-name="H2DS">
                    <connection-url>jdbc:h2:tcp://localhost/runtime/jbpm-demo</connection-url>
                    <driver>h2</driver>
                    <pool></pool>
                    <security>
                       <user-name>sa</user-name>
                       <password></password>
                    </security>
                </datasource>
                <drivers>
                    <driver name="h2" module="com.h2database.h2">
                        <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
                    </driver>
                </drivers>
            </datasources>
        </subsystem>

Change the lines to the following:

        <subsystem xmlns="urn:jboss:domain:datasources:1.0">
            <datasources>
                <datasource jndi-name="java:jboss/datasources/jbpmDS" pool-name="H2DS" enabled="true" use-java-context="true">
                    <connection-url>jdbc:mysql://localhost:3306/jbpm5</connection-url>
                    <driver>mysql</driver>
                    <pool></pool>
                    <security>
                       <user-name>jbpm5</user-name>
                       <password>jbpm5</password>
                    </security>
                </datasource>
                <drivers>
                    <driver name="mysql" module="com.mysql">
                        <xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>
                    </driver>
                </drivers>
            </datasources>
        </subsystem>

Start the demo

We've modified all the neccessary files at this point, all that's left to do is run the demo.

Of course, this would be a good time to start your database up as well!

If you haven't installed the demo yet, do that first:

ant install.demo.db

If you have already installed and run the demo, it can't hurt to reinstall the demo:

ant clean.demo; ant install.demo.db

After you've done that, you can finally start the demo using the following command:

ant start.demo.db

If you're done with the demo, you can stop it using this command:

ant stop.demo.db

The stop.demo ant task will also work, although it might throw some exceptions.

Problems?

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