Advices needed on process definitions deployment strategies

[ronanker]

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.

[rams.rapol]

This is how we are working around for this issue..

You can get the list of process definitions deployed with given process def name..

List<ProcessDefinition> processDefList = repositoryService.createProcessDefinitionQuery()
 .processDefinitionName(processDefName)
 .orderDesc(ProcessDefinitionQuery.PROPERTY_VERSION)
 .page(0, 1).list();

loop through it to get highest version..

Long version = processDefList.get(0).getVersion()

now compare above version with a property file having process definition and version number as key value pair.

If they match, don't do anything, else go ahead and update deployment.

[kukeltje]

A properties file should not be needed since for jBPM4 the version can be in the processdefinition

Besides that , I do think that this belongs 'hidden' in the implementation of the deployer and silently to nothing (or maybe log just a warning)

Please file a jira issue for this.

[ronanker]

Thanks for your replies,

@kukeltje
If I understand you, you say that the jBPM repositoryService should not throw the exception, right ?

I would be pleased to post a jira but it seems that I have a readonly access to the jboss' jira.

[kukeltje]

Did you login? Then you should have write access to

And yes, I think it should not throw an exception

[ronanker]

Did you login?

Yes. I can see my name on the upper right corner and edit my profile. But I did not find how to create a jira.

[kukeltje]

There is a 'create new issue' at the top of the screen, next to

HOME BROWSE PROJECT FIND ISSUES CREATE NEW ISSUE

[kukeltje]

and in the top-right corner is a 'help' icon

[ronanker]

There is a 'create new issue' at the top of the screen, next to

HOME BROWSE PROJECT FIND ISSUES CREATE NEW ISSUE

No. There is no link like that on my screen. just

HOME BROWSE PROJECT FIND ISSUES