8.1. Integration Configuration
The jbpm5.esb deployment that ships with the JBoss ESB includes the jBPM 5 runtime, a datasource, a hibernate configuration and a JPA persistence configuration. The datasource is configured to use H2 as a backend database by default and is used to persist session and process information.
In production you will want change from H2 to a production strength database. All jbpm5.esb deployments should share the same database instance so that the various JBoss ESB nodes have access to the same processes definitions and instances.
The jBPM GWT console is a web application. It is not included, but it can be optionally downloaded from the customer portal and installed through the jBPM installer. Use the jbpm-5.2.0.Final installer as this is the version that has been tested against the JBoss ESB. You may need to make minor changes to the configuration of the JBPM GWT console, including changing the "context-root" in WEB-INF/jboss-web.xml from 'jbpm-console' to 'jbpm5-console' so that it does not conflict with the jbpm 3 version console which ships by default in the ESB.
Check the jBPM documentation to change the security settings for this application. This requires you to change some settings in the conf/login-config.xml. The console can be used for deploying and monitoring jBPM processes, but it can also be used for human task management. For different users, a customized task list will be shown and they can administer those tasks.
The jbpm5.esb/META-INF directory contains the deployment.xml and the jboss-esb.xml. The deployment.xml specifies the resources this esb archive depends on.