[JBPM4] Migration from one process definition version to ano

[sushantgupta402]

We have a requirement that to comply with certain laws the business process definition may be changed and all the process instances should follow the new path defined in the new process definition. I have 2 questions here:
1. Is this doable/advisable?
2. Is there something out of the box which JBPM4 provides to migrate to new process definition?

Thanks in advance.

[kukeltje]

please can you search the forum first (either with google or directly) and then get back with more detailed questions. In general my answers would be:

1: Yes, but not that easy / Depends
2: No

[vchira]

"kukeltje" wrote:
please can you search the forum first (either with google or directly) and then get back with more detailed questions. In general my answers would be:

1: Yes, but not that easy / Depends
2: No

I don't know who you think you are but can you frikin' stop posting this c..p in all posts? i searched google like crazy without an definite answer waht kind of deployment is officialy supported in jBPM 4.1 and how can we migrate Processes from one version to another. this is a Problem that all serios jBPM users have it!!! why don't you just write something about it in User docu or developer docu if you are so frikin' smart!!!!

[sebastian.s]

To answer your question, vchira: He's the guy answering the biggest amount of questions in a competent and friendly way in this forum in his free time (!!).

Features only make it into the user guide if they are considered to be stable, in the dev guide if they are considered to have at least a certain level of stability which means they are not supposed to still change a lot (there exceptions of course).

For you both:

Looking trough the issue list to be fixed in jBPM 4.3 easily brings up this issue which was reopened:

https://jira.jboss.org/jira/browse/JBPM-165

Note the link Tom posted in the comments:

http://calebpowell.blogspot.com/2009/06/jbpm-migrations-our-approach.html

[vchira]

"sebastian.s" wrote:
To answer your question, vchira: He's the guy answering the biggest amount of questions in a competent and friendly way in this forum in his free time (!!).

maybe i saw only a small selection of his posts..if so than i bag your pardon. Even the most friendly advice in the world can not compare with the official docu.
Why isn't anywhere documented if deploying with "overwrite" is possible and if not how could one migrate the old definition process instances to the new process definition?

"sebastian.s" wrote:

Features only make it into the user guide if they are considered to be stable, in the dev guide if they are considered to have at least a certain level of stability which means they are not supposed to still change a lot (there exceptions of course).

For you both:

Looking trough the issue list to be fixed in jBPM 4.3 easily brings up this issue which was reopened:

https://jira.jboss.org/jira/browse/JBPM-165

Note the link Tom posted in the comments:

http://calebpowell.blogspot.com/2009/06/jbpm-migrations-our-approach.html

i found that feature request too,but id doesn't mean anything as log as jBPM 4.3 is not available.. or does it? ;)

[sebastian.s]

AFAIK it is documented that when you deploy new version of a process while the old ones remain useable in the system and existing process instances continue to use the old definition while newly started ones use the newone.

And it should also be documented that when you reference a process definition by its key always the newest one is used.

[sebastian.s]

i found that feature request too,but id doesn't mean anything as log as jBPM 4.3 is not available.. or does it? ;)

I don't know. I saw you've replied on Caleb's post. I would be happy if he was finally in the position to contribute his solution and even happier if his solution or a different one would make it into jBPM 4.3.

Till now I was not aware that process instance versioning would be a topic for me, too. But infact there are use cases for which I would need this functionality.

[koen.aers]

As I said in the post on the developer's forum, there will be support for instance migration in the upcoming release. The solution is somewhat different from Caleb's solution for jBPM 3.x.

Regards,
Koen

[kukeltje]

For the record:

- I never said I was smart...
- I'd be more than happy to contribute documentation and more detailed answers. Just make sure €3000 is added to my account each month (taxes paid) and I'll even code for you.
- If there is no definite answer there probably was little.
- Peace...

[vchira]

As I said in the post on the developer's forum, there will be support for instance migration in the upcoming release. The solution is somewhat different from Caleb's solution for jBPM 3.x.

Regards,
Koen

Can you pls clarify? what kind of sollution? wich post? if i know that the process instance will work with the new process definistion can i just change there process definition in DB or something? would that work?

[sebastian.s]

I doubt that just changing the process definition works. There is already documentation on this feature checked into the trunk. So why don't checkout the documentation to find out? :)

From what I saw in the documentation there are 3 basic use cases right now.