Hi all We are planning to add redirection support for workflow tasks to API Manager C5 (This feature was in C4 and used to plug in external billing engine for subscription). Following will be the suggested plan to implement it
In previous version of AM (see [1][2] for additional information), for subscription workflow, we sent back a json payload containing redirection related payload (redirection url, query params, message to display on the UI) when a subscription request is done (if a custom workflow is triggered and returns a HttpWorkflowResponse from it's execute() method) and from the UI handles the redirections. We are planning to support this for Application creation, subscription creation and api lifecycle state change workflows through the store and publisher REST API. following is the implementation steps (Use subscription creation workflow as the example to describe the steps) 1. Do a Post request to subscription creation (POST /subscriptions) 2. If a workflow is not triggered, sends back a 201 Created response with Location header for subscription resource 3. If a workflow is triggered and subscription goes to a pending state, sends back a 202 Accepted with WorkflowResponse object as a payload ( if the executor returns HttpWorkflowResponse response, then that payload with redirection urls etc will be sent as the payload.). Location header is sent back with the subscription resource url The user (in our case Store/Publisher application will have the implementation to support this) will have to implement the redirection using the rest api response payload. [1] [Architecture] [APIM] Extend Subscription Workflow [2] https://docs.wso2.com/display/AM1100/Configuring+HTTP+Redirection+for+Workflows Thanks, Chamila On Wed, Feb 1, 2017 at 2:02 PM, Yasima Dewmini <[email protected]> wrote: > Hi, > > Thank you for attending to the meeting and giving your valuable thoughts. > > According to the discussion we agreed to continue with our design since it > is a simpler scenario than above mentioned design in IS 5.1.0. > > Regards, > Yasima. > > > On Mon, Jan 30, 2017 at 6:32 PM, Harsha Thirimanna <[email protected]> > wrote: > >> Hi Nuwan, >> Yes as Johan said, we have implemented very generic solution for Workflow >> integration to the IS 5.1.0. It is not coupled with any workflow engine and >> default implementation is for WSO2 BPS. Template engine also very loosely >> couple with the workflow engine. We can discuss this and improve to make it >> more nice to use to across the platform. >> And it is not coupled with identity repos and can be easily port to the >> C5 as well. Since it was ab initial version, there may be some limitation >> that we can improve with this. >> >> *Harsha Thirimanna* >> *Associate Tech Lead | WSO2* >> >> Email: [email protected] >> Mob: +94715186770 <+94%2071%20518%206770> >> Blog: http://harshathirimanna.blogspot.com/ >> Twitter: http://twitter.com/harshathirimann >> Linked-In: linked-in: http://www.linkedin.com/pub/ha >> rsha-thirimanna/10/ab8/122 >> <http://wso2.com/signature> >> >> On Mon, Jan 30, 2017 at 4:01 PM, Darshana Gunawardana <[email protected]> >> wrote: >> >>> Hi NuwanD, >>> >>> C5 workflow implementation for IS not started yet. C4 implementation can >>> be found in following locations, >>> >>> - Core implementation: https://github.com/wso2/carbon >>> -identity-framework/tree/master/components/workflow-mgt >>> >>> <https://github.com/wso2/carbon-identity-framework/tree/master/components/workflow-mgt> >>> - User-management workflow implementation: https://github >>> .com/wso2-extensions/identity-user-workflow >>> <https://github.com/wso2-extensions/identity-user-workflow> >>> >>> Regards, >>> >>> On Mon, Jan 30, 2017 at 2:57 PM, Nuwan Dias <[email protected]> wrote: >>> >>>> Yes, we will try to see if we can reuse anything. Regarding the points >>>> noted down by Darshana, yes, we have the same objectives and the proposed >>>> design achieves all of them too. >>>> >>>> Is the C5 code available somewhere yet? >>>> >>>> On Mon, Jan 30, 2017 at 2:53 PM, Yasima Dewmini <[email protected]> >>>> wrote: >>>> >>>>> Hi Darshana, >>>>> >>>>> Thank you for your input. I will look into above approach and try to >>>>> figure out whether we can use same approach. >>>>> >>>>> Regards, >>>>> Yasima. >>>>> >>>>> On Mon, Jan 30, 2017 at 3:04 AM, Darshana Gunawardana < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi Yasima\NuwanD, >>>>>> >>>>>> With IS 5.1.0 it was implemented generic workflow design[1] that can >>>>>> be used in any product. >>>>>> >>>>>> (Quoting Prabath) >>>>>> It was designed to to achieve, >>>>>> >>>>>>> 1. Simplicity. Keep simple things simple and have provisions to add >>>>>>> more complex stuff >>>>>>> 2. Not coupled into any implementation. No hard coupling to BPEL >>>>>>> 3. Not coupled into WSO2 BPS. (part of 2 as well) >>>>>>> 4. Not specific to IS >>>>>> >>>>>> >>>>>> Have you evaluated that? >>>>>> >>>>>> [1] "[Architecture] Workflow Implementation in IS 5.1.0" >>>>>> >>>>>> Thanks, >>>>>> >>>>>> On Thu, Jan 26, 2017 at 2:52 PM, Nuwan Dias <[email protected]> wrote: >>>>>> >>>>>>> We should be going with BPMN. >>>>>>> >>>>>>> On Thu, Jan 26, 2017 at 2:50 PM, Isuru Haththotuwa <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Have we made a decision whether to use BPEL or BPMN? IMHO better to >>>>>>>> go with BPMN, which is simpler. Also, for the default BP engine, we >>>>>>>> should >>>>>>>> consider Camunda as well, and pick the best one. >>>>>>>> >>>>>>>> [1]. https://camunda.org/ >>>>>>>> >>>>>>>> On Thu, Jan 26, 2017 at 2:25 PM, Yasima Dewmini <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Jan 26, 2017 at 2:18 PM, Malintha Amarasinghe < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> Hi Yasima, >>>>>>>>>> >>>>>>>>>> Do we consider workflow related RESTful API implementation as >>>>>>>>>> well in this scope? >>>>>>>>>> >>>>>>>>> We have some things to clarify. I will update you with fully >>>>>>>>> detailed diagram. >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Thanks >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Thu, Jan 26, 2017 at 2:09 PM, Yasima Dewmini <[email protected]> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> @Shani, >>>>>>>>>>> Thnak you shani for your input. Above diagram shows only the >>>>>>>>>>> basic idea how workflow extension works. I am thinking of adding >>>>>>>>>>> more >>>>>>>>>>> detailed diagram of how the workflow requests are processed with >>>>>>>>>>> workflow >>>>>>>>>>> engine and how to send the status back to APIM. >>>>>>>>>>> >>>>>>>>>>> @Lakshman, >>>>>>>>>>> With the discussion had with Nuwand, we are going to use >>>>>>>>>>> Activiti[1] as default workflow engine. >>>>>>>>>>> >>>>>>>>>>> @Abimaran >>>>>>>>>>> The complete() method will do the DB update same as in C4. But >>>>>>>>>>> that DB implementation will be in Store Impl layer. >>>>>>>>>>> We are planning to use Activiti as default workflow engine. >>>>>>>>>>> And this is an example worklfow of Application creation. We hope >>>>>>>>>>> to implement all the workflow we have in C4. >>>>>>>>>>> >>>>>>>>>>> [1] https://www.activiti.org/ >>>>>>>>>>> >>>>>>>>>>> Regards, >>>>>>>>>>> Yasima. >>>>>>>>>>> >>>>>>>>>>> On Thu, Jan 26, 2017 at 1:08 PM, Abimaran Kugathasan < >>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Yasima, >>>>>>>>>>>> >>>>>>>>>>>> Don't we need to update database upon workflow completion? >>>>>>>>>>>> Also, Are we going to write workflow engine from scratch or going >>>>>>>>>>>> to use >>>>>>>>>>>> WSO2 BPS or Activiti [1]? >>>>>>>>>>>> >>>>>>>>>>>> Also, this should be extended to other workflows as well? >>>>>>>>>>>> >>>>>>>>>>>> [1] : https://www.activiti.org/ >>>>>>>>>>>> >>>>>>>>>>>> On Thu, Jan 26, 2017 at 12:08 PM, Shani Ranasinghe < >>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Yasima, >>>>>>>>>>>>> >>>>>>>>>>>>> Just one thing, IMO we need to incorporate the complete >>>>>>>>>>>>> process if the workflow is enabled also right? in that case the >>>>>>>>>>>>> workflow >>>>>>>>>>>>> engine will call APIM with the status. >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, Jan 26, 2017 at 11:29 AM, Yasima Dewmini < >>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi all, >>>>>>>>>>>>>> >>>>>>>>>>>>>> We are going to implement workflow extensions for APIM. >>>>>>>>>>>>>> Following diagram shows the proposed solution. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Your thoughts and suggestions regarding this are highly >>>>>>>>>>>>>> appreciated. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>> Yasima. >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> http://wso2.com/signatureYasima Dewmini >>>>>>>>>>>>>> Software Engineer, WSO2, Inc. >>>>>>>>>>>>>> Email: [email protected] >>>>>>>>>>>>>> Mobile: +94713117081 <+94%2071%20311%207081> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>>>> [email protected] >>>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Thanks and Regards >>>>>>>>>>>>> *,Shani Ranasinghe* >>>>>>>>>>>>> Senior Software Engineer >>>>>>>>>>>>> WSO2 Inc.; http://wso2.com >>>>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>>>> >>>>>>>>>>>>> mobile: +94 77 2273555 <+94%2077%20227%203555> >>>>>>>>>>>>> Blog: http://waysandmeans.blogspot.com/ >>>>>>>>>>>>> linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>>> [email protected] >>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Thanks >>>>>>>>>>>> Abimaran Kugathasan >>>>>>>>>>>> Senior Software Engineer - API Technologies >>>>>>>>>>>> >>>>>>>>>>>> Email : [email protected] >>>>>>>>>>>> Mobile : +94 773922820 <+94%2077%20392%202820> >>>>>>>>>>>> >>>>>>>>>>>> <http://stackoverflow.com/users/515034> >>>>>>>>>>>> <http://lk.linkedin.com/in/abimaran> >>>>>>>>>>>> <http://www.lkabimaran.blogspot.com/> >>>>>>>>>>>> <https://github.com/abimarank> <https://twitter.com/abimaran> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>> [email protected] >>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> http://wso2.com/signatureYasima Dewmini >>>>>>>>>>> Software Engineer, WSO2, Inc. >>>>>>>>>>> Email: [email protected] >>>>>>>>>>> Mobile: +94713117081 <+94%2071%20311%207081> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Architecture mailing list >>>>>>>>>>> [email protected] >>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Malintha Amarasinghe >>>>>>>>>> Software Engineer >>>>>>>>>> *WSO2, Inc. - lean | enterprise | middleware* >>>>>>>>>> http://wso2.com/ >>>>>>>>>> >>>>>>>>>> Mobile : +94 712383306 <+94%2071%20238%203306> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> http://wso2.com/signatureYasima Dewmini >>>>>>>>> Software Engineer, WSO2, Inc. >>>>>>>>> Email: [email protected] >>>>>>>>> Mobile: +94713117081 <071%20311%207081> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Architecture mailing list >>>>>>>>> [email protected] >>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Thanks and Regards, >>>>>>>> >>>>>>>> Isuru H. >>>>>>>> +94 716 358 048 <+94%2071%20635%208048>* <http://wso2.com/>* >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Architecture mailing list >>>>>>>> [email protected] >>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Nuwan Dias >>>>>>> >>>>>>> Software Architect - WSO2, Inc. http://wso2.com >>>>>>> email : [email protected] >>>>>>> Phone : +94 777 775 729 <+94%2077%20777%205729> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Architecture mailing list >>>>>>> [email protected] >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Regards, >>>>>> >>>>>> >>>>>> *Darshana Gunawardana*Associate Technical Lead >>>>>> WSO2 Inc.; http://wso2.com >>>>>> >>>>>> *E-mail: [email protected] <[email protected]>* >>>>>> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise . >>>>>> Middleware >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> http://wso2.com/signatureYasima Dewmini >>>>> Software Engineer, WSO2, Inc. >>>>> Email: [email protected] >>>>> Mobile: +94713117081 <+94%2071%20311%207081> >>>>> >>>> >>>> >>>> >>>> -- >>>> Nuwan Dias >>>> >>>> Software Architect - WSO2, Inc. http://wso2.com >>>> email : [email protected] >>>> Phone : +94 777 775 729 <+94%2077%20777%205729> >>>> >>> >>> >>> >>> -- >>> Regards, >>> >>> >>> *Darshana Gunawardana*Associate Technical Lead >>> WSO2 Inc.; http://wso2.com >>> >>> *E-mail: [email protected] <[email protected]>* >>> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise . >>> Middleware >>> >>> _______________________________________________ >>> 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 >> >> > > > -- > http://wso2.com/signatureYasima Dewmini > Software Engineer, WSO2, Inc. > Email: [email protected] > Mobile: +94713117081 <+94%2071%20311%207081> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Regards, Chamila Adhikarinayake Senior Software Engineer WSO2, Inc. Mobile - +94712346437 Email - [email protected] Blog - http://helpfromadhi.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
