<p>I'm looking into integrating jBPM with my current project, so far so good just including the  jpdl jar in my ear and using the spring modules 0.8 jbpm module, however I've got to have a reasonable way of going from my changes to to the process definition in the designer to deployment in production.</p>

<p>The path has to be repeatable in a number of environments (dev, many test, staging and then prod) and ideally should be done while the system itself is not running.</p>

<p>I'd Ideally package the entire definition as an SQL script, however I haven't seen any tool to translate from processdefinition.xml to sql and assembling it all manually seems too fiddly and error prone.</p>

<p>Has anyone else out there had any experiences here?</p>

<p>The system is running on websphere 6.1 and it's my preference to avoid executing java code at migration time (running java code to generate artifacts that can then be used during migration is ok though)</p>

Why not use the ant task extensions provided by JBPM specifically
```
DeployProcessTask
```
. You can deploy to different environments having just a single
```
.par
```
file and the corresponding
```
jbpm-cfg.xml
```
for the various dev/test/staging/prod environments. The only change you might have to do is to configure your hibernate config to directly connect to the database instead of using the datasource.