8 Replies Latest reply on Jul 29, 2009 1:04 PM by Kerdudou Ronan

    Advices needed on process definitions deployment strategies

    Kerdudou Ronan Apprentice

      Hello,

      I'm facing a problem of process definitions deployment strategies in our production environment.

      This environment is not accessible using an IDE or ant. The prod team is only awaiting for an ear and sql scripts.

      I'm not sure it's possible to generate SQL scripts to deploy processes. So, I thought process definitions could deployed programmatically after the ear is deployed.
      We already have some initialisation codes that could call all the .

      deployment.deploy();

      But...

      I notice if we don't set the version of the process, it is re-deployed (and the version upgraded) each time our application is deployed even if the definition does not change. I don't think it's a good things to have bunch of deployment of the same process definition in our JBPM database.

      So I tried to put a version number for each process (which seems a good thing to do btw). But in this case, jBPM4 throw an exception because the process is already deployed. And I did not find any API to check if a jpdl.xml file has already been deployed.

      I could just catch and ignore the exception... But I would be pleased to have any advice on how do you have solved this problem.

      I found a solution that seems a little tricky for me. But the idea seems good. => http://seamframework.org/Documentation/JBPMDeploymentInProductionEnvironments

      Thanks for any comment.