+1
Best regards, Frank 2014-12-04 4:40 GMT+01:00 Chathura Ekanayake <[email protected]>: > Hi Chinthana, > > Process center is not used to interact with the BPS runtime or HT runtime. > Instead, end users use it to search/discover available processes and to > execute them if possible. If a user wants to execute a process, process > center delegates it to the associated webapp, which runs separately from > the process center. > > The idea here is that the process center connects all BPM related > products/runtimes in to a single platform. > > Regards, > Chathura > > On Thu, Dec 4, 2014 at 7:20 AM, Srinath Perera <[email protected]> wrote: > >> +1, we need to make sure terminology and wording matches those scenarios. >> For example it should be "Start a Process" not "Create Instance" etc >> (latter is process jargon and user is not interested). >> >> --Srinath >> >> On Wed, Dec 3, 2014 at 7:13 PM, Chathura Ekanayake <[email protected]> >> wrote: >> >>> Hi Srinath, >>> >>> Yes, if a process is already deployed, it can just store the deployment >>> URL. >>> >>> An example scenario would be: >>> An employee wants to claim a travel expense. He logs in to the process >>> center deployed in his organization and search for travel expense claim >>> processes. This process can be in different formats. If only a textual >>> process or a non-executable BPMN is available, he just follows the >>> mentioned steps manually. If there is an associated executable model, he >>> can click the "Start" button to initiate an automated process. In that >>> case, he will be directed to the associated web app where he (and other >>> participants) can provide details via human tasks. >>> >>> As a next step, we can associate event streams with such executable >>> processes to facilitate runtime analysis. I will initiate another thread on >>> that after refining this idea bit more. >>> >>> Regards, >>> Chathura >>> >>> On Wed, Dec 3, 2014 at 5:49 PM, Nandika Jayawardana <[email protected]> >>> wrote: >>> >>>> Hi Chathura, >>>> >>>> In this scenario, does the process center discover the process models >>>> and tasks deployed in BPS or a user manually configure / upload processes >>>> at process center which are deployed to BPS by a user action ? >>>> >>>> Regards >>>> NAndika >>>> >>>> On Wed, Dec 3, 2014 at 5:00 PM, Srinath Perera <[email protected]> >>>> wrote: >>>> >>>>> Hi Chathura, >>>>> >>>>> I think one other case is it is deployed already, and we just get a >>>>> URL. >>>>> >>>>> Also, I think we need to think how above can be useful in real life >>>>> scenario, basically we need to come up with a full story on how above can >>>>> be used. >>>>> >>>>> --Srinath >>>>> >>>>> >>>>> >>>>> On Wed, Dec 3, 2014 at 4:56 PM, Chathura Ekanayake <[email protected]> >>>>> wrote: >>>>> >>>>>> >>>>>> Executable process model is a BPEL or BPMN model, which can be >>>>>> executed in a process runtime. We can support executable models in >>>>>> process >>>>>> center as follows: >>>>>> >>>>>> Executable model contains: >>>>>> - Process archive (e.g. BPEL archive) >>>>>> - [optional] Deployment URL (e.g. URL of a BPS server) >>>>>> - [optional] Webapp URL - This URL points to a web application which >>>>>> can be used to create a new process instance and work on human tasks >>>>>> defined in the process (i.e. this is the operational UI for the process). >>>>>> >>>>>> If a webapp URL is provided, process center provides a "Start" button >>>>>> which simply directs to that URL. For example, employees can search >>>>>> process >>>>>> models from the store side and start them if they are executable. If it >>>>>> is >>>>>> not provided, the human task web app shipped with BPS can be used to >>>>>> start >>>>>> and work on human tasks. >>>>>> >>>>>> If a deployment URL is provided, a "Deploy" button is shown, which >>>>>> deploys a process archive in the corresponding BPS server. >>>>>> >>>>>> Thoughts... >>>>>> >>>>>> Regards, >>>>>> Chathura >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> ============================ >>>>> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera >>>>> Site: http://people.apache.org/~hemapani/ >>>>> Photos: http://www.flickr.com/photos/hemapani/ >>>>> Phone: 0772360902 >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Nandika Jayawardana >>>> Senior Technical Lead >>>> WSO2 Inc ; http://wso2.com >>>> lean.enterprise.middleware >>>> >>> >>> >> >> >> -- >> ============================ >> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera >> Site: http://people.apache.org/~hemapani/ >> Photos: http://www.flickr.com/photos/hemapani/ >> Phone: 0772360902 >> > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
