JBPM6 process definition versioning

[Nishant Parmar]

Needed urgent help!

We have process definition deployed in production and lots of process instances are initialized and in flight.

Now there are changes required to be done in process definition (.bpmn file) to accommodate other business scenarios.

We understand that we can not just replace the old .bpmn file with new one because old .bpmn file may be referred by in flight processes.

What is easiest and best way to handle this situation?

Note: We are using JBPM 6.0

[Maciej Swiderski]

there are several options:

- migrate your process instances - here you can read up a bit on how to do it http://mswiderski.blogspot.com/2014/11/process-instance-migration-made-easy.html

- if your process definition changes are backward compatible you could replace the bpmn2 files (kjar) so processes will pick up new definitions though they must be backward compatible so only new things were added

- deactivate given deployment (kjar) and provide new version, that way new process instances will be started on new definitions and old will continue with old

all listed above applies when you use workbench if you have jBPM embedded you can have slightly different options

Maciej

--
You received this message because you are subscribed to the Google Groups "jBPM Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-developme...@googlegroups.com.
To post to this group, send email to jbpm-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-development/9903ce0c-c779-45a9-b8a5-2a8b8551c892%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Nishant]

Thanks a lot Maciej!

We have jbpm embedded in our application. In this case what option I can try?

[Akhil Soman]

Hi Nishant,

did you solved the issue. iwe also facing the same issue in our production. we also having jbpm embedded with our application. if you can tell me how you resolved this issue, it will be a great help for me.

On Monday, April 18, 2016 at 4:03:53 PM UTC+5:30, Nishant wrote:

Thanks a lot Maciej!

We have jbpm embedded in our application. In this case what option I can try?

On Apr 18, 2016 2:30 AM, "Maciej Swiderski" <swiders...@gmail.com> wrote:

there are several options:

- migrate your process instances - here you can read up a bit on how to do it http://mswiderski.blogspot.com/2014/11/process-instance-migration-made-easy.html

- if your process definition changes are backward compatible you could replace the bpmn2 files (kjar) so processes will pick up new definitions though they must be backward compatible so only new things were added

- deactivate given deployment (kjar) and provide new version, that way new process instances will be started on new definitions and old will continue with old

all listed above applies when you use workbench if you have jBPM embedded you can have slightly different options

Maciej

2016-04-18 6:54 GMT+02:00 Nishant Parmar <nishan...@gmail.com>:

Needed urgent help!

We have process definition deployed in production and lots of process instances are initialized and in flight.

Now there are changes required to be done in process definition (.bpmn file) to accommodate other business scenarios.

We understand that we can not just replace the old .bpmn file with new one because old .bpmn file may be referred by in flight processes.

What is easiest and best way to handle this situation?

Note: We are using JBPM 6.0

--
You received this message because you are subscribed to the Google Groups "jBPM Development" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-dev...@googlegroups.com.

[Akhil Soman]

Hi Maciej,

Could you please tell us the solution for this case when using jbpm embedded with the application.