Re: [Architecture] ESB connector smaple scenario - Integrate Salesforce SOAP with Google Spreadsheet and Gmail

[Manjula Rathnayake]

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.
5. Steps to extend this sample such as commit this sample to a git repo,
steps to build it and deploy in Cloud back.
6. Support channel to ask questions on this sample and motivate to
contribute back to our sample repo.
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.

thank you.

On Thu, Jul 27, 2017 at 1:20 PM, Malaka Silva  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 <
> haripras...@wso2.com> 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: haripras...@wso2.com
>> 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/
> 
> 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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] ESB connector smaple scenario - Integrate Salesforce SOAP with Google Spreadsheet and Gmail

[Malaka Silva]

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 <
haripras...@wso2.com> 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: haripras...@wso2.com
> 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
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/

https://store.wso2.com/store/

Don't make Trees rare, we should keep them with care
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] [VOTE] Release of WSO2 IoT Server 3.1.0 RC version 3

[Pubudu D.P]

-1 Due to the following bug in cipher tool[1]

[1] https://github.com/wso2/product-iots/issues/1245

Cheers,
Pubudu.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp


On Thu, Jul 27, 2017 at 9:38 AM, Madhawa Perera  wrote:

> Hi Devs,
>
> We are pleased to announce the release candidate version 3 of WSO2 IoT
> Server 3.1.0.
>
> Please download, test the product and vote. Vote will be open for 72 hours
> or as needed.
>
> Known issues : https://github.com/wso2/product-iots/issues?q=is%3Aopen+is%
> 3Aissue+label%3A3.1.0-RC1
>
> Source and binary distribution files:
> https://github.com/wso2/product-iots/releases/tag/v3.1.0-RC3
>
> The tag to be voted upon:
> https://github.com/wso2/product-iots/tree/v3.1.0-RC3
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thank you
> Best Regards,
> WSO2 IoT Team
>
> --
> Madhawa Perera
> *Software Engineer*
> Mobile : +94 (0) 773655496 <+94%2077%20365%205496>
> <%2B94%20%280%29%20773%20451194>
> madha...@wso2.com
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "WSO2 IoT Team Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to iot-group+unsubscr...@wso2.com.
> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] ESB connector smaple scenario - Integrate Salesforce SOAP with Google Spreadsheet and Gmail

[Manjula Rathnayake]

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 <
haripras...@wso2.com> wrote:

> Hi Manjula,
>
> On Thu, Jul 27, 2017 at 1:46 PM, Manjula Rathnayake 
> 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  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 <
>>> haripras...@wso2.com> 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: haripras...@wso2.com
 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/
>>> 
>>> 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: haripras...@wso2.com
> M: +94 75 2806528 

Re: [Architecture] ESB connector smaple scenario - Integrate Salesforce SOAP with Google Spreadsheet and Gmail

[Hariprasath Thanarajah]

Hi Manjula,

On Thu, Jul 27, 2017 at 1:46 PM, Manjula Rathnayake 
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  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 <
>> haripras...@wso2.com> 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: haripras...@wso2.com
>>> 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/
>> 
>> 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: haripras...@wso2.com
M: +94 75 2806528, +94 77 7216903
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/

http://ws.apache.org/ns/synapse;
   name="proxyWithGetEnv"
   startOnLoad="true"
   statistics="disable"
   trace="disable"
   transports="https,http">
   
  
 mc.setProperty("salesforcesoap.lead.firstname",java.lang.System.getenv("salesforcesoap_lead_firstname"));
			 mc.setProperty("salesforcesoap.lead.lastname",java.lang.System.getenv("salesforcesoap_lead_lastname"));
			 mc.setProperty("salesforcesoap.lead.email",java.lang.System.getenv("salesforcesoap_lead_email"));
			 

Re: [Architecture] ESB connector smaple scenario - Integrate Salesforce SOAP with Google Spreadsheet and Gmail

[Hariprasath Thanarajah]

Hi Manjula,

On Thu, Jul 27, 2017 at 7:30 PM, Manjula Rathnayake 
wrote:

> Hi Hariprasath,
>
> This is great. Have you tried deploying this sample in Integration Cloud?
>
Yes, I have tried this and got succeed. But one concern in the cloud is if
we need to add more than one environmental valiables then we need to add
those one by one. Is there any way to offer a text area to put all the key
and values in single add?

>
> 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.
>
So we can give them a step by step guide to create the same usecase using
dev studio and from that they can able to develop their usecases. Am I
right? If so I can add those details as well in the doc that shared with
this mail.

>
> thank you.
>
> On Thu, Jul 27, 2017 at 7:09 PM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi Manjula,
>>
>> On Thu, Jul 27, 2017 at 1:46 PM, Manjula Rathnayake 
>> 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  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 <
 haripras...@wso2.com> 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: haripras...@wso2.com
