[Architecture] Sandbox support in API Manager

[Prabath Siriwardena]

On Wed, Mar 28, 2012 at 11:55 AM, Sumedha Rubasinghe <sumedha at wso2.com>wrote:

>
>
> On Tue, Mar 27, 2012 at 11:02 PM, Paul Fremantle <paul at wso2.com> wrote:
>
>> Folks
>>
>> Are we doing anything to support a "sandbox" model for APIs in the API
>> Manager.
>>
>> I have a really simple approach that I think might work:
>>
>> 1) When you publish an API you can specify two endpoints. The real
>> endpoint and the "sandbox" endpoint.
>> 2) Users who subscribe to the API get two keys - a "full" key and a
>> sandbox key.
>> 3) We automatically route requests to the right URL based on which key.
>>
>> The result is that to change from sandbox to production all the user has
>> to do it switch keys.
>>
>
> I guess there needs to be a change happening @ the Synapse API definition
> to support this as well.
> Right now it looks like following.
>

One way to do is - the API Handler can set a property based on the Key -
whether its a sandbox end point or not and based on that property we can
can route..?

Thanks & regards,
-Prabath


>
> <api xmlns="http://ws.apache.org/ns/synapse"  name="DelciousAPI"
> context="/deli">
>         <resource methods="GET" url-mapping="/tags/get">
>             <inSequence>
>                 <property name="REST_URL_POSTFIX" scope="axis2"
> action="remove"/>
>                 <send>
>                     <endpoint name="Delicious">
>                         <address uri="https://api.del.icio.us/v1/tags/get
> "/>
>                     </endpoint>
>                 </send>
>             </inSequence>
>             <outSequence>
>                 <send/>
>             </outSequence>
>         </resource>
> ...
> ...
> </api>
>
> So we need to have a condition check b4 figuring out which URI to be used
> when calling send mediator.
>
>
>
>
>> Paul
>>
>> --
>> Paul Fremantle
>> CTO and Co-Founder, WSO2
>> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>>
>> UK: +44 207 096 0336
>> US: +1 646 595 7614
>>
>> blog: http://pzf.fremantle.org
>> twitter.com/pzfreo
>> paul at wso2.com
>>
>> wso2.com Lean Enterprise Middleware
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, retransmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>>
>>
>> _______________________________________________
>> Architecture mailing list
>> Architecture at wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> /sumedha
> +94 773017743
>
> _______________________________________________
> Architecture mailing list
> Architecture at wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Thanks & Regards,
Prabath

Mobile : +94 71 809 6732

http://blog.facilelogin.com
http://RampartFAQ.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.wso2.org/pipermail/architecture/attachments/20120328/f8d21721/attachment.html>