Re: [Architecture] Generic workflow executor across the platform

I agree, +1 for a form-based approach. Being able to make changes there and observe the output BPEL would help users learn the format and structure. Thanks, Colin Roy-Ehri Software Engineer *WSO2, Inc. : wso2.com * *Mobile* : 812-219-6517 On Sat, Apr 25, 2015 at 6:07

Re: [Architecture] Generic workflow executor across the platform

Dear Pulasthi, having a way to define simple BPEL processes in a form-based manner would be great! Do you have some details on this? Best regards, Frank 2015-04-20 8:42 GMT+02:00 Pulasthi Mahawithana : > Hi Frank, > > We thought of having a simple form based approach at user end. We will use

Re: [Architecture] Generic workflow executor across the platform

Hi Frank, We thought of having a simple form based approach at user end. We will use some BPELs as templates and get the inputs from a form to customize it. On Sat, Apr 11, 2015 at 8:02 PM, Frank Leymann wrote: > Hi Pulasthi, > > when you have "users without BPEL knowledge" in mind, you assume

Re: [Architecture] Generic workflow executor across the platform

Hi Pulasthi, when you have "users without BPEL knowledge" in mind, you assume that these users have programming skills, correct? I.e. that they provide the "workflow process" in JavaScript, for example, correct? Or do you work on a new very easy-to-use workflow language? Best regards, Frank 2

Re: [Architecture] Generic workflow executor across the platform

Hi Manfred, The workflow support is not coupled to WSO2 BPS (except the tool for creation and deployment of simple workflows which I mentioned in the previous mail), it can be used with any external BPEL engine. So, In the case of an external BPEL engine we cannot share the data at DB level. That

Re: [Architecture] Generic workflow executor across the platform

Hi Pulasthi, thank you for info about BPMN implementation. Is the workflow executor database a datastore for workflow-data at product-level? The called workflow engine stores the workflow-data for execution in BPS, right? This leads to redundant workflow-data. Why should/can I not install "BPS-f

Re: [Architecture] Generic workflow executor across the platform

Hi Manfred, The executor can be used with both. "BPEL only" support is for the tool we plan to provide for creation and deployment of simple workflows. We will consider extending it to support BPMN also when the next WSO2 BPS version is released with BPMN support. On Mon, Apr 6, 2015 at 12:11 AM,

Re: [Architecture] Generic workflow executor across the platform

Hi Pulasthi, you mentioned only BPS/BPEL-engine. What about the BPS/BPMN-activiti-engine? Should it not a prefered way to define workflows? best regards Manfred 2015-04-04 14:40 GMT+02:00 Pulasthi Mahawithana : > Hi Frank, > > I sent a separate mail[1] with the architecture. Our main objective

Re: [Architecture] Generic workflow executor across the platform

Hi Frank, I sent a separate mail[1] with the architecture. Our main objective was to provide the workflow support for the events in IS and [1] was designed to address that. Furthermore we plan to provide a way to easily configure a workflow process and deploy it at BPS (for the users without BPEL

Re: [Architecture] Generic workflow executor across the platform

Hi Pulasthi, hi Tanja, can you provide a consolidated architecture figure, please? Can you also position in your architecture BPS? I assume the requirements you address by your architecture is the ability to create an "on-ramp workflow" for ES, AM,... in a "fast" way, correct? Thanks! Best re

Re: [Architecture] Generic workflow executor across the platform

Hi Tanya, The actual architecture is bit different from the one you mentioned here (I'll send a separate mail with details). The executors are responsible only for executing workflow in some manner (can be BPEL, Web Service or even some java code), and they can be registered as OSGI services. The

Re: [Architecture] Generic workflow executor across the platform

Hi Johann and all, As per the offline chat with Pulasthi, the executor serialize the workflow info and save in the database before calling the bpel service. (see the diagram below) ​So in our case if we are to use this component, we will have to do a network call with all the information for the

Re: [Architecture] Generic workflow executor across the platform

Hi Johann, Thanks for the response. IMO it is better if we can make the WorkflowRequestDAO more generic where we can plug any storing mechanism. WDYT? Thanks, Tanya On Tue, Mar 31, 2015 at 5:29 PM, Johann Nallathamby wrote: > Hi Tanya, > > On Tue, Mar 31, 2015 at 4:59 PM, Tanya Madurapperuma

Re: [Architecture] Generic workflow executor across the platform

Hi Tanya, On Tue, Mar 31, 2015 at 4:59 PM, Tanya Madurapperuma wrote: > Hi all, > > We are in the process of implementing the workflow support for ES and came > across the $Subject. > Although many products have worflow support, seems there is no generic > component to achieve this. > > The work

[Architecture] Generic workflow executor across the platform

Hi all, We are in the process of implementing the workflow support for ES and came across the $Subject. Although many products have worflow support, seems there is no generic component to achieve this. The workflow executor for APIM [1] cannot be used platform wide since they pass the ApiMgtDAO t