> 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 

Re: [Architecture] ESB connector smaple scenario - Integrate Salesforce SOAP with Google Spreadsheet and Gmail

[Manjula Rathnayake]

Hi Hariprasath,

On Thu, Jul 27, 2017 at 7:42 PM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:

> Hi Manjula,
>
> On Thu, Jul 27, 2017 at 7:30 PM, Manjula Rathnayake 
> wrote:
>
>> Hi Hariprasath,
>>
>> This is great. Have you tried deploying this sample in Integration Cloud?
>>
> Yes, I have tried this and got succeed. But one concern in the cloud is if
> we need to add more than one environmental valiables then we need to add
> those one by one. Is there any way to offer a text area to put all the key
> and values in single add?
>
Great. You can add all the environment variables into a json file and use
that file in environment variable adding section.


>
>> 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.
>>
> So we can give them a step by step guide to create the same usecase using
> dev studio and from that they can able to develop their usecases. Am I
> right? If so I can add those details as well in the doc that shared with
> this mail.
>
IMO, providing a high level steps would be sufficient pointing to the
existing documents.

thank you.


>
>> thank you.
>>
>> On Thu, Jul 27, 2017 at 7:09 PM, Hariprasath Thanarajah <
>> haripras...@wso2.com> wrote:
>>
>>> Hi Manjula,
>>>
>>> On Thu, Jul 27, 2017 at 1:46 PM, Manjula Rathnayake 
>>> 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  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 <
> haripras...@wso2.com> 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: haripras...@wso2.com
>> M: +94 75 2806528 <075%20280%206528>, +94 77 7216903
>> <077%20721%206903>
>> Blog: 

Re: [Architecture] Choosing APIs for implementing connectors

[kausik .M]

Hi all,

In this use cases we are planning :-

1.From the twitter connector we are getting retrieve searches  and also
from the CallRail connector we are Retrieving caller contact details then
from our *Followupboss* connector we are creating leads from those details.
And also from the *Followupboss* leads we are creating mail subscribers to
the Mailchimp account. For that we are using Mailchimp connector.

2. From our *Streak *connector we are creating boxes . From that boxes we
are creating projects in the *wealthbox CRM.*

3.From the liveChat connector we are getting the contacts from there and we
are creating them as a contacts in *amo CRM*. And also we are adding
companies in the *amo CRM* and we are getting the company names and from
that names we are adding them as a contacts to the Salesbinder.

4.For the event handling we are getting all the events from the
 *wealthbox CRM*
  *amo CRM*
 *Followupboss*
and we are adding those events scheduling in the buffer. Buffer will
schedule those events posts . And automatically buffer will post those
events in the social medias on the scheduling event day. We don't want to
post manually.

These are the use cases we have planned.

We are implementing these connectors.
*1.Followupboss *
*2.wealthbox CRM*
*3.**amo CRM*
*4.Streak*
*5.Buffer*

We are using these existing connectors for the use case. That connectors.
*1.Mailchimp*
*2.Twitter*
*3.Callrail*
*4.Salesbinder*
*5.Livechat*


Thank You
M.Kausik
Computer Science
University of Jaffna
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] ESB connector smaple scenario - Integrate Salesforce SOAP with Google Spreadsheet and Gmail

[Hariprasath Thanarajah]

Hi Manjula,

I have completed all the parts that are mentioned by you. Please have a
look and review it.

https://docs.google.com/a/wso2.com/document/d/1x9Jgcjt6cBG4_Vfd7110D1vNkaoXCpL_SlKBbwO8xIU/edit?usp=sharing

On Thu, Jul 27, 2017 at 7:50 PM, Manjula Rathnayake 
wrote:

> Hi Hariprasath,
>
> On Thu, Jul 27, 2017 at 7:42 PM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi Manjula,
>>
>> On Thu, Jul 27, 2017 at 7:30 PM, Manjula Rathnayake 
>> wrote:
>>
>>> Hi Hariprasath,
>>>
>>> This is great. Have you tried deploying this sample in Integration Cloud?
>>>
>> Yes, I have tried this and got succeed. But one concern in the cloud is
>> if we need to add more than one environmental valiables then we need to add
>> those one by one. Is there any way to offer a text area to put all the key
>> and values in single add?
>>
> Great. You can add all the environment variables into a json file and use
> that file in environment variable adding section.
>
>
>>
>>> 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.
>>>
>> So we can give them a step by step guide to create the same usecase using
>> dev studio and from that they can able to develop their usecases. Am I
>> right? If so I can add those details as well in the doc that shared with
>> this mail.
>>
> IMO, providing a high level steps would be sufficient pointing to the
> existing documents.
>
> thank you.
>
>
>>
>>> thank you.
>>>
>>> On Thu, Jul 27, 2017 at 7:09 PM, Hariprasath Thanarajah <
>>> haripras...@wso2.com> wrote:
>>>
 Hi Manjula,

 On Thu, Jul 27, 2017 at 1:46 PM, Manjula Rathnayake 
 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  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 <
