Sanjeewa, That will be phase 2 :) A web editor for the flows is definitely something we have to do and will do, but not for the next release!
Isabelle. __________________________________________________ Isabelle Mauny Director, Product Management; WSO2, Inc.; http://wso2.com/ On Aug 2, 2013, at 3:10 PM, Sanjeewa Malalgoda <[email protected]> wrote: > > > On Fri, Aug 2, 2013 at 4:16 PM, Isabelle Mauny <[email protected]> wrote: > All, > > So this is part of the overall plan of supporting API manager in DevStudio. > > Today, you can develop and deploy sequences, leveraging the full power of ESB > mediators, as per this : > http://docs.wso2.org/wiki/display/AM140/Adding+a+Mediation+Extension - > However, it's a manual process. > > The purpose of this feature is to make the deployment of sequences easier : > as a developer, I can create sequences to be deployed at the gateway level > from DevStudio and push them to the AM repository. When an API is published, > I can pick the sequence from the sequences list as an IN or OUT sequence, and > the manual deployment process explained above would happen automatically (so > for example, I would have a REST_to_SOAP_SERVICEA sequence, apply it as IN > sequence for APIA and it would be automatically applied to the right place > (i.e. saved as APIA:v1.0.0--IN) in the right folder. If sequences need to be > composed, this would need to happen in DevStudio, not in the API Publisher UI > (for now). > This would be really useful feature IMO. But how external API publisher > connect and create sequences using developer studio(I mean how we can do this > in production deployment)? Also i would like to share my thought on > supporting additional operations to API flow. How about having optimized view > of ESB mediation flow editor inside API manager? So we can let users to add > different operations like adding header, remove header, log message, enrich > message and etc. We do not necessary to let all publishers to do this we an > have role based control mechanism. We can ask API publishers to go and create > API but if they want to do any additional operations we can direct them to > sequence editor user interface. I was thinking about having such editor in > API manager publisher ui. Also i have observed some of other API management > tools support that type of mediation flow editors. > > Thanks, > Sanjeewa. > > So implementing this is two-fold > a) Tools to push the sequences into the right place in the API Manager > registry from Dev Studio ( or allow users to export sequences and import them > manually using the check-in client or similar in case remote access to GW > registry is not allowed). > b) Changes in publisher UI to pick sequence file from registry and deploy > them to the gateway. > > I think those two actions need to be decoupled to allow deploying one > sequence to a cluster of gateways at publishing time. > > Isabelle. > __________________________________________________ > > Isabelle Mauny > Director, Product Management; WSO2, Inc.; http://wso2.com/ > > > On Jul 31, 2013, at 9:39 PM, Sumedha Rubasinghe <[email protected]> wrote: > >> I think we should wait for Isabelle to provide explanation. I am also not >> clear of what is the exact requirement. >> >> Isabelle, This is regarding "Feature #72: Extension Point to associate >> sequences to inbound/outbound/fault flows" . Could you elaborate bit more >> please? >> >> >> On Wed, Jul 31, 2013 at 9:07 PM, Sanjeewa Malalgoda <[email protected]> >> wrote: >> >> >> On Wed, Jul 31, 2013 at 1:20 PM, Vijayaratha Vijayasingam <[email protected]> >> wrote: >> Hi all; >> >> Our requirement >> >> Allow users to create their own sequences and make them available in the API >> configuration. A developer creates the necessary sequences to say log, audit >> requests, may be add authorization via XACML , whatever is needed and pushes >> those with a description to the API publisher repository. When a publisher >> comes in (@ publisher UI) and publishes in API, the list of sequences is >> visible and he can pick one from the lists. >> >> Existing feature >> >> Currently we have a mediation extension point(it is a synapse rest handler) >> where, it picks the existing sequences (which are deployed following a >> naming convention) and whenever a request comes in to the API, handler >> checks whether a custom sequence available for that particular API and if it >> is available it executes that custom sequence . >> >> Implementation >> >> We could use Devstudio to develop the custom sequences and deploy them in >> APIManager. From the publisher UI, we could provide a UI option to select >> the existing sequences. >> Once selected, we could change the sequence name to follow the naming >> convention(needed for handler) and store them in the registry (should we >> store at local registry(file sytem)/user registry?) >> Handler can take care of the execution part(it is already implemented) >> So who is going to develop and add those sequences to API gateway? I guess >> it should done by administrator of system. >> If we need to log incoming message or some headers of incoming requests we >> need to add this to in sequence. Or we may need to add it to out sequence. >> Are we going to support something like that? >> >> Thanks. >> Sanjeewa. >> >> >> >> Please provide suggestions.... >> >> Thanks. >> -- >> -Ratha >> mobile: (+94)755906608 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> >> >> >> -- >> >> Sanjeewa Malalgoda >> WSO2 Inc. >> Mobile : +94713068779 >> >> blog :http://sanjeewamalalgoda.blogspot.com/ >> >> >> >> >> >> -- >> /sumedha >> b : bit.ly/sumedha > > > > > -- > > Sanjeewa Malalgoda > WSO2 Inc. > Mobile : +94713068779 > > blog :http://sanjeewamalalgoda.blogspot.com/ > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
