11-2. Installing jBPM
You want to build a jBPM solution and need to know the simplest way to get the jars. There are many
supported workflows for jBPM, so it isn't clear where to begin for what role. For a business analyst, the
path is different than for a programmer, whose task it will be to employ jBPM, not deploy it. You will
need a few libraries first.
You can use jBPM as an API, rather than as a server or service. This integration is the most natural
to a developer, but not, for example, to a business user. We'll use Maven to get the dependencies.
While we'll focus on embedding jBPM in this chapter, it's useful to see the other ways you can
integrate jBPM into your architecture.
A developer may embed jBPM as services and Hibernate entities.
A developer may deploy jBPM into a stand-alone server, and then use the
administration console to deploy and test processes.
jBPM 4.1 ships with a web application in which a user can diagram and test
For this example, we're using a few libraries for AOP, transactions, the core Spring context, and, of
course, jBPM itself.
If you're looking to find out more, read the documentation, and get the downloadable binaries for
exploration, check out http://jboss.org/jbossjbpm/ . Th ere, you can find a lot of useful information.
Because we're looking to embed it, we'll simply get the libraries and use them in our own solution.
If you're using Maven, the pom.xml file will contain the latest version of the following dependency entries.
You may of course customize this as you see fit, but it's a good start. These are relatively current, and
known-to-be-working, versions of the jars required to get started, as of the time of this writing.
<!-- JBPM -->
<!-- JSR 250 annotations -->