其中工作流引擎选择？ [英] Which workflow engine to choose?
问题描述
我们目前正在评估一个BPM引擎的过程，我真的AP preciate社会各界意见。我做我自己的尽职调查，也想听听基于实现故事的建议。
We are currently in the process of evaluating a BPM engine and I'd really appreciate the community input. I am doing my own due diligence but would also like to hear on the suggestion based on implementation stories.
我的主要评价标准如下
- 开源和OEM友好的许可
- 生产装置（成功案例有很大的帮助）
- 商业支持可用
- 开启标准支持 - BPMN
- 基于输入工作流的动态创建/组装
- 嵌入
目前我正在评估的Activiti和jBPM。 博尼塔开放BPM似乎是一个很好的候选人，以及，但从来没有使用过。你们是否有任何博尼塔成功的部署？
Currently I am evaluating Activiti and JBPM. Bonita open BPM seems like a good candidate as well but never used it. Do you guys have any successful deployments on Bonita?
推荐答案
我刚刚一直在做的Activiti的评估VS jBPM的。
I've just been doing an evaluation of Activiti vs jBPM.
在实际上似乎有两种解决方案之间的很少。
In fact there seems to be very little between the two solutions.
- Activiti的就是Apache V2，jBPM的5.0也是Apache的V2。
- 我们目前正在使用的Activiti，但该项目仍然在开发中，所以我不能在其生产的鲁棒性评论。
- jBPM是开始产品化过程，所以对于5.x的支持将在2012年第一季度上市，见幻灯片32：<一href=\"http://www.slideshare.net/krisverlaenen/streamline-your-business-processes-and-enhance-productivity-by-using-jbpm\">jBPM演示。 jBPM 4中，不是由红帽支持。
- jBPM的4.x版不支持BPMN 2.0，但5.x的呢，Activiti的确实也是如此。 jBPM的5.0刚刚发布，其中包括BPMN 2.0的支持。所以，现在这两种解决方案支持BPMN 2.0。
- 我不太明白你的这个是什么意思，但你可以通过这两个API做了很多
- 同样，不知道你这是什么意思，你的意思是嵌入作为应用程序服务器的一部分，在这种情况下，是两个解决方案。
- Activiti is Apache V2, jBPM 5.0 is also Apache V2.
- We're currently using Activiti, but the project is still in dev, so I can't comment on its robustness in production.
- jBPM is beginning the productization process, so support for 5.x will be available in Q1 2012, see slide 32: jBPM demo. jBPM 4 was not supported by Redhat.
- jBPM 4.x did not support BPMN 2.0, but 5.x does, Activiti does as well. jBPM 5.0 has just been released, which includes support for BPMN 2.0. So now both solutions support BPMN 2.0.
- I'm not quite sure what you mean by this, but you can do a lot through both APIs
- Again, not sure what you mean by this, do you mean embedded as part of an application server, in which case, yes for both solutions.
我们的一个为jBPM的标准是用的Guvnor的互动，当我下载并运行演示安装的jBPM（28/03/2011），并有似乎仍然是一些重大的bug（的GUVNOR-1274 ），所以我个人测试了很多之前我选择去追求这一解决方案。
One of our criteria for jBPM was the interaction with Guvnor, and when I downloaded and ran the demo install for jBPM (28/03/2011) and there still seemed to be some major bugs (GUVNOR-1274), so I personally would test a lot more before I chose to pursue this solution.
事实上，我们将建议上述两种解决方案之一，但我们不知道哪个呢，我们来看看，今年更紧密更高版本。
In fact, we will be recommending one of the above two solutions, but we're not sure which yet, we'll look at it more closely later this year.
这篇关于其中工作流引擎选择？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
