Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

Hi Keerthika, That approach looks so good since we can use this even in the past releases also. As I remember Thulasika used similar approach before. *Nadeeshaan Gunasinghe* Software Engineer, WSO2 Inc. http://wso2.com +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe <#>

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

I think best is first check with script mediator and if there are performance issues will move to class mediator approach. On Sat, Jan 30, 2016 at 12:56 PM, Keerthika Mahendralingam < keerth...@wso2.com> wrote: > +Nadeesan. > > On Sat, Jan 30, 2016 at 12:48 PM, Keerthika Mahendralingam < >

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

+Nadeesan. On Sat, Jan 30, 2016 at 12:48 PM, Keerthika Mahendralingam < keerth...@wso2.com> wrote: > +1 for class mediator. > > @Thulasika, As Malaka said in the code review, it is better to create a > common module for this function so that other connectors also make use of > it. > > On Sat,

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

+1 for class mediator. @Thulasika, As Malaka said in the code review, it is better to create a common module for this function so that other connectors also make use of it. On Sat, Jan 30, 2016 at 12:40 PM, Kathees Rajendram wrote: > Hi Thulasika, > > I think Script mediator

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

Hi All, I used the script mediator to store the access token then I tried to use ESB 4.10 registry persistence feature to store the access token. It works in 4.10 but It doesn't work with previous versions even we can't enable the connector in previous versions(4.8 & 4.9) so finally I have used

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

Hi Thulasika, I think Script mediator will have some performance impact on the mediation logic. You should create a class mediator to store the content into the registry. As Malaka said you should do load testing with both and compare performance with script mediator and class mediator. String

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

Hi All, If we implement this using esb 4.10 feature whole connector is compatible with ESB 4.10 only. Doing a separate version of each connector to support this feature is not good. So will proceed with script mediator approach. However we need to run some testing before implementing this for

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

Hi Thulashika, I think you can use the following script to save the feilds in registry. It will work with 4.8.1, 4.9.0 and 4.10 as well.

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

Hi , I am implementing common init method for ESB 4.9 and 4.10. For ESB 4.10 I use the property mediator to store new persistent content(accessToken) in the registry as following: when I enabling the connector artifact in ESB 4.9.0 I'm getting the following error due to scope "registry".How to

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

Hi Thulasika, This feature is not available in the WSO2 ESB 4.9.0. This is available from in 4.10. Thanks *Nadeeshaan Gunasinghe* Software Engineer, WSO2 Inc. http://wso2.com +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe <#>

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

Hi All, I have automated the cloud to cloud use case using ESB 4.10 registry persistence feature. The current approach is based on the following flow diagram. ​ Thanks, Thulasika On Tue, Dec 8, 2015 at 11:35 AM, Malaka Silva wrote: > Hi, > > One of the main issues we

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

Hi , I have written new init method to resolve above issue. In this method I used an endpoint which is provided by API to check whether accessToken is expired or not.For that, First I get accessToken from registry if the accessToken is null or expired then only call getAccessTokenFromRefressToken

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

Hi, I plan to use the naming for the new init method as autoInit. Thanks. On Mon, Jan 4, 2016 at 8:52 PM, Malaka Silva wrote: > Thulasika this looks good. Can you arrange a code review session for this > please. > > Also what are we calling this new method? > > On Mon, Jan

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

Thulasika this looks good. Can you arrange a code review session for this please. Also what are we calling this new method? On Mon, Jan 4, 2016 at 5:41 PM, Thulasika Vijayanathan wrote: > Hi , > > I have written new init method to resolve above issue. In this method I >

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

Hi, I will look into that as well. Thanks, On Tue, Dec 8, 2015 at 11:35 AM, Malaka Silva wrote: > Hi, > > One of the main issues we had when automating the integration use cases is > accesstokens getting expired and need human interaction to continue the > service. > > From

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

+1 for Nadeeshaan approach. @Thulasika we should give priority to checks like that if the api provide that functionality. On Sun, Dec 20, 2015 at 2:45 PM, Nadeeshaan Gunasinghe wrote: > Hi Thulshika, > > For google spreadsheet you can do something like this. > > There is

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

Hi Thulshika, For google spreadsheet you can do something like this. There is an api call to check whether the access token is valid or not. (" https://www.googleapis.com/oauth2/v1/tokeninfo?access_token=; + accessToken;). This would avoid getting the access token each time. Regards,

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

Hi, Since access token for Google Spreadsheet and Salesforce expires in 1 hour, we need to renew it after expiration time,But now we use getAccessTokenFromRefresToken method for every method call.To cater to this requirement I have added a new init method to save the access token in registry