Hi Senaka, With the previous release, we can define which workflow executor should get executed for a given operation. For example if we take Application Creation operation, we can specify to execute either ApplicationCreationSimpleWorkflowExecutor or ApplicationCreationWSWorkflowExecutor when a new application is created.
A workflow executor has two methods; execute - which can be used to send out a message to an external service notifying the creation of an application. complete - which is used to receive the final result of the workflow and determine if the application can be created or not. In the configuration we can specify which service should be invoked in the execute method, and which service should be used for receiving the status in complete method. Using these two operations, an external BPS workflow can be initiated by calling an external service, and the result of the workflow can be received by the API Manager to complete the application creation process. The Token Generation flow will operate in a similar fashion; - When a subscriber clicks the Generate button, a workflow will be initiated by the application registration request. Until this request is completed, further requests cannot be placed to register the same application. - An admin user either approves or declines the request - In the existing workflows ,this is done by a human task. Admin users can login to the Workflow-Admin, and see all the pending requests. - If the registration request is approved, it will complete the registration process by generating a consumerKey , consumerSecret pair. Accepting the output of the workflow and completing the actual registration can be done in two steps. In a distributed setup, there can be times the key manager nodes might not be able to create consumerKey, secret pair at the exact time the registration process receives the approval. AmilaD On Sat, Feb 8, 2014 at 2:06 PM, Senaka Fernando <sen...@wso2.com> wrote: > Hi Amila, > > Can you define steps (or the extension points) of the existing workflows > and how for example they can be interfaced with an external business > process? And, also the possible steps that you plan to introduce for these > new workflows? > > Thanks, > Senaka. > > > On Thu, Feb 6, 2014 at 11:40 AM, Amila De Silva <ami...@wso2.com> wrote: > >> Hi, >> >> In the previous API Manager release we incorporated workflows for the >> following operations; >> >> 1. User Signup. >> >> 2. Application Creation. >> >> 3. Creating subscriptions. >> >> As a part of the API Manager 2.0.0 release, we are planning to integrate >> workflows for other useful business operations. These are the areas we have >> identified currently; >> >> 1. Token Generation - As of now, after creating an application, >> application owner can Generate a Production or Sandbox access token (or >> both) for an application. What actually happens at this point is the >> application getting registered as an OAuth application of either type. With >> this feature, a workflow will be executed when registering the application, >> so it'll be after an admin user confirms, the application will be able to >> obtain Production (or Sandbox) keys. Using this feature administrators can >> allow users\developers to create Sandbox keys to continue >> development\testing , but defer generating Production keys until the >> testing is done. >> >> 2. Adding/Updating Comments - Currently users can post comments about the >> APIs and these will be displayed in the store without any moderation. With >> this feature, comments can be moderated before they are displayed. >> >> Appreciate your suggestions on these. >> >> Further we'd like to identify any additional useful operations we can >> integrate workflows for. >> >> -- >> *Amila De Silva* >> >> *Software Engineer* >> WSO2 Inc. >> mobile :(+94) 775119302 >> >> >> _______________________________________________ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > > *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* > Senior Technical Lead; WSO2 Inc.; http://wso2.com > > > > * Member; Apache Software Foundation; http://apache.org > <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 > 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*; > > > *M: +94 77 322 1818 <%2B94%2077%20322%201818> Linked-In: > http://linkedin.com/in/senakafernando > <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Amila De Silva* *Software Engineer* WSO2 Inc. mobile :(+94) 775119302
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