>> haripras...@wso2.com> 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.

Re: [Architecture] ESB connector smaple scenario - Integrate Salesforce SOAP with Google Spreadsheet and Gmail

[Hariprasath Thanarajah]

Hi Malaka,

The source code means the artifacts? If so you can find it in[1]. But we
explain the steps to create the project in doc[2],

[1] - https://github.com/hariss63/sfSheetGmailUsecase

[2] -
https://docs.google.com/a/wso2.com/document/d/1x9Jgcjt6cBG4_Vfd7110D1vNkaoXCpL_SlKBbwO8xIU/edit?usp=sharing



On Fri, Jul 28, 2017 at 10:23 AM, Malaka Silva  wrote:

> Hi Hariprasath,
>
> Can you share the source code of integration use case?
>
> On Fri, Jul 28, 2017 at 1:33 AM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi Manjula,
>>
>> I have completed all the parts that are mentioned by you. Please have a
>> look and review it.
>>
>> https://docs.google.com/a/wso2.com/document/d/1x9Jgcjt6cBG4_
>> Vfd7110D1vNkaoXCpL_SlKBbwO8xIU/edit?usp=sharing
>>
>> On Thu, Jul 27, 2017 at 7:50 PM, Manjula Rathnayake 
>> wrote:
>>
>>> Hi Hariprasath,
>>>
>>> On Thu, Jul 27, 2017 at 7:42 PM, Hariprasath Thanarajah <
>>> haripras...@wso2.com> wrote:
>>>
 Hi Manjula,

 On Thu, Jul 27, 2017 at 7:30 PM, Manjula Rathnayake 
 wrote:

> Hi Hariprasath,
>
> This is great. Have you tried deploying this sample in Integration
> Cloud?
>
 Yes, I have tried this and got succeed. But one concern in the cloud is
 if we need to add more than one environmental valiables then we need to add
 those one by one. Is there any way to offer a text area to put all the key
 and values in single add?

>>> Great. You can add all the environment variables into a json file and
>>> use that file in environment variable adding section.
>>>
>>>

> 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.
>
 So we can give them a step by step guide to create the same usecase
 using dev studio and from that they can able to develop their usecases. Am
 I right? If so I can add those details as well in the doc that shared with
 this mail.

>>> IMO, providing a high level steps would be sufficient pointing to the
>>> existing documents.
>>>
>>> thank you.
>>>
>>>

> thank you.
>
> On Thu, Jul 27, 2017 at 7:09 PM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi Manjula,
>>
>> On Thu, Jul 27, 2017 at 1:46 PM, Manjula Rathnayake <
>> manju...@wso2.com> 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 
>>> 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 <
 haripras...@wso2.com> wrote:

> Hi All,
>
> I am working on to create a sample 

Re: [Architecture] [Dev] [VOTE] Release of WSO2 IoT Server 3.1.0 RC version 3

[Madhawa Perera]

Hi all,

We are closing the vote for RC version 3. We will proceed with new RC soon.

Thank you
Best Regards,
Madhawa


On Thu, Jul 27, 2017 at 3:59 PM, Pubudu D.P  wrote:

> -1 Due to the following bug in cipher tool[1]
>
> [1] https://github.com/wso2/product-iots/issues/1245
>
> Cheers,
> Pubudu.
>
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547 <+94%2077%20546%204547>
>
> Linkedin: https://uk.linkedin.com/in/pubududp
> Medium: https://medium.com/@pubududp
>
>
> On Thu, Jul 27, 2017 at 9:38 AM, Madhawa Perera  wrote:
>
>> Hi Devs,
>>
>> We are pleased to announce the release candidate version 3 of WSO2 IoT
>> Server 3.1.0.
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> Known issues : https://github.com/wso2/produc
>> t-iots/issues?q=is%3Aopen+is%3Aissue+label%3A3.1.0-RC1
>>
>> Source and binary distribution files:
>> https://github.com/wso2/product-iots/releases/tag/v3.1.0-RC3
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-iots/tree/v3.1.0-RC3
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thank you
>> Best Regards,
>> WSO2 IoT Team
>>
>> --
>> Madhawa Perera
>> *Software Engineer*
>> Mobile : +94 (0) 773655496 <+94%2077%20365%205496>
>> <%2B94%20%280%29%20773%20451194>
>> madha...@wso2.com
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "WSO2 IoT Team Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to iot-group+unsubscr...@wso2.com.
>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>
>
>


-- 
Madhawa Perera
*Software Engineer*
Mobile : +94 (0) 773655496
<%2B94%20%280%29%20773%20451194>
madha...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture