In the deploy directory of the downloads, you can find
jbpm-enterprise.ear. That J2EE 1.4 compliant
enterprise archive includes: jPDL libraries, jBPM configuration files, the
jBPM web console, and a couple of enterprise beans. In this package, jBPM
is configured for usage in an application server like JBoss. The asynchronous
messaging service is here bound to JMS and the scheduler service is bound to the
EJB Timer Service. So here in this .ear file, no JobExecutor
is started. The persistence service is configured to participate in the overall
JTA transaction.
Within the enterprise archive there are the following files:
jbpm-console.war
: the console web application, adapted
for J2EE integration
jbpm-enterprise.jar
: the supporting enterprise beans
lib/jbpm-configs.jar
: configuration files
lib/jbpm-identity.jar
: identity component classes
lib/jbpm-jpdl.jar
: standard jPDL classes
meta-inf/application.xml
: J2EE app descriptor
jbpm-enterprise.jar
contains the following EJB components:
CommandServiceBean
CommandListenerBean
JobListenerBean
TimerEntityBean
These beans are J2EE 1.4 / EJB 2.1 compliant, to allow them to be deployed on a
variety of application servers. Note however that jBPM only provides deployment descriptors
for JBoss Application Server. All beans are deployed with the transaction-attribute
Required. The source for the EJB classes and interfaces is in
src/enterprise
and the javadocs in doc/javadoc-enterprise
.
A detailed description can be found in the section called “Enterprise Beans”.
jbpm-configs.jar
contains the following files:
jbpm.cfg.xml
: the jBPM configurationhibernate.cfg.xml
: the Hibernate configurationjbpm.mail.templates.xml
: the e-mail templatesSections the section called “jBPM Enterprise Configuration” and the section called “Hibernate Enterprise Configuration” examine the enterprise-specific settings in the first two files. The last file is described in the section called “Mail templates”.