Hi Hariprasath, This is great. Have you tried deploying this sample in Integration Cloud?
Extending is usually needed. For example, every time we find a sample that just covers the part of the story we are interested in. It might not be the exact use case customers are looking for. If we share the source code too, they can edit some parts of it and try deploying back to the runtime and see how it works. This involves set of document links to guide the new users to get familiar with dev studio, connectors, and cloud. thank you. On Thu, Jul 27, 2017 at 7:09 PM, Hariprasath Thanarajah < [email protected]> wrote: > Hi Manjula, > > On Thu, Jul 27, 2017 at 1:46 PM, Manjula Rathnayake <[email protected]> > wrote: > >> Hi Hariprasath, >> >> Looks good. I can see below improvements so that we can make this sample >> personalized for anyone and get some customers around similar use cases. >> 1. Steps taken to configure Gmail, Salesforce and Google Sheets. This >> helps anyone to use their own account and configure. >> 2. Externalize credentials, URLs into environment variables. Then it is a >> matter of setting the correct values for those envs. >> 3. Document the steps to invoke and verify the results. >> 4. Steps to deploy this sample in Cloud and locally. >> > I have done this and you can find the documentation in[X] > >> 5. Steps to extend this sample such as commit this sample to a git repo, >> steps to build it and deploy in Cloud back. >> > Why do we need to extend this? Because we can set the needed values in the > environmetal variables and all the other parts are handled within the > proxy. I will attached the proxy as well to explain this scenario. > >> 6. Support channel to ask questions on this sample and motivate to >> contribute back to our sample repo. >> > +1 > >> 7. Health check for this sample to verify that individual connector APIs >> are not updated(otherwise after some time, this sample will not work and we >> will get to know only when customers report issues) >> >> If we can get above items done for this sample, then we can generalize it >> as a template and enforce for all samples. >> > [X] - https://docs.google.com/a/wso2.com/document/d/1x9Jgcjt6cBG4 > _Vfd7110D1vNkaoXCpL_SlKBbwO8xIU/edit?usp=sharing > >> >> >> thank you. >> >> On Thu, Jul 27, 2017 at 1:20 PM, Malaka Silva <[email protected]> wrote: >> >>> Hi Hariprasath, >>> >>> Looks good. I guess we have to think in a way this can be reused on >>> premise and in our integration cloud. >>> >>> On Thu, Jul 27, 2017 at 10:57 AM, Hariprasath Thanarajah < >>> [email protected]> wrote: >>> >>>> Hi All, >>>> >>>> I am working on to create a sample scenario with ESB connectors >>>> Salesforce SOAP, Google Spreadsheet and Gmail. For that, I used create >>>> method of Sf SOAP connector to create the Lead and from the response of >>>> that method we can able to get the Id of that record and using that Id we >>>> can able to retrieve the information about that Lead creation using >>>> retrieve method. After that, we need to insert the needed information of >>>> that record to a spreadsheet using Google Spreadsheet connector using >>>> addRowsData method and from getCellData method, we can able to retrieve the >>>> information about the record. And finally, we can build the message >>>> body with the above information and send an alert to the manager about the >>>> Lead creation using Gmail Connector. >>>> >>>> Please find the above use case explanation in [1] and sample proxy can >>>> be found in the attached file. >>>> >>>> [1] - >>>> [image: Inline image 1] >>>> >>>> -- >>>> >>>> >>>> *Thank you and Regards,**Hariprasath Thanarajah* >>>> Software Engineer | WSO2 >>>> E: [email protected] >>>> M: +94 75 2806528 <075%20280%206528>, +94 77 7216903 <077%20721%206903> >>>> Blog: hariwso2.blogspot.com >>>> >>>> Skype : hariss636 >>>> LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 >>>> >>>> WSO2, Inc. >>>> lean . enterprise . middleware >>>> >>>> https://wso2.com/signature >>>> http://wso2.com/about/team/hariprashath-thanarajah/ >>>> >>> >>> >>> >>> -- >>> >>> Best Regards, >>> >>> Malaka Silva >>> Associate Director / Architect >>> M: +94 777 219 791 <+94%2077%20721%209791> >>> Tel : 94 11 214 5345 >>> Fax :94 11 2145300 >>> Skype : malaka.sampath.silva >>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>> Blog : http://mrmalakasilva.blogspot.com/ >>> >>> WSO2, Inc. >>> lean . enterprise . middleware >>> https://wso2.com/signature >>> http://www.wso2.com/about/team/malaka-silva/ >>> <http://wso2.com/about/team/malaka-silva/> >>> https://store.wso2.com/store/ >>> >>> Don't make Trees rare, we should keep them with care >>> >> >> >> >> -- >> Manjula Rathnayaka >> Technical Lead >> WSO2, Inc. >> Mobile:+94 77 743 1987 <+94%2077%20743%201987> >> > > > > -- > > > *Thank you and Regards,**Hariprasath Thanarajah* > Software Engineer | WSO2 > E: [email protected] > M: +94 75 2806528 <+94%2075%20280%206528>, +94 77 7216903 > <+94%2077%20721%206903> > Blog: hariwso2.blogspot.com > > Skype : hariss636 > LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660 > > WSO2, Inc. > lean . enterprise . middleware > > https://wso2.com/signature > http://wso2.com/about/team/hariprashath-thanarajah/ > -- Manjula Rathnayaka Technical Lead WSO2, Inc. Mobile:+94 77 743 1987 <+94%2077%20743%201987>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
