Hi Chathura, ​what is the semantics of the deployment URL (second bullet): is this the endpoint where a BPEL archive can be deployed? Or is this the URL of an archive that contains all the artifacts to create a BPEL engine where I can deploy and execute the BPEL file? I suspect the first alternative is what you mean - just double-check.
I don't understand your third bullet: when you deploy a BPEL archive you (nearly always) deploy all roles of all partner links. After that an instance of the process model can be instantiated by any external source by sending messages to the ports that correspond to initiating activities of the process model. The same is true in case a BPEL file uses the BPEL4People extension, i.e. in case some activities are implemented by human tasks. Continuing on the "Webapp URL" (it must be something implementation specific that we have done at WSO2): A process model may be initiated by activities that have not user interaction at all (i.e. that is no peopleActivity activity kicking-off a new instance of the process model). What is the Webapp URL all about in this case? Pushing the "deploy" button is done by non-business-oriented users because it will require quite some technical information, right? I.e. do we support in the Process Store corresponding role models to avoid "frustration" by business users when pushing the "deploy" button? Best regards, Frank 2014-12-03 12:26 GMT+01:00 Chathura Ekanayake <[email protected]>: > > 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 > > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
