AquaLogic to jBPM porting?

[raja021084]

Dear All,

We are migrating our BPM workflow from AquaLogic BPM to jBPM. AquaLogic BPM is very much inline with BPMN2.0 specification and it supports all the BPMN2 activities.

I would like to whether jBPM supports all the activities in BPMN2.0 Specification?

What is the stable jBPM version which can be used for development?

Thanks,

Raja

[salaboy21]

I recommend yourself 5.3.Final.

If you find that something is not supported that is being supported in aqua logic, please report it into the jira system, so we can implement it.

You also have the latest source code available (5.4.0-SNAPSHOT) to try the latest features suported if you want.

Cheers

[salaboy21]

please mark your questions as answered

[raja021084]

Thank you Mauricio.

We also considering an alternate approach for this. Could you please give your input on this.

1) Migrate ALBPM workflow into jBPM 3.x JPDL workflow. Considering jBPM 3.x is very matured and widely used by many customers.

2)Later when jBPM 5.x become stable and mature, migrate JPDL workflow into jBPM 5.x BPMN workflow.

(I assume that JBoss provides necessary documents and utilities for JPDL to BPMN  migration as part of jBPM 3.x to jBPM 5.x porting)

Thanks,

Raja

[salaboy21]

There are migration tools between jPDL and BPMN2 but I don't not recommend that option. If you are planning to migrate now you should migrate to BPMN2 directly, because there is no one to one transalation between the jPDL and BPMN2 node semantics. If you are planning to migrate from aqua logic to jPDL you will need to refactor your processes, the same will happen when you want to migrate to BPMN2. If you are planning to do process refactorings just save yourself one round and go ahead with BPMN2.

Cheers

[raja021084]

Thank you Mauricio. We are on the verge of finalizing our porting strategy. We decided to port into JPDL only. Could you please help me with these questions. 
1)      To mitigate risks associated with JBPM5.3 (since released last month only), we would like to migrate process definition from ALBPM to JBPM3 and curious to know the support period for JBPM3.  
2)      As per our understanding JBOSS 5.0 should be used for JBPM3. Please advise, if JBPM3 is supported by later versions of JBOSS AS(JBoss 7)  also. 
3)      In existing ALBPM process definition we could see 65-70% of albpm:extensions and logic in PBL (ALBPM scripting), for which we are planning to do the following: 
                        a.       Write Handlers in JAVA (to replace scripting part which is currently written using PBL)
                         b.      Use IDE (JDeveloper Studio) to create process definition file. 
  I appreciate all your help. 

Thanks,
Raja

[salaboy21]

Hi Raja,

Let's go to the answers:

1) you should contact [e-mail] and they will foward you to the right people who can provide you that answer.

2) Both jBPM3 and jBPM5 can run in any container, is just matter of configuration, there shoudln't be any strong dependency on any container

3) If you migrate to jPDL you will probably can achieve exactly the same as you have in those extensions, and you will need to do that twice, first for jBPM3 and then for jBPM5.

It's your call.

Cheers

[tsurdilovic]

The jBPM Web Designer has support for the jPDL 3.2 ->BPMN2.0 conversion project. It has been tested with simple processes. Even tho this is still BETA, it is useful to get the conversion started and then make modifications and add execution semantics to the generated BPMN2.0..just makes life a little simpler than having to start from scratch.

HTH