Re: [Architecture] Integration Solutions - Salesforce to Netsuite account sync
Hi, We have streaming solution to handle such use cases. Currently there are similar solutions in our road map. On Thu, Oct 26, 2017 at 4:30 PM, Kesavan Yogarajah <kesav...@wso2.com> wrote: > Hi Sajith, > > This scenario only syncs newly added accounts. We can include the > update part also. But for the initial versions, we focus on simple export > solutions as we did in [1]. So the end users can simply try these solutions > without much configuration changes or be tuning the platforms. > We will consider increasing the complexity of the solutions in future. > > Thanks > Kesavan > > [1] - https://docs.wso2.com/display/IntegrationCloud/Integration+Solutions > > Kesavan Yogarajah > Software Engineer > Mobile :+94 (0) 779 758021 <077%20975%208021> > kesav...@wso2.com > WSO2, Inc. > lean . enterprise . middleware > > On Thu, Oct 26, 2017 at 11:16 AM, Sajith Kariyawasam <saj...@wso2.com> > wrote: > >> Hi Kesavan, >> >> Does this sync newly added acounts only? What if a user account details >> in Salesforce gets updated? Shouldn't those be reflected in Netsuite? >> >> On Wed, Oct 25, 2017 at 6:44 PM, Kesavan Yogarajah <kesav...@wso2.com> >> wrote: >> >>> Hi All, >>> >>> We are planning to implement the following use case using Salesforce >>> SOAP and Netsuite connectors. Here, newly created accounts will be >>> periodically retrieved and added as customers in Netsuite. >>> >>> >>> >>> Operations: >>> Salesforce - Query >>> Netsuite - addList >>> >>> Please let us know if you have any concerns. >>> >>> Thanks >>> >>> Kesavan Yogarajah >>> Software Engineer >>> Mobile :+94 (0) 779 758021 <+94%2077%20975%208021> >>> kesav...@wso2.com >>> WSO2, Inc. >>> lean . enterprise . middleware >>> >>> ___ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Sajith Kariyawasam >> *Associate Tech Lead* >> *WSO2 Inc.; http://wso2.com <http://wso2.com/>* >> *Committer and PMC member, Apache Stratos * >> *AMIE (SL)* >> *Mobile: 0772269575 <077%20226%209575>* >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > _______ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- 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/ <http://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] Fix the Facebook Connector
Hi Janani, We need to release this today. On Mon, Oct 23, 2017 at 11:20 AM, Janani Thangavel <jan...@wso2.com> wrote: > Hi All, > > I ran the integration test for Facebook connector with EI(6.1.1). Some > integration test cases are failed, because of the API changes, new > mandatory and optional parameters are added in the methods, the credentials > are changed to access the method and responses of the methods are changed. > > I'm Planing to fix these methods by this Wednesday. > >- CreateComment >- UpdateComment >- DeleteComment >- CreateLike >- DeleteLike >- GetVideoDetails(Mandatory) >- PublishNotification >- CreateAppAchievements >- DeleteAppAchievements >- CreateUserAchievement >- CreateAppSubscription >- DeleteAppSubscription >- GetPageDetails(Mandatory) >- GetAppDetails >- BanAppUser >- BlockUserFromPage >- UnblockUserFromPage >- UpdatePageDetails >- UpdateAppDetails >- GetPageMilestoneDetails >- GetFriendListDetails >- AddPhotoToPage >- UpdatePagePicture >- AddPageVideo > > > Regards, > > Janani Thangavel > Associate Software Engineer > WSO2 Inc : http://wso2.org > <http://www.google.com/url?q=http%3A%2F%2Fwso2.org=D=1=AFQjCNE_eTDfyl2ibPcq0hcXvRDNVuQmMg> > Mobile : +94771856427 <077%20185%206427> > -- 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/ <http://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] Workday Connector
Hi Nirthika, Have we completed method implementations? Why integration tests are taking time? Please plan to complete this tomorrow. We need to release the connector this week. On Mon, Oct 23, 2017 at 8:28 PM, Nirthika Rajendran <nirth...@wso2.com> wrote: > Hi All, > > Please find the milestone plan[1] for workday connector. > > [1] https://docs.google.com/spreadsheets/d/1BJFUPuL-_JH_ > sqlpEstPfYHZ5ps9LbfhH7m4rT-dvSo/edit#gid=0 > > Regards, > *Nirthika Rajendran* > *Associate Software Engineer* > WSO2 Inc : http://wso2.org > Mobile : +94 77 719 8368 <077%20719%208368> > LinkedIn: https://www.linkedin.com/in/nirthika/ > Blog : > *http://nirthika-tech-stuff.blogspot.com/ > <http://nirthika-tech-stuff.blogspot.com/>* > > On Tue, Oct 17, 2017 at 6:16 PM, Nirthika Rajendran <nirth...@wso2.com> > wrote: > >> Hi All, >> >> I have implemented the "Get_Workers" operation. It's works fine. >> And I will continue the rest of the operation in the workday. >> >> Regards, >> *Nirthika Rajendran* >> *Associate Software Engineer* >> WSO2 Inc : http://wso2.org >> Mobile : +94 77 719 8368 <+94%2077%20719%208368> >> LinkedIn: https://www.linkedin.com/in/nirthika/ >> Blog : >> *http://nirthika-tech-stuff.blogspot.com/ >> <http://nirthika-tech-stuff.blogspot.com/>* >> >> On Wed, Oct 11, 2017 at 2:10 PM, Rajjaz Mohammed <raj...@wso2.com> wrote: >> >>> Hi Nirthika, >>> >>> This list[1] may help you to chose the methods. >>> >>> [1] https://docs.mulesoft.com/release-notes/workday-connector-re >>> lease-notes >>> >>> On Wed, Oct 11, 2017 at 2:02 PM, Nirthika Rajendran <nirth...@wso2.com> >>> wrote: >>> >>>> Hi Malaka, >>>> >>>> There are nearly 250 operations in total for Human_Resource [1] and >>>> Payroll [2] >>>> >>>> [1] https://community.workday.com/sites/default/files/file-h >>>> osting/productionapi/Human_Resources/v29.0/Human_Resources.html >>>> [2] https://community.workday.com/sites/default/files/file-h >>>> osting/productionapi/Payroll/v29.0/Payroll.html >>>> >>>> So we plan to do 10 methods totally for the first version. >>>> >>>> *Human_Resource* >>>> 1.Get_Workers >>>> 2.Get_Committee_Definition >>>> 3.Get_Committee_Types >>>> 4.Manage_Committee_Membership >>>> 5.Put_Committee_Classification >>>> >>>> *Payroll* >>>> 6.Get_Payroll_Balances >>>> 7.Get_Period_Schedules >>>> 8.Get_Payroll_Results >>>> 9.Get_Paycheck_Deliveries >>>> 10.Put_Paycheck_Delivery_Public >>>> >>>> Regards, >>>> >>>> *Nirthika Rajendran* >>>> *Associate Software Engineer* >>>> WSO2 Inc : http://wso2.org >>>> Mobile : +94 77 719 8368 <+94%2077%20719%208368> >>>> LinkedIn: https://www.linkedin.com/in/nirthika/ >>>> Blog : http://nirthi-tech-stuff.blogspot.com/ >>>> >>>> On Wed, Oct 11, 2017 at 1:32 PM, Malaka Silva <mal...@wso2.com> wrote: >>>> >>>>> Can you share the operations we are planning to cover? >>>>> >>>>> On Wed, Oct 11, 2017 at 11:30 AM, Nirthika Rajendran < >>>>> nirth...@wso2.com> wrote: >>>>> >>>>>> Hi Malaka, >>>>>> >>>>>> Yes we will cover section(s) fully with the first version. >>>>>> >>>>>> Regards, >>>>>> >>>>>> *Nirthika Rajendran* >>>>>> *Associate Software Engineer* >>>>>> WSO2 Inc : http://wso2.org >>>>>> Mobile : +94 77 719 8368 <077%20719%208368> >>>>>> LinkedIn: https://www.linkedin.com/in/nirthika/ >>>>>> Blog : http://nirthi-tech-stuff.blogspot.com/ >>>>>> >>>>>> On Wed, Oct 11, 2017 at 10:40 AM, Malaka Silva <mal...@wso2.com> >>>>>> wrote: >>>>>> >>>>>>> Hi Nirthika, >>>>>>> >>>>>>> Shall we plan to cover section(s) fully with the first version. >>>>>>> >>>>>>> Eg: All operations in Human_Resources and Payroll. >>>>>>> >>>>>>> Otherwise it'll be diffic
Re: [Architecture] Milestone Plan for Redis Connector
No this task was not completed and published to the store. On Tue, Oct 17, 2017 at 2:58 PM, KasunG Gajasinghe <kas...@wso2.com> wrote: > Have we written this connector? I can't seem to find it in the Store [1]. > > [1] https://store.wso2.com/store/pages/top-assets?q=%22_ > default%22%3A%22redis%22 > > Thanks. > > On Wed, Apr 15, 2015 at 4:00 PM, Vanjikumaran Sivajothy <va...@wso2.com> > wrote: > >> You have to forward this apim-> Esb >> >> >> On Wednesday, April 15, 2015, ly h <liuh...@gmail.com> wrote: >> >>> Can we use it as axis transport in apim, or we must forward data from >>> apim to esb. >>> >>> 2015-04-15 10:39 GMT+08:00 Vanjikumaran Sivajothy <va...@wso2.com>: >>> >>>> Hi liuhf, >>>> Yes it is possible, you have to make sure that you have utilized this >>>> connector in proxy web services of Wso2 ESB and expose that via api manager >>>> as you want >>>> >>>> >>>> On Monday, April 13, 2015, ly h <liuh...@gmail.com> wrote: >>>> >>>>> If this finished, can we use it in APIManager? We want http<->redis. >>>>> >>>>> Best regards! >>>>> >>>>> liuhf >>>>> >>>>> 2015-04-10 18:18 GMT+08:00 Naasheer Ali <naashe...@wso2.com>: >>>>> >>>>>> Hi All, >>>>>> I'm gonna implement the Redis connector for WSO2 ESB. >>>>>> 1. Overview >>>>>> >>>>>>- Redis is an open source, BSD licensed, avanced* key-value cache >>>>>>*and* store. *It is often referred to as a* data structure server >>>>>>*since keys can contain *Strings, hashes, lists, sets, sorted >>>>>>sets bitmaps* and *hyperloglogs.* >>>>>> >>>>>> 2. Advantages of Redis >>>>>> >>>>>>- Redis can contain more complex data types, with atomic >>>>>>operation defined on those data types. >>>>>>- Redis data types are closely related to fundamental data >>>>>>structure and are exposed to the programmer as such, without >>>>>> additional >>>>>>abstraction layers. >>>>>>- Redis is an in-memory but persistent on disk database, so it >>>>>>represents a different trade off where very high write and read speed >>>>>> is >>>>>>achieved with the limitation of data sets that can't be lager than >>>>>> memory. >>>>>>- The memory representation of complex data structures is much >>>>>>simpler to manipulate compared to the same data structure on disk, so >>>>>> Redis >>>>>>can do a lot, with little internal complexity. >>>>>> >>>>>> 3. Use Cases : >>>>>> >>>>>>- Queuing slow operations >>>>>>- cross-language develoment, >>>>>>- atomic counters and generating sequences >>>>>>- dealing with temporary data in your application >>>>>>- Redis as a cache >>>>>> >>>>>> >>>>>> Please find my milestone plan. >>>>>> >>>>>> Regards, >>>>>> -- >>>>>> >>>>>> *Naasheer Ali* | Associate Software Engineer >>>>>> >>>>>> WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka >>>>>> >>>>>> Email: naashe...@wso2.comr >>>>>> >>>>>> _______ >>>>>> Architecture mailing list >>>>>> Architecture@wso2.org >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>> >>>> -- >>>> Sent from Gmail Mobile >>>> >>>> ___ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >> >> -- >> Sent from Gmail Mobile >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc. > email: kasung AT spamfree wso2.com > linked-in: http://lk.linkedin.com/in/gajasinghe > blog: http://kasunbg.org > phone: +1 650-745-4499 <+1%20650-745-4499>, 77 678 0813 > > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- 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/ <http://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] Workday Connector
Can you share the operations we are planning to cover? On Wed, Oct 11, 2017 at 11:30 AM, Nirthika Rajendran <nirth...@wso2.com> wrote: > Hi Malaka, > > Yes we will cover section(s) fully with the first version. > > Regards, > > *Nirthika Rajendran* > *Associate Software Engineer* > WSO2 Inc : http://wso2.org > Mobile : +94 77 719 8368 <077%20719%208368> > LinkedIn: https://www.linkedin.com/in/nirthika/ > Blog : http://nirthi-tech-stuff.blogspot.com/ > > On Wed, Oct 11, 2017 at 10:40 AM, Malaka Silva <mal...@wso2.com> wrote: > >> Hi Nirthika, >> >> Shall we plan to cover section(s) fully with the first version. >> >> Eg: All operations in Human_Resources and Payroll. >> >> Otherwise it'll be difficult to implement a use case. >> >> On Wed, Oct 11, 2017 at 10:13 AM, Nirthika Rajendran <nirth...@wso2.com> >> wrote: >> >>> Hi All, >>> >>> We have planned to implement workday connector for EI by referring the >>> workday API documentation [1] version v29.0. >>> >>> Workday is a Software-as-a-Service (SaaS) solution developed by Workday >>> Inc., comprising a set of management applications, covering several areas >>> like human resources management, payroll, recruiting and talent. >>> >>> Now planning to cover the following Methods [2] for initial version. >>> >>> [1] https://community.workday.com/sites/default/files/file-hosti >>> ng/productionapi/versions/v29.0/index.html >>> >>> [2] >>> *Services* *Operations* >>> Human_Resources Get_Workers >>> Put_Committee_Type >>> >>> Payroll Get_Paycheck_Deliveries >>> Put_Paycheck_Delivery_Public >>> >>> Recruiting Get_Candidates >>> Put_Candidate >>> >>> Talent Get_Competency_Classes >>> Put_Competency_Class >>> >>> Please let me know if you have any suggestions on this? >>> >>> Regards, >>> *Nirthika Rajendran* >>> *Associate Software Engineer* >>> WSO2 Inc : http://wso2.org >>> Mobile : +94 77 719 8368 <077%20719%208368> >>> LinkedIn: https://www.linkedin.com/in/nirthika/ >>> Blog : http://nirthi-tech-stuff.blogspot.com/ >>> >> >> >> >> -- >> >> 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 <011%202%20145300> >> 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 >> > > -- 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/ <http://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] Workday Connector
Hi Nirthika, Shall we plan to cover section(s) fully with the first version. Eg: All operations in Human_Resources and Payroll. Otherwise it'll be difficult to implement a use case. On Wed, Oct 11, 2017 at 10:13 AM, Nirthika Rajendran <nirth...@wso2.com> wrote: > Hi All, > > We have planned to implement workday connector for EI by referring the > workday API documentation [1] version v29.0. > > Workday is a Software-as-a-Service (SaaS) solution developed by Workday > Inc., comprising a set of management applications, covering several areas > like human resources management, payroll, recruiting and talent. > > Now planning to cover the following Methods [2] for initial version. > > [1] https://community.workday.com/sites/default/files/file- > hosting/productionapi/versions/v29.0/index.html > > [2] > *Services* *Operations* > Human_Resources Get_Workers > Put_Committee_Type > > Payroll Get_Paycheck_Deliveries > Put_Paycheck_Delivery_Public > > Recruiting Get_Candidates > Put_Candidate > > Talent Get_Competency_Classes > Put_Competency_Class > > Please let me know if you have any suggestions on this? > > Regards, > *Nirthika Rajendran* > *Associate Software Engineer* > WSO2 Inc : http://wso2.org > Mobile : +94 77 719 8368 <077%20719%208368> > LinkedIn: https://www.linkedin.com/in/nirthika/ > Blog : http://nirthi-tech-stuff.blogspot.com/ > -- 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/ <http://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] [PET] Improving File Connector
On Thu, Sep 21, 2017 at 7:51 PM, Keerthika Mahendralingam < keerth...@wso2.com> wrote: > Hi All, > > Currently, I'm working on improving the file connector with the following > functionalities. > >- Read a specific line from a file >- Read range of lines >- Get last modified time of a file > > Since we are using common-vfs can we do this for all file systems? > >- Get the size of a file >- Append line/data to a file to a specific line >- Split the file into chunks > > What is the logic to do this? > >- Merge the chunks into a file > > Please let me know if you have any concerns. > > > Thanks, > -- > <dev-requ...@wso2.org> > Keerthika Mahendralingam > Software Engineer > Mobile :+94 (0) 776 121144 <077%20612%201144> > keerth...@wso2.com > WSO2, Inc. > lean . enterprise . middleware > -- 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/ <http://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] DB event listener for ESB
Hi Shakila, For use case 1 and 2 better to take the column name from a parameter rather than hard coding the column names. On Tue, Aug 15, 2017 at 11:51 AM, Shakila Sasikaran <shak...@wso2.com> wrote: > Hi all, > > Please find the use-cases that we are going to support with the DB event > listener. Appreciate your comments on this. > > 1. Take record based on timestamp. Have a field in records called > 'lastmodifieddatetime' and based on that take records in each polling > cycle: This is supported by the current implementation. > 2. Have a boolean column 'isChanged' in the record and by default, it will > be 'true'. Each polling cycle takes only records with 'true' value and > updates as 'false' once it is polled. > 3. Give an option to delete the record after polling it. We can have a > boolean type parameter 'deleteAfterRead' and if it is set to true, it will > delete the record after polling it. > > Thanks > > On Sat, Aug 12, 2017 at 6:36 AM, Malaka Silva <mal...@wso2.com> wrote: > >> Hi All, >> >> We have identified users still need a solution from integration layer. We >> are planning to continue a generic solution for this. >> >> On Tue, Sep 6, 2016 at 11:12 AM, Anjana Fernando <anj...@wso2.com> wrote: >> >>> Hi, >>> >>> If we say, we monitor one table, that means, we can simply say, give the >>> table name to be monitored in the inbound endpoint. And probably we have to >>> give the logic as to what warrants a change in the database, is it a row >>> value change, a new row being added etc.. and doing complex operations can >>> be very tricky as the database grows, and not to mention expressing on what >>> exactly to do to figure out a change in the database. So I'm just thinking >>> if we can do this in an efficient way at all, and how useful it would be at >>> the end. For example, even running a SELECT COUNT (*) can be an expensive >>> operation in a large table. So, by any chance, if the database server >>> doesn't give any native trigger functionality, I can see an user just >>> writing his custom extension to poll a database and run his custom logic to >>> figure out changes. >>> >>> Cheers, >>> Anjana. >>> >>> On Wed, Aug 31, 2016 at 12:00 PM, Srinath Perera <srin...@wso2.com> >>> wrote: >>> >>>> +1 .. we can say that we only monitor one table and recommend to setup >>>> triggers if they need to detect lot of conditions. >>>> >>>> On Wed, Aug 31, 2016 at 3:12 AM, Chamila De Alwis <chami...@wso2.com> >>>> wrote: >>>> >>>>> One hybrid solution would be to have db triggers adding records to a >>>>> single "monitor" table in which a polling inbound endpoint can >>>>> periodically >>>>> look check for changes [1]. Based on the new records, the consequent >>>>> sequence can decide which actions to execute. >>>>> >>>>> [1] - http://stackoverflow.com/questions/6153330/can-a-sql-trigger >>>>> -call-a-web-service >>>>> >>>>> Regards, >>>>> Chamila de Alwis >>>>> Committer and PMC Member - Apache Stratos >>>>> Senior Software Engineer | WSO2 >>>>> Blog: https://medium.com/@chamilad >>>>> >>>>> >>>>> >>>>> On Tue, Aug 30, 2016 at 4:52 AM, Srinath Perera <srin...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi Malaka, >>>>>> >>>>>> If it is done using triggers, it can be done without us doing >>>>>> anything. I assume trigger can hit a URL in the ESB that trigger >>>>>> processing. >>>>>> >>>>>> Adding a DB listener as an inbound endpoint is OK. >>>>>> >>>>>> I suggest we only do DB listener. >>>>>> >>>>>> --Srinath >>>>>> >>>>>> On Tue, Aug 30, 2016 at 3:13 PM, Malaka Silva <mal...@wso2.com> >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> There are requirements to do additional operations when there are >>>>>>> changes done to organization data. >>>>>>> >>>>>>> One way to do this is to create triggers at database level. However >>>>>>> there are limitations on actions users can perform using t
Re: [Architecture] DB event listener for ESB
Hi All, We have identified users still need a solution from integration layer. We are planning to continue a generic solution for this. On Tue, Sep 6, 2016 at 11:12 AM, Anjana Fernando <anj...@wso2.com> wrote: > Hi, > > If we say, we monitor one table, that means, we can simply say, give the > table name to be monitored in the inbound endpoint. And probably we have to > give the logic as to what warrants a change in the database, is it a row > value change, a new row being added etc.. and doing complex operations can > be very tricky as the database grows, and not to mention expressing on what > exactly to do to figure out a change in the database. So I'm just thinking > if we can do this in an efficient way at all, and how useful it would be at > the end. For example, even running a SELECT COUNT (*) can be an expensive > operation in a large table. So, by any chance, if the database server > doesn't give any native trigger functionality, I can see an user just > writing his custom extension to poll a database and run his custom logic to > figure out changes. > > Cheers, > Anjana. > > On Wed, Aug 31, 2016 at 12:00 PM, Srinath Perera <srin...@wso2.com> wrote: > >> +1 .. we can say that we only monitor one table and recommend to setup >> triggers if they need to detect lot of conditions. >> >> On Wed, Aug 31, 2016 at 3:12 AM, Chamila De Alwis <chami...@wso2.com> >> wrote: >> >>> One hybrid solution would be to have db triggers adding records to a >>> single "monitor" table in which a polling inbound endpoint can periodically >>> look check for changes [1]. Based on the new records, the consequent >>> sequence can decide which actions to execute. >>> >>> [1] - http://stackoverflow.com/questions/6153330/can-a-sql-trigger >>> -call-a-web-service >>> >>> Regards, >>> Chamila de Alwis >>> Committer and PMC Member - Apache Stratos >>> Senior Software Engineer | WSO2 >>> Blog: https://medium.com/@chamilad >>> >>> >>> >>> On Tue, Aug 30, 2016 at 4:52 AM, Srinath Perera <srin...@wso2.com> >>> wrote: >>> >>>> Hi Malaka, >>>> >>>> If it is done using triggers, it can be done without us doing anything. >>>> I assume trigger can hit a URL in the ESB that trigger processing. >>>> >>>> Adding a DB listener as an inbound endpoint is OK. >>>> >>>> I suggest we only do DB listener. >>>> >>>> --Srinath >>>> >>>> On Tue, Aug 30, 2016 at 3:13 PM, Malaka Silva <mal...@wso2.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> There are requirements to do additional operations when there are >>>>> changes done to organization data. >>>>> >>>>> One way to do this is to create triggers at database level. However >>>>> there are limitations on actions users can perform using triggers. >>>>> >>>>> So if we implement custom inbound endpoint we can cover most of the >>>>> use cases. >>>>> [image: Inline image 1] >>>>> >>>>> >>>>> >>>>> There are several ways to do that. But we already know using JDBC is >>>>> impossible at the moment. One way to achieve this is implementing a >>>>> polling >>>>> inbound to monitor the changes in the database object (such as a table in >>>>> the database). If any change occurred, that inbound can invoke a sequence. >>>>> But this is not a good practice. What if your database has more than ten >>>>> tables? Then users have to create ten threads for each table and that >>>>> would >>>>> be a great mess regarding to the performance. >>>>> >>>>> There are also vendor specific solutions provided. [1] [2] >>>>> >>>>> JPA also provide this capability [3] However with this users need to >>>>> create entities for there environment and using those with ESB is complex. >>>>> >>>>> Using Hibernate we can do the same and maintain the configuration in >>>>> XML. >>>>> >>>>> Thoughts about this inbound are welcome? >>>>> >>>>> [1] http://stackoverflow.com/questions/12618915/how-to-imple >>>>> ment-a-db-listener-in-java >>>>> [2] http://www.ibm.com/support/knowledgecenter/SSSHYH_5.1.1/ >>>>> com.ibm.netco
Re: [Architecture] ESB connector smaple scenario - Integrate Salesforce SOAP with Google Spreadsheet and Gmail
Hi Hariprasath, Yes synapse configs. Ideally users should be able to run standard use case with this. If they want to extend can customize the integration flow. On Fri, Jul 28, 2017 at 10:55 AM, Hariprasath Thanarajah < haripras...@wso2.com> wrote: > 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 <mal...@wso2.com> 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 <manju...@wso2.com> >>> 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 <manju...@wso2.com >>>>> > 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. >>>>>>>&g
Re: [Architecture] Choosing APIs for implementing connectors
Hi Kausik, Thx for the explanation. Looks good. On Fri, Jul 28, 2017 at 12:05 AM, kausik .M <kausik...@gmail.com> wrote: > 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 > -- 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/ <http://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] ESB connector smaple scenario - Integrate Salesforce SOAP with Google Spreadsheet and Gmail
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/ <http://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] How valid is sending TOTP code to email? How about sending it over SMS?
Another point is only few have snmp gateways. Most of the time users stick to SMS providers (via rest api) to send SMS. On Sat, Jul 22, 2017 at 10:30 PM, Dinesh J Weerakkody <dine...@wso2.com> wrote: > I also think having both options is better than sticking to one. > > There are two reasons for that, > First, SMS is not guaranteed to deliver in seconds, and might get delayed. > Second, we use mobile apps to access emails and it's just a matter of > opening the app which is already logged in the mail box. Plus can access > from anywhere as long as internet is there. > -- 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/ <http://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] Using Nashorn JavaScript engine in Script Mediator
+1 to introduce a new mediator due to following. Most of the current connectors are using script mediator. Also how sure we are the Nashorn based script mediator can handle all the use cases we used the handle? On Wed, Jul 19, 2017 at 8:29 PM, Isuru Udana <isu...@wso2.com> wrote: > Hi, > > If we cannot get Nashorn to work with E4X or E4X style syntax, we > shouldn't simply change the JS engine to Nashorn in current Script > Mediator. We need to make sure our releases are backward compatible. > So in that case we need to introduce a new mediator. > > Thanks. > > > > On Wed, Jul 19, 2017 at 7:39 PM, Harshana Eranga Martin < > harshan...@gmail.com> wrote: > >> Hi Malaka, >> >> If you drop the support for E4X when moving to Nashorn, what happens to >> the customers who want to migrate their artefacts from an old ESB version >> (say 4.8.1) to the new version? >> >> Re-writting the entire JS artefacts will not be a possibility for many. >> So you need to have a serious think about how to provide a safe and pain >> free migration path for old E4X based code to the new engine. >> >> Thanks and Regards, >> Harshana >> -- >> Harshana Eranga Martin >> >> Committer - Eclipse ECF: http://www.eclipse.org/ecf/ >> Blog: http://harshana05.blogspot.com >> Profile: https://www.google.com/profiles/harshana05 >> >> On 19 July 2017 at 21:14, Malaka Gangananda <mala...@wso2.com> wrote: >> >>> Hi All, >>> >>> Current script mediator use Rhino as its JavaScript engine and we are in >>> the process of upgrading the script mediator to use new Nashorn engine. So >>> we will be providing the capability of using Rhino as javascript engine for >>> java 7 users and Nashorn for java 8 users in script mediator. But in the >>> process we have found some issues and solved them. Such as when trying to >>> set Json payload the existing Rhino engine will use its native objects to >>> pass Json payload so in existing script mediator it use different >>> serialization techniques for each Rhino native object type. But in Nashorn >>> the passed object will be always ScriptObjectMirror type. We have overcome >>> this issue by serializing these objects using serialization functionality >>> of Nashorn native "JSON" object. So when handling the Json payloads the >>> used engine will not be an issue. But the main issue was usage of E4X xml >>> objects when handling xml payloads with Rhino engine. Because as stated >>> in[1] E4X is deprecated and it does not supported by Nashorn engine. To >>> overcome this when using Nashorn, DOMparser can be used to parse xml >>> strings rather than using xml objects. But then the users who are using >>> script mediator with new Nashorn engine will not be able to use xml objects >>> in javascript but they will be able to use setPayloadXML and getPayloadXML >>> methods in script mediator by using string representations of xml. So the >>> decision we need to make is whether to use existing mediator with Nashorn >>> engine support but without using E4X(which is deprecated but still using >>> Rhino engine it will be supported) or writing new mediator separately for >>> javascript with Nashorn engine support. >>> >>> >>> [1] https://developer.mozilla.org/en-US/docs/Archive/Web/E4X/Pro >>> cessing_XML_with_E4X >>> >>> Thanks, >>> -- >>> Malaka. >>> -- >>> Malaka Gangananda - Software Engineer | WSO2 >>> Email : mala...@wso2.com >>> Mobile : +94713564340 <+94%2071%20356%204340> >>> Web : http://wso2.com >>> <http://wso2.com/signature> >>> >>> ___ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Isuru Udana* > Senior Technical Lead > WSO2 Inc.; http://wso2.com > email: isu...@wso2.com cell: +94 77 3791887 <077%20379%201887> > blog: http://mytecheye.blogspot.com/ > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- 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/ <http://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] Improving Enrich Mediator
Hi Nirthika, Find my comments inline. On Wed, Jul 19, 2017 at 5:36 PM, Nirthika Rajendran <nirth...@wso2.com> wrote: > Hi All, > > I am working on the Jira improvement [1]. The earlier discussion on this > can see on the mail thread [2] and [3]. > > As mentioned in the mail thread [2] if we remove the attributes "type" and > "property" and support both via Xpath only, then should it support for > backward compatibility? > Guess so. Otherwise existing integration can break. We can properly document the recommended way to use it once this is completed. > > Please give some suggestions. > > [1] https://wso2.org/jira/browse/ESBJAVA-3688 > [2] http://mail.wso2.org/mailarchive/architecture/2015-May/020110.html > [3] http://mail.wso2.org/mailarchive/architecture/2015-May/020075.html > > > Thanks. > Regards, > *Nirthika Rajendran* > *Associate Software Engineer* > WSO2 Inc : http://wso2.org > Mobile : +94 77 719 8368 <077%20719%208368> > LinkedIn: https://www.linkedin.com/in/nirthika/ > Blog : http://nirthi-tech-stuff.blogspot.com/ > -- 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/ <http://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] AS4 support in EI
sending MSH. >>>> >>>> *Message Consumer*: The business application which receives the >>>> message content from receiving MSH. >>>> >>>> *P-Mode Parameters*: Message sending and receiving operations are >>>> governed by P-Mode configuration. These are configured in sending and >>>> receiving MSHs. >>>> >>>> >>>> >>>> >>>> The current implementation details of AS4 custom mediator[2] is as >>>> follows. >>>> >>>>- This is in conformance with AS4 Profile of ebMS 3.0 Version >>>>1.0[1]. >>>>- The current AS4 implementation only supports features as stated >>>>in the Access Point Implementation Guide (attached). >>>>- One-way / Push Message Exchange Patterns (MEPs) is supported. >>>>- Only the *required* P-Mode Parameters are supported (According to >>>>[1]). >>>> >>>> >>>> *Supported P-Mode Parameters* >>>> >>>> >>>> PMode Parameter >>>> >>>> Supported or not >>>> >>>> PMode.ID >>>> >>>> true >>>> >>>> PMode.Agreement >>>> >>>> true >>>> >>>> PMode.MEP >>>> >>>> true >>>> >>>> PMode.MEPbinding >>>> >>>> true >>>> >>>> PMode.Initiator.Party >>>> >>>> true >>>> >>>> PMode.Initiator.Role >>>> >>>> true >>>> >>>> PMode.Initiator.Authorization.username >>>> >>>> false >>>> >>>> PMode.Initiator.Authorization.password >>>> >>>> false >>>> >>>> PMode.Responder.Party >>>> >>>> true >>>> >>>> PMode.Responder.Role >>>> >>>> true >>>> >>>> PMode.Responder.Authorization.username >>>> >>>> false >>>> >>>> PMode.Responder.Authorization.password >>>> >>>> false >>>> >>>> PMode.Protocol.Address >>>> >>>> true >>>> >>>> PMode.Protocol.SOAPVersion >>>> >>>> true >>>> >>>> PMode.BusinessInfo.Service >>>> >>>> true >>>> >>>> PMode.BusinessInfo.Action >>>> >>>> true >>>> >>>> PMode.BusinessInfo.Properties[] >>>> >>>> false >>>> >>>> PMode.BusinessInfo.PayloadProfile[] >>>> >>>> false >>>> >>>> PMode.BusinessInfo.PayloadProfile.maxSize >>>> >>>> false >>>> >>>> PMode.ErrorHandling.Report.SenderErrorsTo >>>> >>>> false >>>> >>>> PMode.ErrorHandling.Report.ReceiverErrorsTo >>>> >>>> false >>>> >>>> PMode.ErrorHandling.Report.AsResponse >>>> >>>> true >>>> >>>> PMode.ErrorHandling.Report.ProcessErrorNotifyConsumer >>>> >>>> false >>>> >>>> PMode.ErrorHandling.Report.ProcessErrorNotifyProducer >>>> >>>> true >>>> >>>> PMode.ErrorHandling.Report.DeliveryFailuresNotifyProducer >>>> >>>> true >>>> >>>> PMode.Security.WSSVersion >>>> >>>> false >>>> >>>> PMode.Security.X509.Sign >>>> >>>> false >>>> >>>> PMode.Security. X509.Encryption >>>> >>>> false >>>> >>>> PMode.Security.UsernameToken >>>> >>>> false >>>> >>>> PMode.Security.PModeAuthorize >>>> >>>> false >>>> >>>> PMode.Security.SendReceipt >>>> >>>> true >>>> >>>> PMode.Security.SendReceipt.NonRepudiation >>>> >>>> false >>>> >>>> PMode.PayloadService.CompressionType >>>> >>>> true >>>> >>>> PMode.ReceptionAwareness >>>> >>>> true >>>> >>>> PMode.ReceptionAwareness.Retry.Parameters >>>> >>>> true >>>> >>>> AS4 support in EI, will be introduced as a separate transport. >>>> >>>> [1] http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/ >>>> AS4-profile/v1.0/os/AS4-profile-v1.0-os.html >>>> [2] https://github.com/manoramahp/org.wso2.carbon.mediator.as4 >>>> >>>> Thanks, >>>> Manorama >>>> -- >>>> Manorama Perera >>>> Software Engineer >>>> WSO2, Inc.; http://wso2.com/ >>>> >>> >>> >>> >>> -- >>> Manorama Perera >>> Software Engineer >>> WSO2, Inc.; http://wso2.com/ >>> >> >> >> >> -- >> Manorama Perera >> Software Engineer >> WSO2, Inc.; http://wso2.com/ >> > > > > -- > Manorama Perera > Software Engineer > WSO2, Inc.; http://wso2.com/ > -- 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/ <http://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] ESB Connector for BreezoMeter
Hi Pawan, Good to hear. Like to see connector getting published to the store soon. On Thu, Jul 13, 2017 at 3:44 PM, Pawan Nayanajith <djnayanaj...@gmail.com> wrote: > Hi All, > > I have finished the implementation of the connector for BreezoMeter and I > have written all the methods that I have mentioned in the previous mail. > > And now I am currently writing test cases for those methods. > > Thank you. > Pawan Nayanajith > Department of Computer Science, > University of Jaffna. > > On Fri, Jun 23, 2017 at 10:28 AM, Shakila Sivagnanarajah <shak...@wso2.com > > wrote: > >> Hi Pawan, >> >> Thank you for contributing to WSO2 Extensions. >> >> Your method selection looks good. >> >> When we complete connector, it should include all of the following. >> >>- Implement the connector and do developer testing. >>- Implement the integration testing and test with ESB tooling. >>- Complete the documentation. >>- Get your code reviewed by the WSO2 team. >> >> Other than the connector implementation, you can think of implementing an >> integration scenario with a real world use case. For your reference, please >> look at [1]. >> >> If you have any questions regarding this please let us know. >> >> [1] https://docs.wso2.com/display/ESBCONNECTORS/Sample+Business+ >> Scenario+for+Shopify >> >> Thanks >> >> On Thu, Jun 22, 2017 at 1:54 PM, Pawan Nayanajith <djnayanaj...@gmail.com >> > wrote: >> >>> Hi All, >>> >>> I have planned to implement a WSO2 ESB connector for BreezoMeter as a >>> part of the 3rd year project for the course unit "Rapid Application >>> Development". >>> >>> Where *BreezoMeter <https://breezometer.com/air-quality-api/> *is a >>> world leading air pollution API and it provides real-time air quality >>> data across the world. >>> >>> I have planned to include the following methods into the connector. >>> >>> Real Time Air Quality Data <https://breezometer.com/air-quality-api/> >>> >>>- Get real time air quality data by address. >>>- Get real time air quality data by latitude and longitude >>>(Geocoding). >>> >>> History Air Quality Data for a Specific Date >>> <https://breezometer.com/air-quality-api/history-api/> >>> >>>- Get history air quality data by address for a specific date. >>>- Get history air quality data by latitude and longitude (Geocoding) >>>for a specific date. >>> >>> History Air Quality data for a Range of Dates >>> <https://breezometer.com/air-quality-api/history-api/> >>> >>>- Get history air quality data by address for a range of dates. >>>- Get history air quality data by latitude and longitude (Geocoding) >>>for a range of dates. >>> >>> >>> Thank you. >>> >>> Pawan Nayanajith >>> Department of Computer Science, >>> University of Jaffna. >>> >>> >> >> >> -- >> Shakila Sivagnanarajah >> Software Engineer >> Mobile :+94 (0) 768 856837 <076%20885%206837> >> shak...@wso2.com >> WSO2, Inc. >> lean . enterprise . middleware >> http://www.wso2.com/ >> > > -- 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/ <http://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] Salesforce Wave Analytics Connector
Hi Praveenath, Thank you for keeping us updated. I guess soon we can get the connector to the store. On Thu, Jul 13, 2017 at 2:59 PM, Praveenath Logeshwaran < logeshwaranpraveen...@gmail.com> wrote: > Hello there, >I have implemented all the methods which I mentioned in the > previous mail. Currently I am working on implementing test cases for those > endpoints. > > > On 23 June 2017 at 09:28, Kesavan Yogarajah <kesav...@wso2.com> wrote: > >> Hi Praveen, >> >> Thank you for contributing WSO2 Extensions. >> >> Your method selection looks good. >> >> When we say complete connector, it should be all of the following. >> >>- Develop the methods and do developer testing. >>- Implement the integration testing and test with ESB tooling. >>- Complete documentation. >> >> If you have any questions regarding this please let us know. >> >> Regards >> Kesavan >> >> Kesavan Yogarajah >> Software Engineer >> Mobile :+94 (0) 779 758021 <077%20975%208021> >> kesav...@wso2.com >> WSO2, Inc. >> lean . enterprise . middleware >> >> On Thu, Jun 22, 2017 at 7:12 PM, Praveenath Logeshwaran < >> logeshwaranpraveen...@gmail.com> wrote: >> >>> Hi All, >>> >>> I am Praveenath Logeshwaran, studying Computer Science at University of >>> Jaffna. I have planned to implement Salesforce Wave Analytics >>> <https://developer.salesforce.com/docs/atlas.en-us.bi_dev_guide_rest.meta/bi_dev_guide_rest/bi_rest_overview.htm> >>> connector as my 3rd year project for “Rapid Application Development” >>> course unit. I have planned to include the following methods into the >>> connector: >>> >>> >>> >>>- >>> >>>Wave Resource >>> >>> <https://developer.salesforce.com/docs/atlas.en-us.bi_dev_guide_rest.meta/bi_dev_guide_rest/bi_resources_wave.htm> >>>- >>> >>> Get Wave Resource >>> - >>> >>>Dashboards List Resource >>> >>> <https://developer.salesforce.com/docs/atlas.en-us.bi_dev_guide_rest.meta/bi_dev_guide_rest/bi_resources_dashboards.htm> >>>- >>> >>> Get Dashboard Resource >>> - >>> >>>Datasets List Resource >>> >>> <https://developer.salesforce.com/docs/atlas.en-us.bi_dev_guide_rest.meta/bi_dev_guide_rest/bi_resources_datasets.htm> >>>- >>> >>> Get Datasets List Resource >>> - >>> >>>Dataset Resource >>> >>> <https://developer.salesforce.com/docs/atlas.en-us.bi_dev_guide_rest.meta/bi_dev_guide_rest/bi_resources_dataset_id.htm> >>>- >>> >>> Get Dataset Resource >>> - >>> >>> Update Dataset Resource >>> - >>> >>> Delete Dataset Resource >>> - >>> >>>Query Resource >>> >>> <https://developer.salesforce.com/docs/atlas.en-us.bi_dev_guide_rest.meta/bi_dev_guide_rest/bi_resources_query.htm> >>>- >>> >>> Execute Query >>> - >>> >>>Versions List Resource >>> >>> <https://developer.salesforce.com/docs/atlas.en-us.bi_dev_guide_rest.meta/bi_dev_guide_rest/bi_resources_datasets_id_versions.htm> >>>- >>> >>> Get Versions List >>> - >>> >>>Version Resource >>> >>> <https://developer.salesforce.com/docs/atlas.en-us.bi_dev_guide_rest.meta/bi_dev_guide_rest/bi_resources_datasets_id_versions_id.htm> >>>- >>> >>> Get Dataset version >>> - >>> >>> Update Dataset Predicate >>> - >>> >>>XMD List Resource >>> >>> <https://developer.salesforce.com/docs/atlas.en-us.bi_dev_guide_rest.meta/bi_dev_guide_rest/bi_resources_xmds.htm> >>>- >>> >>> Get list of XMD Resource >>> - >>> >>>XMD Resource >>> >>> <https://developer.salesforce.com/docs/atlas.en-us.bi_dev_guide_rest.meta/bi_dev_guide_rest/bi_resources_xmd_main.htm> >>>- >>> >>> Get XMD for a version of a dataset >>> >>> >>> -- >>> Regards >>> Praveenath >>> >>> >>> >> > > > -- > Regards > Praveenath > Tel :+94777479780 <077%20747%209780> > > -- 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/ <http://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] Choosing APIs to Implement Connectors
Hi Tharuka, Thx for the explanation. This looks good. On Wed, Jul 12, 2017 at 12:34 AM, Tharuka <tharuka.ckasth...@gmail.com> wrote: > Hello Sir. > > I think you didn't get clearly what I'm tryng to say.Here is the simple > sequence Diagram. > <http://wso2-oxygen-tank.10903.n7.nabble.com/file/n150216/Capture.png> > > Thank you sir. > > Tharuka KasthuriArachci. > Department of Computer Science, > University of Jaffna. > > > > -- > View this message in context: http://wso2-oxygen-tank.10903. > n7.nabble.com/Choosing-APIs-to-Implement-Connectors-tp150163p150216.html > Sent from the WSO2 Architecture mailing list archive at Nabble.com. > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- 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/ <http://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] Choosing APIs to Implement Connectors
Hi Tharuka , If I understand correctly when an user uploads content, user gets a notification to his/her own mobile device? If not can you provide more details on the use case you are planning to implement. Maybe a simple sequence diagram may help? On Tue, Jul 11, 2017 at 5:50 PM, Tharuka <tharuka.ckasth...@gmail.com> wrote: > Hello Sir, > BTW you can call me Malaka :) > > Thank you for your consideration and reply, in vk.com their is a option to > allow the current location of the user when they uploading a post. we can > detect their location by that method and for messaging option we use to use > their last location(which uploaded their last post) as their location. and > also we kindly request you if their is any mistake in our business senario > please let us know. > > thank you sir, > > Tharuka KasthuriArachchi, > Department of Computer Science, > University of jaffna. > > > > > > -- > View this message in context: http://wso2-oxygen-tank.10903. > n7.nabble.com/Choosing-APIs-to-Implement-Connectors-tp150163p150202.html > Sent from the WSO2 Architecture mailing list archive at Nabble.com. > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- 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/ <http://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] Choosing APIs to Implement Connectors
Hi Tharuka, Sounds good. Can you explain bit about how are you planning to detect the location of the user? On Mon, Jul 10, 2017 at 11:52 PM, Tharuka <tharuka.ckasth...@gmail.com> wrote: > Hi All, > > We are 3rd year students of University of Jaffna, as our third year project > in Rapid application development We wish do impliment esb connectors for > following APIs. > 1. Vk - A Social media network > 2. Google Geocoding - A mapping service > 3. Pushover - Messaging > 4. PhotoBucket - Photo > > And also we will build a bussiness senario using these APIs. can anyone > suggest us about these APIs. > here is our business senario. > Untitled.png > <http://wso2-oxygen-tank.10903.n7.nabble.com/file/n150163/Untitled.png> > If we connect Geocoding and VK social media then users post photos and > status we can detect the location of the user. Also by connection of VK and > pushover notification service user can receive update to their android or > apple phone. > > we are four members in our group. > Can we implement connetors for these APIs, also we need more suggestion > about our business senario. > > Thank you > Tharuka KasthuriArachchi, > Department of Computer Science, > Univercity of Jaffna. > > > > -- > View this message in context: http://wso2-oxygen-tank.10903. > n7.nabble.com/Choosing-APIs-to-Implement-Connectors-tp150163.html > Sent from the WSO2 Architecture mailing list archive at Nabble.com. > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- 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/ <http://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] Choosing APIs for implementing connectors
Hi Kausik and Team, Good to hear. I think first you can share us the use case you are planning to implement. Then you can implement the connectors to support the mentioned use case. Find more details on samples and how to write a connector in [1] and [2] [1] https://docs.wso2.com/display/ESBCONNECTORS/Writing+a+Connector [2] https://docs.wso2.com/display/ESBCONNECTORS/Sample+Business+Scenarios On Tue, Jul 4, 2017 at 9:58 PM, Kausik <kausik...@gmail.com> wrote: > Thank You for your response. our group has 5 members. We are planning to do > one connector per each person. > > > > -- > View this message in context: http://wso2-oxygen-tank.10903. > n7.nabble.com/Choosing-APIs-for-implementing-connectors- > tp149953p149984.html > Sent from the WSO2 Architecture mailing list archive at Nabble.com. > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- 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/ <http://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] Choosing APIs for implementing connectors
Hi Kausik, Good to hear that you are interested in doing connectors. Yes I guess you have a good combinations of apis. CRM, Accounting, Marketing and social media. I guess you can come up with an interesting bossiness use case :) On Mon, Jul 3, 2017 at 8:59 PM, Kausik <kausik...@gmail.com> wrote: > Hi All, > > We are planning to implement WSO2 ESB connectors for following APIs > 1.Dotmailer > 2.Sage > 3.Streak > 4.Buffer > 5.Followupboss > as a part of the 3rd year project for the course unit "Rapid Application > Development". > > And also we will build a business scenario using these APIs. Can anyone > suggest us about these APIs. > Can we implementt the connectors for these APIs. > > > Thank you. > > M.Kausik > 3rd Year > Department of Computer Science, > University of Jaffna. > > > > -- > View this message in context: http://wso2-oxygen-tank.10903. > n7.nabble.com/Choosing-APIs-for-implementing-connectors-tp149952.html > Sent from the WSO2 Architecture mailing list archive at Nabble.com. > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- 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/ <http://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] [PET] Amazon Lambda Connector
Hi Kanapriya, I think our focus should be to invoke function with parameters. Not the admin or dev operations what are most likely one time tasks. On Mon, Jun 26, 2017 at 12:03 PM, Kanapriya Kuleswararajan <kanapr...@wso2.com> wrote: > Hi All, > > We have planned to do amazon lambda connector for ESB with the following > Methods [1] for initial version. > > AWS Lambda : - is an event-driven, server-less computing platform provided > by Amazon as a part of the Amazon Web Services. It is a compute service that > runs code in response to events and automatically manages the compute > resources required by that code. > > [1] > > CreateFunction - Creates a new Lambda function. > DeleteFunction - Deletes the specified Lambda function code and > configuration. > GetFunction - Returns the configuration information of the Lambda function > and a presigned URL link to the .zip file you uploaded with CreateFunction > so can download the .zip file. > GetFunctionConfiguration - Returns the configuration information of the > Lambda function. > ListFunctions - Returns a list of your Lambda functions. > ListVersionsByFunction - List all versions of a function. > UpdateFunctionCode - Updates the code for the specified Lambda function. > UpdateFunctionConfiguration - Updates the configuration parameters for the > specified Lambda function by using the values provided in the request. > CreateAlias - Creates an alias that points to the specified Lambda function > version. > DeleteAliasn - Deletes the specified Lambda function alias. > GetAlias - Returns the specified alias information such as the alias ARN, > description, and function version it is pointing to. > ListAliases - Returns list of aliases created for a Lambda function. > UpdateAlias - To update the function version to which the alias points and > the alias description. > AddPermission - Adds a permission to the resource policy associated with the > specified AWS Lambda function. > RemovePermission - To remove individual permissions from an resource policy > associated with a Lambda function by providing a statement ID that provided > when added the permission. > GetAccountSettings - Returns a customer's account settings. > > > Please let me know if you have any suggestions on this? > > > Thanks, > Kanapriya Kuleswararajan > Software Engineer | WSO2 > Mobile : - 0774894438 > Mail : - kanapr...@wso2.com > LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ -- 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] [PET] Microsoft Dynamics CRM Connector
Hi Kanapriya, This approach looks good. It'll not be practical to support all the entity types and there also can be custom fields. On Fri, May 19, 2017 at 11:33 AM, Kanapriya Kuleswararajan < kanapr...@wso2.com> wrote: > Hi All, > > In MicrosoftDynamicCRM, there is a method to create [1], update, delete > entities and etc. But each entity has different or dynamic set of > parameters [2]. > > Due to that , Now I'm planning to implement the connector by getting the > entity type and required payload for that specific entity from the user. > > [1] https://msdn.microsoft.com/en-us/library/gg328090.aspx#bkmk_ > basicCreate > [2] https://msdn.microsoft.com/en-us/library/mt607894.aspx#bkmk_Properties > > Any concern on this? > > Thanks > Kanapriya > > Kanapriya Kuleswararajan > Software Engineer | WSO2 > Mobile : - 0774894438 <077%20489%204438> > Mail : - kanapr...@wso2.com > LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ > <https://www.linkedin.com/in/hariprasath-thanarajah-5234b660> > > On Wed, May 17, 2017 at 2:46 PM, Kanapriya Kuleswararajan < > kanapr...@wso2.com> wrote: > >> Hi All, >> >> I have planned to implement a Microsoft Dynamics Customer Relationship >> Management (CRM) connector with the following Methods [1] for initial >> version. >> >> Microsoft Dynamics CRM [2] is now known as Microsoft Dynamics 365 for >> Sales, Marketing, and Service. The Web API [3] which is new for Microsoft >> Dynamics 365 (online & on-premises), provides a development experience that >> can be used across a wide variety of programming languages, platforms, and >> devices. The Web API implements the OData (Open Data Protocol), version >> 4.0, an OASIS standard for building and consuming RESTful APIs over rich >> data sources. >> Here We have to register a Dynamics 365 app with Azure Active Directory >> as mentioned in [4] >> ( ie, The user must have a Microsoft Dynamics 365 (online) system user >> account with administrator role for the Microsoft Office 365 subscription). >> So that it can connect to the Microsoft Dynamics 365 server, authenticate >> using OAuth [5], and access the web services. >> >> [1] >> >>- Create - This example creates a new account entity. The response >>OData-EntityId header contains the Uri of the created entity. >>- Associate entities on create - To associate new entities to >>existing entities when they are created and need to set the value of >>single-valued navigation properties using the @odata.bind annotation. >>- Create with data returned - All the data from the created record >>will be returned with a status of 201 (Created). >>- Retrieve - Returns data for an account entity instance with the >>primary key value >>- Retrieve specific properties - To retrieve the entities with the >>specific property values >>- Retrieve using an alternate key - If an entity has an alternate key >>defined, then use the alternate key to retrieve the entity instead of the >>unique identifier for the entity. >>- Retrieve a single property value - To retrieve the value of a >>single property for an entity, >>- Update - Updates an existing account record with the accountid >>value >>- Update with data returned - To retrieve data from an entity you are >>updating you can compose your PATCH request so that data from the created >>record will be returned with a status of 200 (OK). >>- Update a single property value - To update only a single property >>value >>- Delete a single property value - To delete the value of a single >>property >>- Upsert an entity - An upsert operation is exactly like an update. >>The difference is that if the entity doesn’t exist it will be created. If >>it already exists, it will be updated. >>- Delete - To delete an entity >> >> [2] https://en.wikipedia.org/wiki/Microsoft_Dynamics_CRM >> [3] https://msdn.microsoft.com/en-us/library/mt593051.aspx >> [4] https://msdn.microsoft.com/en-us/library/mt622431.aspx >> [5] https://docs.microsoft.com/en-us/azure/active-directory/deve >> lop/active-directory-protocols-oauth-code >> >> Please let me know if you have any suggestions on this? >> >> Thanks >> Kanapriya Kuleswararajan >> Software Engineer | WSO2 >> Mobile : - 0774894438 <077%20489%204438> >> Mail : - kanapr...@wso2.com >> LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ >> <https://www.linkedin.com/in/hariprasath-th
Re: [Architecture] Milestone Plan for new version of Kafka Connector
Hi Hariprasath, We have to consider new features what come with 0.9 such as security. Shall we identify the new feature list first. Then will update plan accordingly. Also I feel we need to allocate some more time for the load testing. [1] https://www.confluent.io/blog/apache-kafka-0-9-is-released/ On Mon, May 15, 2017 at 12:30 PM, Hariprasath Thanarajah < haripras...@wso2.com> wrote: > Hi All, > > We are now planning to create a new version of Kafka connector for Kafka > version 0.9.0. Please find the attached milestone plan below in [1], > > [1] - https://docs.google.com/a/wso2.com/spreadsheets/d/ > 1FvdEBDCzqImJdaK-RdD6k6x_60eskXzfOn2cLTRT-4w/edit?usp=sharing > > -- > > > *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/ <http://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] [PET] SNMP Connector
Hi Vivekananthan, AFAIK this communication is asynchronous and we may not get the response on the same path. So we have to design properly when implementing the listener since we can maintain listener per message flow? [1] http://www.jitendrazaa.com/blog/java/snmp/create-snmp-client-in-java-using-snmp4j/ On Tue, Mar 7, 2017 at 11:18 AM, Vivekananthan Sivanayagam < vivekanant...@wso2.com> wrote: > Hi Malaka, > > We are using snmp4j[1] library to implement the connector. > > SNMP Communication: > > [image: Inline image 1] > > Let see how SNMPSet operation works, The set operation is used to > change[2] the value of a managed object or to create a new row in a table. > Objects that are defined in the MIB as read-write or write-only can be > altered or created. The Manager sends the SET request to Agent and Agent > will receive the request and will respond with a GetResponse message > indicating the change has been made or an error indication as to why the > change cannot be made. > > Layered communication: > > [image: Inline image 2] > > [1] http://www.snmp4j.org/html/download.html > [2] https://en.wikipedia.org/wiki/Simple_Network_ > Management_Protocol#Overview_and_basic_concepts > > Vivekananthan Sivanayagam > Associate Software Engineer | WSO2 > E:vivekanant...@wso2.com > M:+94752786138 <075%20278%206138> > > On Tue, Mar 7, 2017 at 8:55 AM, Malaka Silva <mal...@wso2.com> wrote: > >> Hi Vivekananthan, >> >> I guess here ESB acts as the SNMP Manager? Also can you explain how the >> communications happens, protocol details, are you planning to use any libs >> etc, >> >> Perhaps a flow diagram will help. >> >> On Mon, Mar 6, 2017 at 10:01 PM, Vivekananthan Sivanayagam < >> vivekanant...@wso2.com> wrote: >> >>> >>> >>> H >>> >>> i All, >>> >>> Currently, I am implementing the SNMP connector which used to monitor >>> and configure the network components such as servers, routers, switches or >>> printers through the WSO2 ESB and supports SNMP Version 2. >>> >>> *About SNMP:* >>> >>> Simple Network Management Protocol (SNMP) is an Internet-standard >>> protocol for managing devices on IP networks. Using SNMP, the Network >>> operators can be able to manage their network elements, identify the >>> problem and can configure the remote system. >>> >>> Let us take a simple example to understand SNMP, consider a Network with >>> four printers, and we need to shut down the Printer 1(P1), using a >>> management protocol like SNMP we can easily figure out the right device and >>> do shut down. For that, we can succeed with SNMPSet operation which is used >>> to set/write values in the Managed Device. Basically, it is used to >>> configure Network Elements. >>> >>> There are two major things we need to get to know when talking about >>> SNMP. >>> >>> *SNMP Manager:* A manager or management system is a separate entity >>> that is responsible for communicating with the SNMP agent implemented >>> network devices. >>> >>> *SNMP Agent:* The agent is a program that is packaged within the >>> network element. Enabling the agent allows it to collect the management >>> information database from the device locally and makes it available to the >>> SNMP manager. >>> >>> *Note*: If we assign the SNMP Manager to write permission for the >>> SNMP Agent, the SNMP Manager can also send a configuration request to the >>> Agent (using a Set message) to change a local parameter. >>> >>> *Understanding the Management Information Base (MIB)* >>> >>> When an SNMPManager requests information from an SNMPAgent, the SNMP >>> Agent retrieves the current value of the requested information from the >>> Management Information Base (MIB). The MIB defines the managed objects that >>> an SNMP manager monitors (or sometimes configures) on an SNMP agent. >>> >>> *SNMP Connector Operation:* >>> >>> snmpGet: The GET operation is a request sent by the manager to the >>> managed device. It is performed to retrieve one or more values from the >>> managed device. >>> SnmpGetBulk: The GETBULK operation is used to retrieve voluminous data >>> from large MIB table. >>> snmpGetNext : >>> >>> The >>> GET NEXT operation retrieves the value of the next OID in the MIB tree. >>> snmpSet: This operation is used by the managers to modify o
Re: [Architecture] [PET] SNMP Connector
Hi Vivekananthan, I guess here ESB acts as the SNMP Manager? Also can you explain how the communications happens, protocol details, are you planning to use any libs etc, Perhaps a flow diagram will help. On Mon, Mar 6, 2017 at 10:01 PM, Vivekananthan Sivanayagam < vivekanant...@wso2.com> wrote: > > > H > > i All, > > Currently, I am implementing the SNMP connector which used to monitor and > configure the network components such as servers, routers, switches or > printers through the WSO2 ESB and supports SNMP Version 2. > > *About SNMP:* > > Simple Network Management Protocol (SNMP) is an Internet-standard protocol > for managing devices on IP networks. Using SNMP, the Network operators can > be able to manage their network elements, identify the problem and can > configure the remote system. > > Let us take a simple example to understand SNMP, consider a Network with > four printers, and we need to shut down the Printer 1(P1), using a > management protocol like SNMP we can easily figure out the right device and > do shut down. For that, we can succeed with SNMPSet operation which is used > to set/write values in the Managed Device. Basically, it is used to > configure Network Elements. > > There are two major things we need to get to know when talking about SNMP. > > *SNMP Manager:* A manager or management system is a separate entity > that is responsible for communicating with the SNMP agent implemented > network devices. > > *SNMP Agent:* The agent is a program that is packaged within the > network element. Enabling the agent allows it to collect the management > information database from the device locally and makes it available to the > SNMP manager. > > *Note*: If we assign the SNMP Manager to write permission for the SNMP > Agent, the SNMP Manager can also send a configuration request to the Agent > (using a Set message) to change a local parameter. > > *Understanding the Management Information Base (MIB)* > > When an SNMPManager requests information from an SNMPAgent, the SNMP Agent > retrieves the current value of the requested information from the > Management Information Base (MIB). The MIB defines the managed objects that > an SNMP manager monitors (or sometimes configures) on an SNMP agent. > > *SNMP Connector Operation:* > > snmpGet: The GET operation is a request sent by the manager to the managed > device. It is performed to retrieve one or more values from the managed > device. > SnmpGetBulk: The GETBULK operation is used to retrieve voluminous data > from large MIB table. > snmpGetNext : > > The > GET NEXT operation retrieves the value of the next OID in the MIB tree. > snmpSet: This operation is used by the managers to modify or assign the > value of the Managed device. > > > Thanks, > Vivek. > > Vivekananthan Sivanayagam > Associate Software Engineer | WSO2 > E:vivekanant...@wso2.com > M:+94752786138 <075%20278%206138> > -- 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/ <http://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] SNMP Connector
Hi Thulasika, How are we progressing with this? On Thu, Dec 8, 2016 at 4:13 PM, Thulasika Vijayanathan <thulas...@wso2.com> wrote: > Hi , > > SNMP connector send the SNMP messages to SNMP listener, to send the SNMP > messages we need to specify the following properties: > >- Request Identifier: A number used to match requests with replies. It >is generated by the device that sends a request and copied into this field >in a Response-PDU by the responding SNMP entity. >- Error Index: When Error Status is non-zero, this field contains a >pointer that specifies which object generated the error. Always zero in a >request. >- Variable Bindings: A set of name-value pairs identifying the MIB >objects in the PDU, and in the case of messages other than requests, >containing their values. >- PDU Type: An integer value that indicates the PDU type. > > > Thanks, > Thulasika. > > On Thu, Dec 8, 2016 at 11:06 AM, Malaka Silva <mal...@wso2.com> wrote: > >> Hi Thulasika, >> >> How are you progressing with this. It'll be great if you could explain >> what level of details we can publish and how? >> >> On Fri, Dec 2, 2016 at 12:38 PM, Thulasika Vijayanathan < >> thulas...@wso2.com> wrote: >> >>> Hi, >>> >>> I am planning to implement the SNMP connector to send the SNMP messages >>> to other devices. >>> >>> When a device send a message to the ESB mediation flow(that means when >>> we receive a request/message to ESB mediation flow), the connector should >>> be able to compose and address the SNMP message and send it to the >>> destination which will be listening to the SNMP messages as shown below. >>> >>> >>> >>> Please give your suggestion on this. >>> >>> >>> Thanks, >>> >>> Thulasika. >>> >>> On Thu, Nov 24, 2016 at 9:57 AM, Thulasika Vijayanathan < >>> thulas...@wso2.com> wrote: >>> >>>> Hi, >>>> >>>> From this method we can retrieve the managed device's system >>>> details(local or remote device), For example, When using this get method we >>>> can get the response as follows: Linux thulasi-ThinkPad-T540p >>>> 4.4.0-47-generic #68~14.04.1-Ubuntu SMP Wed Oct 26 19:42:11 UTC 2016 >>>> x86_64]. >>>> >>>> Thanks, >>>> Thulasika. >>>> >>>> On Wed, Nov 23, 2016 at 6:20 PM, Malaka Silva <mal...@wso2.com> wrote: >>>> >>>>> Hi Thulasika, >>>>> >>>>> The use case we should support is the SNMP connector should >>>>> send/publish SNMP messages in ESB mediation flow. >>>>> >>>>> I am not sure what do you mean by retrieve stats. Is there any use >>>>> case that you try to cover. >>>>> >>>>> On Wed, Nov 23, 2016 at 1:35 PM, Sidath Weerasinghe <sid...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi Thulasika, >>>>>> >>>>>> can you explain how do you expose server analytics via SNMP ? >>>>>> >>>>>> >>>>>> On Wed, Nov 23, 2016 at 11:43 AM, Thulasika Vijayanathan < >>>>>> thulas...@wso2.com> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I have planned to implement the SNMP connector. Simple Network >>>>>>> Management Protocol (SNMP) is a widely used protocol for monitoring >>>>>>> network >>>>>>> devices such as servers, printers, hubs, switches, and routers on an IP >>>>>>> network. >>>>>>> >>>>>>> Connector will have the following operation: >>>>>>> snmpGet():- It is performed to retrieve one or more values from the >>>>>>> managed remote/local device. >>>>>>> >>>>>>> [1] https://wso2.org/jira/browse/ESBCONNECT-133 >>>>>>> >>>>>>> Thanks, >>>>>>> -- >>>>>>> Thulasika >>>>>>> Associate Software Engineer >>>>>>> Mobile:0778014295 >>>>>>> email: thulas...@wso2.com <sanj...@wso2.com> >>>>>>> >>>>>>> _______ >>>>>>> Architecture mailing list >>>>>>> Architectur
Re: [Architecture] SNMP Connector
Hi Thulasika, How are you progressing with this. It'll be great if you could explain what level of details we can publish and how? On Fri, Dec 2, 2016 at 12:38 PM, Thulasika Vijayanathan <thulas...@wso2.com> wrote: > Hi, > > I am planning to implement the SNMP connector to send the SNMP messages to > other devices. > > When a device send a message to the ESB mediation flow(that means when we > receive a request/message to ESB mediation flow), the connector should be > able to compose and address the SNMP message and send it to the destination > which will be listening to the SNMP messages as shown below. > > > > Please give your suggestion on this. > > > Thanks, > > Thulasika. > > On Thu, Nov 24, 2016 at 9:57 AM, Thulasika Vijayanathan < > thulas...@wso2.com> wrote: > >> Hi, >> >> From this method we can retrieve the managed device's system >> details(local or remote device), For example, When using this get method we >> can get the response as follows: Linux thulasi-ThinkPad-T540p >> 4.4.0-47-generic #68~14.04.1-Ubuntu SMP Wed Oct 26 19:42:11 UTC 2016 >> x86_64]. >> >> Thanks, >> Thulasika. >> >> On Wed, Nov 23, 2016 at 6:20 PM, Malaka Silva <mal...@wso2.com> wrote: >> >>> Hi Thulasika, >>> >>> The use case we should support is the SNMP connector should >>> send/publish SNMP messages in ESB mediation flow. >>> >>> I am not sure what do you mean by retrieve stats. Is there any use case >>> that you try to cover. >>> >>> On Wed, Nov 23, 2016 at 1:35 PM, Sidath Weerasinghe <sid...@wso2.com> >>> wrote: >>> >>>> Hi Thulasika, >>>> >>>> can you explain how do you expose server analytics via SNMP ? >>>> >>>> >>>> On Wed, Nov 23, 2016 at 11:43 AM, Thulasika Vijayanathan < >>>> thulas...@wso2.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> I have planned to implement the SNMP connector. Simple Network >>>>> Management Protocol (SNMP) is a widely used protocol for monitoring >>>>> network >>>>> devices such as servers, printers, hubs, switches, and routers on an IP >>>>> network. >>>>> >>>>> Connector will have the following operation: >>>>> snmpGet():- It is performed to retrieve one or more values from the >>>>> managed remote/local device. >>>>> >>>>> [1] https://wso2.org/jira/browse/ESBCONNECT-133 >>>>> >>>>> Thanks, >>>>> -- >>>>> Thulasika >>>>> Associate Software Engineer >>>>> Mobile:0778014295 >>>>> email: thulas...@wso2.com <sanj...@wso2.com> >>>>> >>>>> ___ >>>>> Architecture mailing list >>>>> Architecture@wso2.org >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Thank You, >>>> Best Regards, >>>> >>>> Sidath Weerasinghe >>>> >>>> >>>> *Intern* >>>> >>>> *WSO2, Inc. * >>>> >>>> *lean . enterprise . middleware * >>>> >>>> >>>> *Mobile: +94719802550 <%2B94719802550>* >>>> >>>> *Email: *sid...@wso2.com >>>> >>>> Blog: https://medium.com/@sidath >>>> >>>> Linkedin: https://lk.linkedin.com/in/sidathweerasinghe >>>> >>>> _______ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> >>> Best Regards, >>> >>> Malaka Silva >>> Senior Technical Lead >>> M: +94 777 219 791 >>> Tel : 94 11 214 5345 >>> Fax :94 11 2145300 <011%202%20145300> >>> 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 >>> >> >> >> >> -- >> Thulasika >> Associate Software Engineer >> Mobile:0778014295 <077%20801%204295> >> email: thulas...@wso2.com <sanj...@wso2.com> >> > > > > -- > Thulasika > Associate Software Engineer > Mobile:0778014295 <077%20801%204295> > email: thulas...@wso2.com <sanj...@wso2.com> > -- Best Regards, Malaka Silva Senior Technical Lead 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/ <http://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] ESB connector auto generation tool
Just to add we are also planning to do swagger to connector automation in parallel. On Thu, Dec 1, 2016 at 5:56 PM, Rajjaz Mohammed <raj...@wso2.com> wrote: > Hi All, > > I have released connector automation tool[1] for custom wsdl . Our next > step is to improve existing tool to support generic wsdl files like > salesforce partner wsdl. > Also this should not be specific to SFDC in future. Should support wsdls in general. > > [1] https://docs.wso2.com/display/ESBCONNECTORS/ESB+Connector+ > Auto+Generation+Tool > > On Fri, Nov 4, 2016 at 7:22 PM, Rajjaz Mohammed <raj...@wso2.com> wrote: > >> Hi Malaka, >> >> This is the output of the tool for check . Currently I’m working on the >> documentation part. >> >> On Fri, Nov 4, 2016 at 7:08 PM, Malaka Silva <mal...@wso2.com> wrote: >> >>> Hi Rajjaz, >>> >>> So phrase 1 is to complete automation of Salesforce custom integration >>> with ESB. >>> >>> Attaching the configs may not be clear for some one to followup. Can you >>> document the steps how we can automate this integration? >>> >>> On Fri, Nov 4, 2016 at 6:41 PM, Rajjaz Mohammed <raj...@wso2.com> wrote: >>> >>>> Hi All, >>>> >>>> I have done the first face of the development and test the connector >>>> with ESB and it's works as expected. Here with i attached the apex class, >>>> WSDL ,generated connector source code and the connector zip. >>>> >>>> *Authentication is only support for salesforce in current development . >>>> Later we will extend to other products. >>>> >>>> On Fri, Oct 14, 2016 at 6:26 AM, Malaka Silva <mal...@wso2.com> wrote: >>>> >>>>> I think we should have both options and user can control the behavior. >>>>> >>>>> Also we should automate init method for known use cases. >>>>> >>>>> On Thu, Oct 13, 2016 at 4:08 PM, Keerthika Mahendralingam < >>>>> keerth...@wso2.com> wrote: >>>>> >>>>>> IMO we need to go ahead with the first approach since there may be >>>>>> some cases we need to have some additional properties, headers, or host, >>>>>> etc. which are not common for all connectors. These are depend on the >>>>>> backend service. >>>>>> >>>>>> >>>>>> Thanks, >>>>>> Keerthika. >>>>>> >>>>>> On Thu, Oct 13, 2016 at 3:55 PM, Rajjaz Mohammed <raj...@wso2.com> >>>>>> wrote: >>>>>> >>>>>>> Hi All, >>>>>>> >>>>>>> We have two options in the output of auto-generation tool. >>>>>>> >>>>>>>1. source code of the connector >>>>>>>2. connector zip >>>>>>> >>>>>>> If we generate connector zip file directly we can reduce the manual >>>>>>> works but if we generate the source code from this tool >>>>>>> >>>>>>>- add init method manually for authentication >>>>>>>- modify some special cases like adding DISABLE_CHUNKING etc. >>>>>>>- integration test >>>>>>> >>>>>>> WDYT? >>>>>>> >>>>>>> On Wed, Oct 12, 2016 at 3:28 PM, Malaka Silva <mal...@wso2.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Yes Authorization is bit tricky and specific to vendors. So we can >>>>>>>> have predefined templates (eg: Salesforce custom web services) and make >>>>>>>> this plug-able? >>>>>>>> >>>>>>>> On Wed, Oct 12, 2016 at 2:44 PM, Rajjaz Mohammed <raj...@wso2.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi All, >>>>>>>>> >>>>>>>>> I have done some testings on this area for that I created an apex >>>>>>>>> class[1] to create an account in salesforce and tested with simple >>>>>>>>> java >>>>>>>>> client using WSDL file and it works fine and can able to extract the >>>>>>>>> common >>>>>>>>> information from WSDL (attached). >>>>>>>>> >&
Re: [Architecture] Connection Pool Implementation for ESB Kafka and JMS Connectors
Seems like a significant improvement. I guess pool exists per node in cluster? Once completed please arrange a code review. On Wed, Nov 30, 2016 at 12:27 PM, Kathees Rajendram <kath...@wso2.com> wrote: > Hi, > > I am working on connection pool implementation for Kafka [1] and JMS [2] > connectors. In the existing connectors, connections are created and > closed per message which gives the performance issue. I have improved the > Kafka connector with configurable connection pool parameter. When > publishing the messages, the maximum pool size parameter value can be > changed in the connector configuration. Now the implementation with > connection pool gives better performance. > > The following results are with connection pool implementation. > Average throughput - 4980/s > > > *Threads & Pool Size* *Messages per a Thread* *No of Messages* *A Message > Size(byte)* > *Throughput (/s)* > 10 > 500 5,000 106 3728 > 20 500 10,000 106 4757 > 100 > 2500 250,000 106 5283 > 100 1 1,000,000 106 4920 > > > The following results were without connection pool implementation. > Average throughput - 2767/s > > *Threads* *Messages per a Thread* *No of Messages* *A Message Size(byte)* > *Throughput (/s)* > 10 500 5,000 106 1590 > 20 500 10,000 106 2251 > 100 250 25,000 106 2940 > 1,000 1500 1,500,000 106 2780 > In my git repo [3], I have committed the connection pool implementation > for Kafka connector. Please give your suggestion. > > [1] - https://wso2.org/jira/browse/ESBCONNECT-122 > [2] - https://wso2.org/jira/browse/ESBCONNECT-142 > [3] - https://github.com/RKathees/esb-connector-kafka/blob/ > master/src/main/java/org/wso2/carbon/connector/KafkaConnectionPoolManager. > java > > Thanks, > Kathees > -- > Kathees > Software Engineer, > email: kath...@wso2.com > mobile: +94772596173 <077%20259%206173> > -- Best Regards, Malaka Silva Senior Technical Lead 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/ <http://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] SMPP Connector Improvement
Hi Biruntha, There can be multiple gateways based on client configuration and for multiple tenants. We need to reuse only the sessions for the given service provider and tenant. I guess you are considering those as well? On Tue, Nov 22, 2016 at 12:14 PM, Biruntha Gnaneswaran <birun...@wso2.com> wrote: > Hi All, > > Currently i’m working on the SMPP connector improvement as described below: > >1. > >Query the status of the submitted message :- When message is send >using the SMPP protocol, SMSC returns a message reference (messageId). Then >we are able to query the SMSC for the delivery status of this message. >2. > >Maintain the SMPP session between multiple calls of send SMS operation >:- Current version of the connector creates new session for each sms. To >solve this problem, i create own connection pool to use it in the >multithreading environment by creating a ConcurrentLinkedQueue and push the >connections to that queue. Each time a thread requests a connection, >connection is popped out from queue. Once job is done, threads push >connection back to queue. If there are no connection in the queue, it will >create a new connection. > > > This improvement is regarding the jira [1] and [2]. > > [1] https://wso2.org/jira/browse/ESBCONNECT-120 > > [2] https://wso2.org/jira/browse/ESBCONNECT-121 > > Thanks, > Biruntha > > Associate Software Engineer > WSO2 > Email : birun...@wso2.com > Linkedin : https://lk.linkedin.com/in/biruntha > Mobile : +94773718986 > -- Best Regards, Malaka Silva Senior Technical Lead 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/ <http://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] SMPP inbound Endpoint
Hi Dimuthu, Connectors can only be used in mediation logic. Since listening should not be a part of mediation flow make sense to have an inbound extension for this. On Mon, Nov 21, 2016 at 2:01 PM, Dimuthu Leelarathne <dimut...@wso2.com> wrote: > Hi Biruntha, > > Is there a reason why it is not part of the existing SMPP connector, as it > makes sense to use it for sending and receiving SMSes. > > thanks, > Dimuthu > > > On Mon, Nov 21, 2016 at 1:56 PM, Biruntha Gnaneswaran <birun...@wso2.com> > wrote: > >> Hi Dimuthu, >> It is not part of the SMPP connector rather another extension. It is a >> custom Inbound like Twitter (Streaming connector). >> Thanks, >> >> Biruntha >> >> Associate Software Engineer >> WSO2 >> Email : birun...@wso2.com >> Linkedin : https://lk.linkedin.com/in/biruntha >> Mobile : +94773718986 >> >> On Mon, Nov 21, 2016 at 1:29 PM, Dimuthu Leelarathne <dimut...@wso2.com> >> wrote: >> >>> Hi Biruntha, >>> >>> Is this going to be part of the SMS connector or the ESB? >>> >>> thanks, >>> Dimuthu >>> >>> >>> On Mon, Nov 21, 2016 at 1:26 PM, Dimuthu Leelarathne <dimut...@wso2.com> >>> wrote: >>> >>>> >>>> >>>> On Mon, Nov 21, 2016 at 11:36 AM, Biruntha Gnaneswaran < >>>> birun...@wso2.com> wrote: >>>> >>>>> Hi All, >>>>> >>>>> I have planned to implement SMPP inbound endpoint to consume SMPP >>>>> messages from the SMSC as described below. The behaviour of this inbound >>>>> endpoint is Event Based. Because, inbound endpoint polls only once to >>>>> establish a connection with the SMSC and then It listens on a given port >>>>> for messages that are coming in. When they are available, it is injected >>>>> to >>>>> a given sequence. >>>>> >>>>> Architecture diagram of SMPP inbound Endpoint: >>>>> >>>>> >>>>> How SMPP Message receive from SMSC: >>>>> >>>>> The SMSC may deliver short messages to an ESME. In this case the ESME >>>>> must be connected to the SMSC as an ESME Receiver which is authorised to >>>>> receive short messages from the SMSC and to return the corresponding SMPP >>>>> message responses to the SMSC. The following diagram illustrates a typical >>>>> SMPP request/response sequence between an SMSC and an ESME, while >>>>> receiving >>>>> the message. >>>>> >>>>> >>>>> >>>>> >>>>> ESME - It is an external application that connects to a Short Message >>>>> Service Center (SMSC) to sending and/or receiving of SMS >>>>> <https://en.wikipedia.org/wiki/Short_message_service> messages. >>>>> >>>>> SMSC - It is to store, forward, convert and deliver Short Message >>>>> Service (SMS) messages. >>>>> >>>>> outbind - Outbind operation is to allow the SMSC signal an ESME to >>>>> originate a bind_receiver request to the SMSC while the SMSC had >>>>> outstanding messages for delivery to the ESME. >>>>> >>>>> bind_receiver - In order to receive messages, the ESME should respond >>>>> with a “bind_receiver” request to which the SMSC will reply with a >>>>> “bind_receiver_resp”. >>>>> >>>>> deliver_sm - The deliver_sm is issued by the SMSC to send a message >>>>> to an ESME. Using this command, the SMSC may route a short message to the >>>>> ESME for delivery. >>>>> >>>>> The exchange of SMPP request and response PDUs (Protocol Data Units) >>>>> between an SMSC and ESME Receiver may be implemented synchronously or >>>>> asynchronously as shown above. Thus the SMSC may send multiple deliver_sm >>>>> requests to the ESME, without synchronously waiting for the associated >>>>> response PDUs. >>>>> >>>>> Your comments and suggestions on this are highly appreciated. >>>>> >>>>> Thanks, >>>>> Biruntha >>>>> >>>>> Associate Software Engineer >>>>> WSO2 >>>>> Email : birun...@wso2.com >>>>> Linkedin : https://lk.linkedin.com/in/biruntha >>>>> Mobile : +94773718986 >>
Re: [Architecture] Common Extension Framework for IS Authenticators
Yes we should do that. @Kathees - Did we create a redmine for this already? On Thu, Nov 10, 2016 at 7:27 AM, Harsha Thirimanna <hars...@wso2.com> wrote: > Hi all, > Let's consider these common stuff to the connectors as a part of the > framework itself, because now connector team pack this common code module > with each connector and duplicate with each. From C5 onward we can remove > that from connector level and provide it from framework. > WDYT ? > > On Nov 8, 2016 1:50 PM, "Kathees Rajendram" <kath...@wso2.com> wrote: > > The common module is released with federated authenticator support in > multi factor authentication, locking user while applying wrong code in > other steps and tenant based configuration for application authentication > xml file. > > > Thanks, > Kathees > > On Fri, Nov 4, 2016 at 7:43 PM, Kathees Rajendram <kath...@wso2.com> > wrote: > >> Hi Malaka, >> >> This is the common module [1] for the authenticators. I will release to >> the nexus by Monday. >> >> [1] - https://github.com/wso2-extensions/identity-extension-utils >> >> Thanks, >> Kathees >> >> On Fri, Nov 4, 2016 at 9:41 AM, Malaka Silva <mal...@wso2.com> wrote: >> >>> Hi Kathees, >>> >>> Did we release this? If not please update once done.. >>> >>> On Sat, Oct 8, 2016 at 6:51 AM, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> My understanding here is what we try to do here is getting generic >>>> methods (Utils) to a common module. Nothing more. >>>> >>>> Dynamic sequence is something that should be supported from IS product >>>> framework in the future. >>>> >>>> On Fri, Oct 7, 2016 at 10:06 PM, Harsha Thirimanna <hars...@wso2.com> >>>> wrote: >>>> >>>>> This is kind of dynamic sequence bases on different factors like per >>>>> user , per group , right ? >>>>> Do you guys have concrete plan for this ? Then shall we discuss this >>>>> design before jump to the code ? >>>>> >>>>> *Harsha Thirimanna* >>>>> Associate Tech Lead | WSO2 >>>>> >>>>> Email: hars...@wso2.com >>>>> Mob: +94715186770 >>>>> Blog: http://harshathirimanna.blogspot.com/ >>>>> Twitter: http://twitter.com/harshathirimann >>>>> Linked-In: linked-in: http://www.linkedin.com/pub/ha >>>>> rsha-thirimanna/10/ab8/122 >>>>> <http://wso2.com/signature> >>>>> >>>>> On Fri, Oct 7, 2016 at 12:10 PM, Kathees Rajendram <kath...@wso2.com> >>>>> wrote: >>>>> >>>>>> Thanks for the comments and suggestions. >>>>>> >>>>>> The subject may be mislead. We need to create a utility component >>>>>> with common use cases. Basically we are providing generalized component >>>>>> and >>>>>> the common use cases are applicable for most of authenticators. >>>>>> >>>>>> As you said, alternative authentication flow is not in authenticator >>>>>> level and a use case for IS framework is, if we configure a >>>>>> authenticator flow for particular SP, that will be applicable for all >>>>>> users. Based on the user role or the policy, we need to have the a >>>>>> authentication access model. For example:- For particular user group, we >>>>>> need to enable two factor authenticator (Basic + SMS OTP), for other user >>>>>> group, we need to have Basic + other factor (Basic + RSA or Token2) and >>>>>> for some other user group, we need basic or social login. This should be >>>>>> configurable. >>>>>> >>>>>> We are building common use cases for the authenticators [1]. Please >>>>>> add if anything, we can include in authentication level. >>>>>> >>>>>> [1] - https://store.wso2.com/store/assets/isconnector/list >>>>>> >>>>>> Thanks, >>>>>> Kathees >>>>>> >>>>>> On Thu, Oct 6, 2016 at 2:43 PM, Ishara Karunarathna <isha...@wso2.com >>>>>> > wrote: >>>>>> >>>>>>> Hi Malaka. >>>>>>> >>>>>>> On Thu, Oct 6, 2016 at 12:25 PM, Malaka Silva <mal...@wso2.com> >>>>>>> wrote: >&g
Re: [Architecture] Rewriting Google Spreadsheet Connector for Google Sheets API Version v4
can also be used to remove columns, and remove part >>of a row or column >>- >> >>updateDimensionProperties using batch request :- Adjust column width or >> row height >> >>- >> >>autoResizeDimensions using batch request :– Request turns on automatic >> resizing of columns >> >>- >> >>insertDimension using batch request :- Insert an empty row or column >> >>- >> >>moveDimension using batch request :- Move a row or column >> >>- >> >>sortRange using batch request :- Sort a range with multiple sorting >> specifications >> >> >> *Working with Cell-based feeds* >> >>- >> >>Retrieve cell data or multiple ranges of cell data :– version 3 can >>only return cell contents as input values (as would be entered by a user >> at >>a keyboard) and/or the outputs of formula (if numeric). But version 4 >>grants full access to values, formulas, formatting, hyperlinks, data >>validation, and other properties. >>- >> >>Edit content of a cell >>- >> >>Edit content of multiple cell using batch request >> >> I have attached [3] my milestone plan for the Google Spreadsheet >> Connector. >> >> [1] https://developers.google.com/google-apps/spreadsheets/?hl=en[2] >> https://developers.google.com/sheets/guides/concepts >> [3] >> https://docs.google.com/spreadsheets/d/1DvemfUFwBo4JHrbWyNpcpqMQQ1SoVo3ag3Q9tl9Pmuw/edit#gid=0 >> >> Thanks, >> >> Biruntha >> >> Associate Software Engineer >> WSO2 >> Email : birun...@wso2.com >> Linkedin : https://lk.linkedin.com/in/biruntha >> Mobile : +94773718986 >> > > -- Best Regards, Malaka Silva Senior Technical Lead 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/ <http://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] Versioning support for ESB artifacts
Hi Amjadh , Thx for the detail explanation. I am bit unclear why we should do like this. Can you explain a use case where we have to use the above versioning. The way I see this is we are simple creating a new artifact? Typically we get the requirement to support versioning with Carbon Applications. I guess this is not covered as part of this? On Mon, Nov 7, 2016 at 9:39 AM, Amjadh Ifthikar <amj...@wso2.com> wrote: > > Hi all, > > I am currently working on the project “Versioning support for ESB > artifacts”. I have completed implementing the solution in wso2 synapse and > also done necessary changes in the developer studio as well. According to > the project, proxy service and sequence artifacts will be deployed and > dispatched as follows. > > Proxy service deployment > > A versioned proxy service should be defined as follows. > > transports="https http" version="1.0.0" isDefault=”true”> > > The defined version will be concatenated with the proxy name to generate a > unique id for the proxy service. The proxy service will be deployed using > this unique id. > > Eg. testproxy/1.0.0 > > The isDefault attribute helps the user to name the respective version as > the default version.(See proxy service dispatching for effect of isDefault) > > If there is no version attribute defined, the proxy is deployed by its > name. This measure is taken to support backward compatibility. > > Proxy service dispatching > > A proxy service should be referred in a request as follows. > > The following requests are processed and the proxy service is dispatched. > > >- > >http://localhost:8280/services/StockQuoteProxy/1.0.0 or >http://localhost:8280/services/StockQuoteProxy/1.0. >0.StockQuoteProxy/1.0.0HttpSoap11Endpoint > > <http://localhost:8280/services/StockQuoteProxy/1.0.0.StockQuoteProxy/1.0.0HttpSoap11Endpoint> > > > If the request is sent as follows, the proxy service with the respective > version is deployed. > > >- > >http://localhost:8280/services/StockQuoteProxy or >http://localhost:8280/services/StockQuoteProxy.StockQuoteProxy/ >HttpSoap11Endpoint > > <http://localhost:8280/services/StockQuoteProxy.StockQuoteProxy/HttpSoap11Endpoint> > > > If a service is not found for the above request, > > 1). If the user have defined a proxy service with the attribute isDefault > = “true” with the name requested, it will be dispatched. > > 2).If no axis service is found, it will see if there is only one proxy > service containing the name provided. If so it is dispatched. > > 2). If there are many proxy services with the given name, the service with > the highest version is dispatched. > > Serializing an artifact > > When serializing an artifact, both name and version can be taken from the > artifact object to create the serialized artifact. > > Sequence deployment > > Ideally sequence deployment should be as follows. > > http://ws.apache.org/ > ns/synapse" version=”1.0.0”> > > The defined sequence name will be concatenated with the version to create > a unique id. > > Eg.test/1.0.0 > > The deployed sequence will be added to the local registry with this unique > id as the key. > > Sequence dispatching > > A versioned sequence should be referenced as follows. > > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, Malaka Silva Senior Technical Lead 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/ <http://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] Improvement to Amazon S3 connector
Thx for the update Yashothara. Is the feature released to store and documented? On Sun, Nov 6, 2016 at 11:33 AM, Yashothara Shanmugarajah < yashoth...@wso2.com> wrote: > Hi all, > > I have done the improvement with getting Object with signed URL. As far as > I know there is no options to do other methods by using signed URL. > > Thanks. > > Best Regards, > Yashothara.S > Software Engineer > WSO2 > http://wso2.com > https://wso2.com/signature > <https://www.google.com/url?q=https%3A%2F%2Fwso2.com%2Fsignature=D=1=AFQjCNFqSCK3YQC9g0l53f6yjvsVrxRHXg> > > On Mon, Oct 24, 2016 at 5:04 PM, Yashothara Shanmugarajah < > yashoth...@wso2.com> wrote: > >> Hi all, >> >> Amazon S3 provides a simple web services interface that can be used to >> store and retrieve any amount of data, at any time, from anywhere on the >> web.There is already amazon S3 connector in store. Now I am doing >> improvement Creating the URL signing for S3 connector [1]. Here I focused >> to create signed URL using policy with using cloud Key pairs. >> >> [1] https://wso2.org/jira/browse/ESBCONNECT-123 >> >> Thanks. >> >> Best Regards, >> Yashothara.S >> Software Engineer >> WSO2 >> http://wso2.com >> https://wso2.com/signature >> <https://www.google.com/url?q=https%3A%2F%2Fwso2.com%2Fsignature=D=1=AFQjCNFqSCK3YQC9g0l53f6yjvsVrxRHXg> >> > > -- Best Regards, Malaka Silva Senior Technical Lead 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/ <http://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] ESB connector auto generation tool
Hi Rajjaz,
So phrase 1 is to complete automation of Salesforce custom integration with
ESB.
Attaching the configs may not be clear for some one to followup. Can you
document the steps how we can automate this integration?
On Fri, Nov 4, 2016 at 6:41 PM, Rajjaz Mohammed <raj...@wso2.com> wrote:
> Hi All,
>
> I have done the first face of the development and test the connector with
> ESB and it's works as expected. Here with i attached the apex class, WSDL
> ,generated connector source code and the connector zip.
>
> *Authentication is only support for salesforce in current development .
> Later we will extend to other products.
>
> On Fri, Oct 14, 2016 at 6:26 AM, Malaka Silva <mal...@wso2.com> wrote:
>
>> I think we should have both options and user can control the behavior.
>>
>> Also we should automate init method for known use cases.
>>
>> On Thu, Oct 13, 2016 at 4:08 PM, Keerthika Mahendralingam <
>> keerth...@wso2.com> wrote:
>>
>>> IMO we need to go ahead with the first approach since there may be some
>>> cases we need to have some additional properties, headers, or host, etc.
>>> which are not common for all connectors. These are depend on the backend
>>> service.
>>>
>>>
>>> Thanks,
>>> Keerthika.
>>>
>>> On Thu, Oct 13, 2016 at 3:55 PM, Rajjaz Mohammed <raj...@wso2.com>
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> We have two options in the output of auto-generation tool.
>>>>
>>>>1. source code of the connector
>>>>2. connector zip
>>>>
>>>> If we generate connector zip file directly we can reduce the manual
>>>> works but if we generate the source code from this tool
>>>>
>>>>- add init method manually for authentication
>>>>- modify some special cases like adding DISABLE_CHUNKING etc.
>>>>- integration test
>>>>
>>>> WDYT?
>>>>
>>>> On Wed, Oct 12, 2016 at 3:28 PM, Malaka Silva <mal...@wso2.com> wrote:
>>>>
>>>>> Yes Authorization is bit tricky and specific to vendors. So we can
>>>>> have predefined templates (eg: Salesforce custom web services) and make
>>>>> this plug-able?
>>>>>
>>>>> On Wed, Oct 12, 2016 at 2:44 PM, Rajjaz Mohammed <raj...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> I have done some testings on this area for that I created an apex
>>>>>> class[1] to create an account in salesforce and tested with simple java
>>>>>> client using WSDL file and it works fine and can able to extract the
>>>>>> common
>>>>>> information from WSDL (attached).
>>>>>>
>>>>>> Our next step will create the connector based on the information
>>>>>> extracted from WSDL. But we can only create the synapse template
>>>>>> configuration which is general. Another challenge is the authentication
>>>>>> part so we plan to create the init as the separate module because it
>>>>>> will
>>>>>> not same to all connectors.
>>>>>>
>>>>>> [1]
>>>>>>
>>>>>> global class ConnectorAutomation{
>>>>>> global class RequestClass{
>>>>>> webService String accountName;
>>>>>> }
>>>>>> global class ResponseClass{
>>>>>> webService String responseResultID;
>>>>>> webService String responseResultName;
>>>>>> webService String responseResultRecordType;
>>>>>> }
>>>>>> webService static ResponseClass addAccount(String name){
>>>>>> Account acct = new Account();
>>>>>> acct.Name = name;
>>>>>> insert acct;
>>>>>> ResponseClass resClass = new ResponseClass();
>>>>>> resClass.responseResultID = acct.Id;
>>>>>> resClass.responseResultName = acct.Name;
>>>>>> resClass.responseResultRecordType = acct.AccountNumber;
>>>>>> return resClass;
>>>>>> }
>>>>>> }
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Sep 21, 2016 at 10:41 AM, Mala
Re: [Architecture] Rewriting MailChimp Connector
Hi Vivekananthan, Please check if it make sense to remove those? I am just suggesting :) On Mon, Oct 24, 2016 at 4:55 PM, Vivekananthan Sivanayagam < vivekanant...@wso2.com> wrote: > Noted Malaka. > > Vivekananthan Sivanayagam > Associate Software Engineer | WSO2 > E:vivekanant...@wso2.com > M:+94752786138 > > On Mon, Oct 24, 2016 at 4:42 PM, Malaka Silva <mal...@wso2.com> wrote: > >> Hi Vivekanathan, >> >> I guess we can skip Folders and Templates >> for the initial version? >> >> I think those won't be used in most of the use cases? >> >> On Mon, Oct 24, 2016 at 3:37 PM, Vivekananthan Sivanayagam < >> vivekanant...@wso2.com> wrote: >> >>> Hi All, >>> >>> MailChimp is an online email marketing solution to manage subscribers, >>> send emails, and track results. An existing connector was developed to >>> support 2.0 [1] and MailChimp API v3.0 [2]is now live. The current version >>> (2.0) will no longer be supported after 2016. >>> >>> I am going to implement the following methods for the newer version. >>> >>> *Campaigns* >>> >>>- createCampaign >>>- getAllCampaigns >>>- getCampaign >>>- deleteCampaign >>>- updateCampaign >>>- getSendCheckList >>>- addCampaignFeedback >>>- getAllCampaignFeedbacks >>>- getCampaignFeedback >>>- updateCampaignFeedback >>>- deleteCampaignFeedback >>>- searchCampaign >>>- getCampaignContent >>> >>> *Folders* >>> >>>- createCampaignFolder >>>- getCampaignFolder >>>- getAllCampaignFolders >>>- createTemplateFolder >>>- getAllTemplateFolders >>>- getTemplateFolder >>> >>> *Lists* >>> >>>- createList >>>- getAllLists >>>- getList >>>- updateList >>>- deleteList >>>- getAllListAbuseReports >>>- getListActivity >>>- SubscribeOrUnsubscribeListMembers >>> >>> *Reports* >>> >>>- getReport >>>- getAllReports >>>- getCampaignAbuseReport >>>- getAllCampaignAbuseReports >>>- getAllClickReports >>>- getClickReport >>>- getLocation >>> >>> *Templates* >>> >>>- createTemplate >>>- getAllTemplates >>>- getTemplate >>>- updateTemplate >>>- deleteTemplate >>>- getDefaultContent >>> >>> [1] https://apidocs.mailchimp.com/api/2.0/ >>> [2] http://developer.mailchimp.com/documentation/mailchimp/r >>> eference/overview/ >>> >>> Thanks, >>> >>> Vivekananthan Sivanayagam >>> Associate Software Engineer | WSO2 >>> E:vivekanant...@wso2.com >>> M:+94752786138 >>> >> >> >> >> -- >> >> Best Regards, >> >> Malaka Silva >> Senior Technical Lead >> 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/ >> <http://wso2.com/about/team/malaka-silva/> >> https://store.wso2.com/store/ >> >> Don't make Trees rare, we should keep them with care >> > > -- Best Regards, Malaka Silva Senior Technical Lead 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/ <http://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] Rewriting MailChimp Connector
Hi Vivekanathan, I guess we can skip Folders and Templates for the initial version? I think those won't be used in most of the use cases? On Mon, Oct 24, 2016 at 3:37 PM, Vivekananthan Sivanayagam < vivekanant...@wso2.com> wrote: > Hi All, > > MailChimp is an online email marketing solution to manage subscribers, > send emails, and track results. An existing connector was developed to > support 2.0 [1] and MailChimp API v3.0 [2]is now live. The current version > (2.0) will no longer be supported after 2016. > > I am going to implement the following methods for the newer version. > > *Campaigns* > >- createCampaign >- getAllCampaigns >- getCampaign >- deleteCampaign >- updateCampaign >- getSendCheckList >- addCampaignFeedback >- getAllCampaignFeedbacks >- getCampaignFeedback >- updateCampaignFeedback >- deleteCampaignFeedback >- searchCampaign >- getCampaignContent > > *Folders* > >- createCampaignFolder >- getCampaignFolder >- getAllCampaignFolders >- createTemplateFolder >- getAllTemplateFolders >- getTemplateFolder > > *Lists* > >- createList >- getAllLists >- getList >- updateList >- deleteList >- getAllListAbuseReports >- getListActivity >- SubscribeOrUnsubscribeListMembers > > *Reports* > >- getReport >- getAllReports >- getCampaignAbuseReport >- getAllCampaignAbuseReports >- getAllClickReports >- getClickReport >- getLocation > > *Templates* > >- createTemplate >- getAllTemplates >- getTemplate >- updateTemplate >- deleteTemplate >- getDefaultContent > > [1] https://apidocs.mailchimp.com/api/2.0/ > [2] http://developer.mailchimp.com/documentation/ > mailchimp/reference/overview/ > > Thanks, > > Vivekananthan Sivanayagam > Associate Software Engineer | WSO2 > E:vivekanant...@wso2.com > M:+94752786138 > -- Best Regards, Malaka Silva Senior Technical Lead 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/ <http://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] ESB connector auto generation tool
I think we should have both options and user can control the behavior.
Also we should automate init method for known use cases.
On Thu, Oct 13, 2016 at 4:08 PM, Keerthika Mahendralingam <
keerth...@wso2.com> wrote:
> IMO we need to go ahead with the first approach since there may be some
> cases we need to have some additional properties, headers, or host, etc.
> which are not common for all connectors. These are depend on the backend
> service.
>
>
> Thanks,
> Keerthika.
>
> On Thu, Oct 13, 2016 at 3:55 PM, Rajjaz Mohammed <raj...@wso2.com> wrote:
>
>> Hi All,
>>
>> We have two options in the output of auto-generation tool.
>>
>>1. source code of the connector
>>2. connector zip
>>
>> If we generate connector zip file directly we can reduce the manual works
>> but if we generate the source code from this tool
>>
>>- add init method manually for authentication
>>- modify some special cases like adding DISABLE_CHUNKING etc.
>>- integration test
>>
>> WDYT?
>>
>> On Wed, Oct 12, 2016 at 3:28 PM, Malaka Silva <mal...@wso2.com> wrote:
>>
>>> Yes Authorization is bit tricky and specific to vendors. So we can have
>>> predefined templates (eg: Salesforce custom web services) and make this
>>> plug-able?
>>>
>>> On Wed, Oct 12, 2016 at 2:44 PM, Rajjaz Mohammed <raj...@wso2.com>
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> I have done some testings on this area for that I created an apex
>>>> class[1] to create an account in salesforce and tested with simple java
>>>> client using WSDL file and it works fine and can able to extract the common
>>>> information from WSDL (attached).
>>>>
>>>> Our next step will create the connector based on the information
>>>> extracted from WSDL. But we can only create the synapse template
>>>> configuration which is general. Another challenge is the authentication
>>>> part so we plan to create the init as the separate module because it will
>>>> not same to all connectors.
>>>>
>>>> [1]
>>>>
>>>> global class ConnectorAutomation{
>>>> global class RequestClass{
>>>> webService String accountName;
>>>> }
>>>> global class ResponseClass{
>>>> webService String responseResultID;
>>>> webService String responseResultName;
>>>> webService String responseResultRecordType;
>>>> }
>>>> webService static ResponseClass addAccount(String name){
>>>> Account acct = new Account();
>>>> acct.Name = name;
>>>> insert acct;
>>>> ResponseClass resClass = new ResponseClass();
>>>> resClass.responseResultID = acct.Id;
>>>> resClass.responseResultName = acct.Name;
>>>> resClass.responseResultRecordType = acct.AccountNumber;
>>>> return resClass;
>>>> }
>>>> }
>>>>
>>>>
>>>>
>>>> On Wed, Sep 21, 2016 at 10:41 AM, Malaka Silva <mal...@wso2.com> wrote:
>>>>
>>>>> Yes Kasun this is what our end goal is. We are starting this with soap
>>>>> based services. Also great if you can share any work done to speed up our
>>>>> r
>>>>>
>>>>> @Ajanthan
>>>>> - Yes we are currently planning to have this a command line tool,
>>>>> however this is not yet finalized.
>>>>>
>>>>> On Wed, Sep 21, 2016 at 2:09 AM, Kasun Indrasiri <ka...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Malaka,
>>>>>>
>>>>>> We did a PoC project on generating a connector based on a given
>>>>>> Swagger definition. Is this a similar requirement?
>>>>>>
>>>>>> On Tue, Sep 20, 2016 at 10:51 AM, Ajanthan Balachandran <
>>>>>> ajant...@wso2.com> wrote:
>>>>>>
>>>>>>> What do you mean by a tool? Is it command line tool or maven plugin
>>>>>>> or eclipse plugin?
>>>>>>>
>>>>>>> On Fri, Sep 9, 2016 at 2:07 AM, Rajjaz Mohammed <raj...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>>
&
Re: [Architecture] ESB connector auto generation tool
Yes Authorization is bit tricky and specific to vendors. So we can have
predefined templates (eg: Salesforce custom web services) and make this
plug-able?
On Wed, Oct 12, 2016 at 2:44 PM, Rajjaz Mohammed <raj...@wso2.com> wrote:
> Hi All,
>
> I have done some testings on this area for that I created an apex class[1]
> to create an account in salesforce and tested with simple java client using
> WSDL file and it works fine and can able to extract the common information
> from WSDL (attached).
>
> Our next step will create the connector based on the information extracted
> from WSDL. But we can only create the synapse template configuration which
> is general. Another challenge is the authentication part so we plan to
> create the init as the separate module because it will not same to all
> connectors.
>
> [1]
>
> global class ConnectorAutomation{
> global class RequestClass{
> webService String accountName;
> }
> global class ResponseClass{
> webService String responseResultID;
> webService String responseResultName;
> webService String responseResultRecordType;
> }
> webService static ResponseClass addAccount(String name){
> Account acct = new Account();
> acct.Name = name;
> insert acct;
> ResponseClass resClass = new ResponseClass();
> resClass.responseResultID = acct.Id;
> resClass.responseResultName = acct.Name;
> resClass.responseResultRecordType = acct.AccountNumber;
> return resClass;
> }
> }
>
>
>
> On Wed, Sep 21, 2016 at 10:41 AM, Malaka Silva <mal...@wso2.com> wrote:
>
>> Yes Kasun this is what our end goal is. We are starting this with soap
>> based services. Also great if you can share any work done to speed up our
>> r
>>
>> @Ajanthan
>> - Yes we are currently planning to have this a command line tool,
>> however this is not yet finalized.
>>
>> On Wed, Sep 21, 2016 at 2:09 AM, Kasun Indrasiri <ka...@wso2.com> wrote:
>>
>>> Hi Malaka,
>>>
>>> We did a PoC project on generating a connector based on a given Swagger
>>> definition. Is this a similar requirement?
>>>
>>> On Tue, Sep 20, 2016 at 10:51 AM, Ajanthan Balachandran <
>>> ajant...@wso2.com> wrote:
>>>
>>>> What do you mean by a tool? Is it command line tool or maven plugin or
>>>> eclipse plugin?
>>>>
>>>> On Fri, Sep 9, 2016 at 2:07 AM, Rajjaz Mohammed <raj...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>> Hi,
>>>>>>
>>>>>> We have currently 150+ connectors in store
>>>>>> <https://store.wso2.com/store/>. Using those we can easily build
>>>>>> integration use cases with WSO2 ESB.
>>>>>>
>>>>>> However there are some apis that resides on premises and specific to
>>>>>> some users. If we need to integrate such services, we either need to
>>>>>> manually do the integration with ESB or develop a connector and use it.
>>>>>>
>>>>>> The idea of this project is to automate the development of connectors
>>>>>> that makes the integration tasks more productive.
>>>>>>
>>>>>> So we are planning to start this with soap based connectors and move
>>>>>> to rest based support later.
>>>>>>
>>>>>> For soap based connector generation we basically need to parse the
>>>>>> wsdl and generate a connector operation per soap operation.
>>>>>>
>>>>>> For that we can use WSDL4J. Using this we can get the required
>>>>>> operations and request/response messages required. Using this information
>>>>>> we can build the connector operations.(Sequence Templates)
>>>>>>
>>>>>> eg:
>>>>>> String wsdlPath = "/home/wso2/Desktop/ConnectorTest.wsdl";
>>>>>> WSDLReader reader = javax.wsdl.factory.WSDLFactory
>>>>>> .newInstance().newWSDLReader();
>>>>>> javax.wsdl.Definition defn = reader.readWSDL(wsdlPath);
>>>>>>
>>>>>> Map tmp =
>>>>>> defn.getAllServices();
>>>>>>
>>>>>> for(javax.xml.namespace.QName key:tmp.keySet()){
>>>>>> ServiceImpl serviceImpl = tmp.get(key);
>>>>>> Map <String,PortImpl> mPorts = serviceImpl.getPorts();
>>>>>
Re: [Architecture] Speedup traffic serving process in scalable/ containerized deployment
Hi Sanjeewa, My understanding is gateway pool is not tenant specific and will not be returned but rather terminated? On Mon, Oct 10, 2016 at 8:01 PM, Sanjeewa Malalgoda <sanje...@wso2.com> wrote: > Hi All, > Starting this mail thread to continue discussion on "speedup instance > activate time when we move ahead with container based deployments". As of > now all of us are working on speedup server start time and deploy instances > on demand with the help of load balancer. Please note that this is not > alternative/replacement to effort on starting server faster(2 secs or > less). This is about make request serving more faster even with small > server startup time. > > When we do container based deployment standard approach we discussed so > far was, > >- At the first request check the tenant and service from URL and do >lookup for running instances. >- If matching instance available route traffic to that. >- Else spawn new instance using template(or image). When we spawn >this new instance we need to let it know what is the current tenant and >data sources, configurations it should use. >- Then route requests to new node. >- After some idle time this instance may terminate. > > *Suggestion* > If we maintain hot pool(started and ready to serve requests) of servers > for each server type(API Gateway, Identity Server etc) then we can cutoff > server startup time + IaaS level spawn time from above process. Then when > requests comes to wso2.com tenants API Gateway we can pick instance from > gateway instance pool and set wso2.com tenant context and data source > using service call(assuming setting context and configurations is much > faster). > > *Implementation* > For this we need to implement some plug-in to instance spawn process. > Then instead of spawning new instance it will pick one instance from the > pool and configure it to behave as specific tenant. > For this each instance running in pool can open up port, so load balancer > or scaling component can call it and tell what is the tenant and > configurations. > Once it configured server close that configuration port and start traffic > serving. > After some idle time this instance may terminate. > > This approach will help us if we met following condition. > (Instance loading time + Server startup time + Server Lookup) *>* (Server > Lookup + Loading configuration and tenant of running server from external > call) > > Any thoughts on this? > > Thanks, > sanjeewa. > -- > > *Sanjeewa Malalgoda* > WSO2 Inc. > Mobile : +94713068779 > > <http://sanjeewamalalgoda.blogspot.com/>blog :http://sanjeewamalalgoda. > blogspot.com/ <http://sanjeewamalalgoda.blogspot.com/> > > > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, Malaka Silva Senior Technical Lead 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/ <http://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] Common Extension Framework for IS Authenticators
My understanding here is what we try to do here is getting generic methods (Utils) to a common module. Nothing more. Dynamic sequence is something that should be supported from IS product framework in the future. On Fri, Oct 7, 2016 at 10:06 PM, Harsha Thirimanna <hars...@wso2.com> wrote: > This is kind of dynamic sequence bases on different factors like per user > , per group , right ? > Do you guys have concrete plan for this ? Then shall we discuss this > design before jump to the code ? > > *Harsha Thirimanna* > Associate Tech Lead | WSO2 > > Email: hars...@wso2.com > Mob: +94715186770 > Blog: http://harshathirimanna.blogspot.com/ > Twitter: http://twitter.com/harshathirimann > Linked-In: linked-in: http://www.linkedin.com/pub/ > harsha-thirimanna/10/ab8/122 > <http://wso2.com/signature> > > On Fri, Oct 7, 2016 at 12:10 PM, Kathees Rajendram <kath...@wso2.com> > wrote: > >> Thanks for the comments and suggestions. >> >> The subject may be mislead. We need to create a utility component with >> common use cases. Basically we are providing generalized component and the >> common use cases are applicable for most of authenticators. >> >> As you said, alternative authentication flow is not in authenticator >> level and a use case for IS framework is, if we configure a >> authenticator flow for particular SP, that will be applicable for all >> users. Based on the user role or the policy, we need to have the a >> authentication access model. For example:- For particular user group, we >> need to enable two factor authenticator (Basic + SMS OTP), for other user >> group, we need to have Basic + other factor (Basic + RSA or Token2) and >> for some other user group, we need basic or social login. This should be >> configurable. >> >> We are building common use cases for the authenticators [1]. Please add >> if anything, we can include in authentication level. >> >> [1] - https://store.wso2.com/store/assets/isconnector/list >> >> Thanks, >> Kathees >> >> On Thu, Oct 6, 2016 at 2:43 PM, Ishara Karunarathna <isha...@wso2.com> >> wrote: >> >>> Hi Malaka. >>> >>> On Thu, Oct 6, 2016 at 12:25 PM, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> >>>> >>>> On Thu, Oct 6, 2016 at 10:31 AM, Ishara Karunarathna <isha...@wso2.com> >>>> wrote: >>>> >>>>> Hi Malaka. >>>>> >>>>> On Thu, Oct 6, 2016 at 9:42 AM, Malaka Silva <mal...@wso2.com> wrote: >>>>> >>>>>> Hi Ishara, >>>>>> >>>>>> I guess the subject is bit misleading. What we are trying to achieve >>>>>> here is to put common functionalities used by all / most of the IS >>>>>> extensions. >>>>>> >>>>>> For example we have done a improvement to totp to support multi >>>>>> tenancy. These logic's are built into totp and that is wrong. So we are >>>>>> planning to have these in this module. >>>>>> >>>>> I think here you are trying to implement utility component to be used >>>>> in authenticates. >>>>> >>>> yes >>>> >>>> >>> Then +1 for have utility component with common usecases. >>> >>>> >>>>>> On Thu, Oct 6, 2016 at 9:29 AM, Ishara Karunarathna <isha...@wso2.com >>>>>> > wrote: >>>>>> >>>>>>> Hi kathees, >>>>>>> >>>>>>> On Wed, Oct 5, 2016 at 2:12 PM, Kathees Rajendram <kath...@wso2.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi All, >>>>>>>> >>>>>>>> I am working on creating common extension framework for IS >>>>>>>> authenticators. >>>>>>>> >>>>>>> Can you explain more on this. What is the existing problem and how >>>>>>> its going to fix this framework. >>>>>>> >>>>>>> At the moment we have authentication framework where we mainly >>>>>>> handle the authentication related operations and Authenticators >>>>>>> are one of the connectors that can be plugged in to authentication >>>>>>> framework. >>>>>>> So why do we need another framework for authenticates. >>>>>>> >>>>>
Re: [Architecture] Supporting per tenant Mutual SSL in API Gateway
On Thu, Oct 6, 2016 at 10:44 AM, Sajith Kariyawasam <saj...@wso2.com> wrote: > Hi all, > > We were discussing ways of implementing the above feature. > > As of now, for supporting mutual SSL in API Gateway, dynamic SSL Profiles > are used [1 > <http://ishara-cooray.blogspot.com/2016/07/how-to-secure-your-backend-services-and.html> > ][2 > <http://jagathsa.blogspot.com/2015/09/dynamic-ssl-profiles-in-wso2-esb-490.html> > ] > There, keystores and truststores can be configured dynamically per backend > endpoint (ip and port). > > But the limitation in here is, those cannot configured per-tenant basis as > SSL profile is bound to a transport and the transports are not tenant aware. > > As we can see, we have following two options. > > 1. Enhance the transports to be tenant aware, so that per tenant profiles > can be maintained. > SSL handshake happens at the initial stage of the communication and the transport will not become optimized with this. > or > > 2. Deploying per tenant API Gateway nodes > Container per tenant make sense. > > > Any thoughts on those are highly appreciated. > > [1] http://ishara-cooray.blogspot.com/2016/07/how-to-secure- > your-backend-services-and.html > [2] http://jagathsa.blogspot.com/2015/09/dynamic-ssl-profiles- > in-wso2-esb-490.html > > > Thanks, > Sajith > > -- > Sajith Kariyawasam > *Associate Tech Lead* > *WSO2 Inc.; http://wso2.com <http://wso2.com/>* > *Committer and PMC member, Apache Stratos * > *AMIE (SL)* > *Mobile: 0772269575 <0772269575>* > > _______ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, Malaka Silva Senior Technical Lead 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/ <http://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] Common Extension Framework for IS Authenticators
On Thu, Oct 6, 2016 at 10:31 AM, Ishara Karunarathna <isha...@wso2.com> wrote: > Hi Malaka. > > On Thu, Oct 6, 2016 at 9:42 AM, Malaka Silva <mal...@wso2.com> wrote: > >> Hi Ishara, >> >> I guess the subject is bit misleading. What we are trying to achieve >> here is to put common functionalities used by all / most of the IS >> extensions. >> >> For example we have done a improvement to totp to support multi tenancy. >> These logic's are built into totp and that is wrong. So we are planning to >> have these in this module. >> > I think here you are trying to implement utility component to be used in > authenticates. > yes > >> On Thu, Oct 6, 2016 at 9:29 AM, Ishara Karunarathna <isha...@wso2.com> >> wrote: >> >>> Hi kathees, >>> >>> On Wed, Oct 5, 2016 at 2:12 PM, Kathees Rajendram <kath...@wso2.com> >>> wrote: >>> >>>> Hi All, >>>> >>>> I am working on creating common extension framework for IS >>>> authenticators. >>>> >>> Can you explain more on this. What is the existing problem and how its >>> going to fix this framework. >>> >>> At the moment we have authentication framework where we mainly handle >>> the authentication related operations and Authenticators >>> are one of the connectors that can be plugged in to authentication >>> framework. >>> So why do we need another framework for authenticates. >>> >>> And I think following items also more specific to authenticates and I >>> don't think we can use them in all authenticates. >>> >>> Thanks, >>> Ishara >>> >>> >>> >>>> >>>> In extension common framework, I am planing to add the following >>>> features which can be reused in authenticators. >>>> >>>>- Federated authenticator support - Currently, two-factor >>>>authenticator supports basic authenticator in the first step and >>>> federated >>>>authentication in first factor supports only in TOTP authenticator. I am >>>>planing to add this federated authenticator support in common framework >>>> so >>>>we can reuse in all two factor authenticators. >>>> >>>> >>>>- Account Lock/Unlock - Currently, we don't have any limit for >>>>applying the code in two factor authenticator authentication. I am >>>> planing >>>>to add Lock a user account functionality [1] when configurable number of >>>>applying code attempts are exceeded in second step of authentication. >>>> >>>> >>>>- Alternative authentication steps >>>> >>>> Backup Phone no - Add backup phone so user can still sign >>>> in if user lose phone and add alternative step as backup phone no. >>>> Backup codes - These printable one-off pass codes allow >>>> you to sign in when away from your phone, like when you’re traveling. >>>> Currently We have similar >>>> functionality in SMS OTP authenticator,We will move to IS authenticator >>>> common framework which can be used in other authenticators. >>>> >>> Is this specific to a authinticator? >> >> >> > Yes I think above listed stuff are specific to each authenticators. > For example if you think of Alternative authentication step, That > alternative mechanism should have some relation with the > the configured authenticators. > Actually if should not be a functionality of the authenticator this is > something we should implement introducing policy base > dynamic authentication flows. Then we should be able to configures > authenticates, alternative authenticates, Security levels etc. > with a policy. > >> >>>>- HOTP and TOTP algorithm based code generation - We can reuse OTP >>>>code generation in SMS [2] and Email OTP [3], TOTP [4] authenticators. >>>> >>>> >>>> Supporting muti tenancy should be added. >> >> > Normally we associate an authenticator to a SP in a given tenant so do we > need to handle tenancy in a authenticator level ? > No issues is how can we keep configuration bound to a tenant in local authinticators. Eg:- Keep configs for the super teanant in local file and per tenant in registry. > > Thanks, > Ishara > > >> Please let me know if yo
Re: [Architecture] Common Extension Framework for IS Authenticators
Hi Ishara, I guess the subject is bit misleading. What we are trying to achieve here is to put common functionalities used by all / most of the IS extensions. For example we have done a improvement to totp to support multi tenancy. These logic's are built into totp and that is wrong. So we are planning to have these in this module. On Thu, Oct 6, 2016 at 9:29 AM, Ishara Karunarathna <isha...@wso2.com> wrote: > Hi kathees, > > On Wed, Oct 5, 2016 at 2:12 PM, Kathees Rajendram <kath...@wso2.com> > wrote: > >> Hi All, >> >> I am working on creating common extension framework for IS authenticators. >> > Can you explain more on this. What is the existing problem and how its > going to fix this framework. > > At the moment we have authentication framework where we mainly handle the > authentication related operations and Authenticators > are one of the connectors that can be plugged in to authentication > framework. > So why do we need another framework for authenticates. > > And I think following items also more specific to authenticates and I > don't think we can use them in all authenticates. > > Thanks, > Ishara > > > >> >> In extension common framework, I am planing to add the following >> features which can be reused in authenticators. >> >>- Federated authenticator support - Currently, two-factor >>authenticator supports basic authenticator in the first step and federated >>authentication in first factor supports only in TOTP authenticator. I am >>planing to add this federated authenticator support in common framework so >>we can reuse in all two factor authenticators. >> >> >>- Account Lock/Unlock - Currently, we don't have any limit for >>applying the code in two factor authenticator authentication. I am planing >>to add Lock a user account functionality [1] when configurable number of >>applying code attempts are exceeded in second step of authentication. >> >> >>- Alternative authentication steps >> >> Backup Phone no - Add backup phone so user can still sign >> in if user lose phone and add alternative step as backup phone no. >> Backup codes - These printable one-off pass codes allow you >> to sign in when away from your phone, like when you’re traveling. >> Currently We have similar >> functionality in SMS OTP authenticator,We will move to IS authenticator >> common framework which can be used in other authenticators. >> > Is this specific to a authinticator? > >>- HOTP and TOTP algorithm based code generation - We can reuse OTP >>code generation in SMS [2] and Email OTP [3], TOTP [4] authenticators. >> >> >> Supporting muti tenancy should be added. > Please let me know if you have any concerns. >> >> [1] - https://docs.wso2.com/display/IS520/User+Account+Locking+and >> +Account+Disabling >> >> [2] - https://docs.wso2.com/display/ISCONNECTORS/Configuring+SMSOT >> P+Authenticator >> >> [3] - https://docs.wso2.com/display/ISCONNECTORS/Configuring+Email >> OTP+Authenticator >> >> [4] - https://docs.wso2.com/display/ISCONNECTORS/Configuring+TOT >> P+Authenticator >> >> Thanks, >> Kathees >> >> -- >> Kathees >> Software Engineer, >> email: kath...@wso2.com >> mobile: +94772596173 >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Ishara Karunarathna > Associate Technical Lead > WSO2 Inc. - lean . enterprise . middleware | wso2.com > > email: isha...@wso2.com, blog: isharaaruna.blogspot.com, mobile: > +94717996791 > > > > _______ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, Malaka Silva Senior Technical Lead 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/ <http://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] SurveyGizmo Connector
Hi Yashothara, You mean latest is v5 and we are doing the connector for that? If so this looks good. On Thu, Oct 6, 2016 at 8:30 AM, Yashothara Shanmugarajah < yashoth...@wso2.com> wrote: > Hi All, > > SurveyGizmo is a survey tool which used to analyze in-depth data > collection and report on and integrate it into business processes. > Automated analysis is done, so it is easy to see correlations, patterns, > and trends between questions. > > We can find API Documentation in https://apihelp.surveygizmo.com/help > <http://developers.freshdesk.com/api/> > > SurveyGizmo is REST based API. We can authenticate API using API key and > secret Key. > > There are 5 versions in this API. In intial versions we can authenticate > using username and password. But now we can authenticate using API key and > Secret Key. > > I have selected following methods for the implementation: > > *Campaigns* > > createCampaign: Create a new Campaign > > getCampaignById: Get the campaign by Id > > listCampaigns: List all campaigns for survey > > updateCampaign: Update or Copy an existing Campaign. > > > *Contacts* > > getContactListById: Get contact list by ID. > > listContactLists: List all contact lists. > > > *SurveyResponses* > > listResponses: List all responses to to a survey. > > > *Survey* > > createSurvey: Create a new survey. > > listSurveys: List all surveys. > > getSurveyById: Get the survey by ID > > updateSurvey: Update or Copy an existing survey. > > > I will update findings. > > Thanks. > Best Regards, > Yashothara.S > Software Engineer > WSO2 > http://wso2.com > https://wso2.com/signature > <https://www.google.com/url?q=https%3A%2F%2Fwso2.com%2Fsignature=D=1=AFQjCNFqSCK3YQC9g0l53f6yjvsVrxRHXg> > -- Best Regards, Malaka Silva Senior Technical Lead 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/ <http://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] [Progress] Dynamically Detection Of Broker Nodes In Cluster And Load Balancing
On Thu, Sep 29, 2016 at 10:06 AM, Sidath Weerasinghe <sid...@wso2.com> wrote: > Hi all, > > In Andes client, I implemented a new initialContextFactory and inside > that, I made an AMQP URL. > Inside the Andes client, I called that web service to get the cluster node > IP address and Port details. When calling web service it shuffles the IP > address and gives String to the client. Using this, create AMQP URL inside > the Andes client, Other IPs put as a failover. > What is the web service you called to get the all the members? Can this be a single point of failure? > > The client can set failover values as properties. Inside the new > initialContextFactory, read those properties and set failover. > "amqp://admin:admin@carbon/carbon?brokerlist='tcp://10.100.4.165:5672? > *retries='10'='1000'*;tcp://10.100.4.166:5672? > *retries='10'='1000''='roundrobin?cyclecount='20'*'" > > Any ideas for this. > > On Thu, Sep 22, 2016 at 5:11 PM, Sidath Weerasinghe <sid...@wso2.com> > wrote: > >> Hi all, >> >> In MB, the user/developers having to manually list out the IPs in the >> connection URL could be difficult. The change of IPs of the broker nodes >> would require reconfiguring and restart the client applications connected >> to it. I am implementing a way to dynamically detection the MB nodes in the >> cluster and load balance through them. >> >> I got the IP address(all network interfaces) and AMQP port and store >> database at cluster startup. When node shutdown that details are removed >> from the database. >> I wrote an admin service to get those database details at the carbon >> business module. >> >> In andes client, I implemented a new initialContextFactory and inside >> that, I made an AMQP URL. As a mock, I got the IP list from the file and >> randomly select one of the IP and port and make AMPQ URL. Other IPs put as >> a fail-over. I tested it. >> >> *Work to be done* >> I will call web service inside the andes client and get the IP and port >> and resolve it according to the client network. After that get the correct >> IP and the port. >> >> >> -- >> Thank You, >> Best Regards, >> >> Sidath Weerasinghe >> >> >> *Intern* >> >> *WSO2, Inc. * >> >> *lean . enterprise . middleware * >> >> >> *Mobile: +94719802550 <%2B94719802550>* >> >> *Email: *sid...@wso2.com >> >> Blog: https://medium.com/@sidath >> >> Linkedin: https://lk.linkedin.com/in/sidathweerasinghe >> > > > > -- > Thank You, > Best Regards, > > Sidath Weerasinghe > > > *Intern* > > *WSO2, Inc. * > > *lean . enterprise . middleware * > > > *Mobile: +94719802550 <%2B94719802550>* > > *Email: *sid...@wso2.com > > Blog: https://medium.com/@sidath > > Linkedin: https://lk.linkedin.com/in/sidathweerasinghe > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, Malaka Silva Senior Technical Lead 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/ <http://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] ESB connector auto generation tool
Yes Kasun this is what our end goal is. We are starting this with soap
based services. Also great if you can share any work done to speed up our
r
@Ajanthan
- Yes we are currently planning to have this a command line tool, however
this is not yet finalized.
On Wed, Sep 21, 2016 at 2:09 AM, Kasun Indrasiri <ka...@wso2.com> wrote:
> Hi Malaka,
>
> We did a PoC project on generating a connector based on a given Swagger
> definition. Is this a similar requirement?
>
> On Tue, Sep 20, 2016 at 10:51 AM, Ajanthan Balachandran <ajant...@wso2.com
> > wrote:
>
>> What do you mean by a tool? Is it command line tool or maven plugin or
>> eclipse plugin?
>>
>> On Fri, Sep 9, 2016 at 2:07 AM, Rajjaz Mohammed <raj...@wso2.com> wrote:
>>
>>>
>>> Hi,
>>>>
>>>> We have currently 150+ connectors in store
>>>> <https://store.wso2.com/store/>. Using those we can easily build
>>>> integration use cases with WSO2 ESB.
>>>>
>>>> However there are some apis that resides on premises and specific to
>>>> some users. If we need to integrate such services, we either need to
>>>> manually do the integration with ESB or develop a connector and use it.
>>>>
>>>> The idea of this project is to automate the development of connectors
>>>> that makes the integration tasks more productive.
>>>>
>>>> So we are planning to start this with soap based connectors and move to
>>>> rest based support later.
>>>>
>>>> For soap based connector generation we basically need to parse the wsdl
>>>> and generate a connector operation per soap operation.
>>>>
>>>> For that we can use WSDL4J. Using this we can get the required
>>>> operations and request/response messages required. Using this information
>>>> we can build the connector operations.(Sequence Templates)
>>>>
>>>> eg:
>>>> String wsdlPath = "/home/wso2/Desktop/ConnectorTest.wsdl";
>>>> WSDLReader reader = javax.wsdl.factory.WSDLFactory
>>>> .newInstance().newWSDLReader();
>>>> javax.wsdl.Definition defn = reader.readWSDL(wsdlPath);
>>>>
>>>> Map tmp =
>>>> defn.getAllServices();
>>>>
>>>> for(javax.xml.namespace.QName key:tmp.keySet()){
>>>> ServiceImpl serviceImpl = tmp.get(key);
>>>> Map <String,PortImpl> mPorts = serviceImpl.getPorts();
>>>> for(String k1:mPorts.keySet()){
>>>> PortImpl portImpl = mPorts.get(k1);
>>>> List bindingOperations =
>>>> portImpl.getBinding().getBindingOperations();
>>>> for(BindingOperationImpl bindingOperation:bindingOperations){
>>>> System.out.println("operation:" + bindingOperation.getName());
>>>> BindingInput bindingInput = bindingOperation.getBindingInput();
>>>> }
>>>> }
>>>> }
>>>> Map messages = defn.getMessages();
>>>> Iterator msgIterator = messages.values().iterator();
>>>> while (msgIterator.hasNext()){
>>>> Message msg = (Message)msgIterator.next();
>>>> if (!msg.isUndefined()) {
>>>> System.out.println(msg.getQName());
>>>> }
>>>> }
>>>> Thoughts?
>>>>
>>>>
>>> Hi All,
>>>
>>> I have the plan to implement ESB connector auto-generation tool. Plase
>>> add if anything more to above explanation about the tool.
>>>
>>> Best Regards,
>>>>
>>>> Malaka Silva
>>>> Senior Technical Lead
>>>> 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/
>>>> <http://wso2.com/about/team/malaka-silva/>
>>>> https://store.wso2.com/store/
>>>>
>>>> Don't make Trees rare, we should keep them with care
>>>>
>>>
>>>
>>>
>>> --
>>> Thank you
>>> Best Regards
>>>
>>> *Rajjaz HM*
>>> Associate Software Engineer
>>> Platform Extension Team
>>> WSO2 Inc. <http://wso2.com/>
>>> lean | enterprise | m
Re: [Architecture] Amazon SQS inbound Endpoint
e servers to get the messages. So, with less number of calls >>>> to make >>>> to SQS to get the messages. In this mechanism, the queue will not >>>> send any >>>> response back to the receiver if there are no messages available in >>>> the >>>> queue. >>>> >>>> >>>>- >>>> >>>> Amazon SQS won’t delete the messages after consuming it. The >>>>consumer has to perform delete message operation after consuming it by >>>>setting “*visibility timeout*“*, *which is a time period during >>>>which the SQS hide the messages to consume. >>>> >>>> >>>> Your comments and suggestions are highly appreciated. >>>> [1] - >>>> *https://docs.google.com/document/d/1tuRUZUDQyonEBIHyocxTIkZu4nERD99TY_pyw35oavs/edit* >>>> <https://docs.google.com/document/d/1tuRUZUDQyonEBIHyocxTIkZu4nERD99TY_pyw35oavs/edit> >>>> >>>> >>>> Thanks, >>>> Biruntha >>>> >>>> Associate Software Engineer >>>> WSO2 >>>> Email : birun...@wso2.com >>>> Linkedin : https://lk.linkedin.com/in/biruntha >>>> Mobile : +94773718986 >>>> >>> >>> >> > -- Best Regards, Malaka Silva Senior Technical Lead 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/ <http://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
[Architecture] ESB connector auto generation tool
Hi,
We have currently 150+ connectors in store <https://store.wso2.com/store/>.
Using those we can easily build integration use cases with WSO2 ESB.
However there are some apis that resides on premises and specific to some
users. If we need to integrate such services, we either need to manually do
the integration with ESB or develop a connector and use it.
The idea of this project is to automate the development of connectors that
makes the integration tasks more productive.
So we are planning to start this with soap based connectors and move to
rest based support later.
For soap based connector generation we basically need to parse the wsdl and
generate a connector operation per soap operation.
For that we can use WSDL4J. Using this we can get the required operations
and request/response messages required. Using this information we can build
the connector operations.(Sequence Templates)
eg:
String wsdlPath = "/home/wso2/Desktop/ConnectorTest.wsdl";
WSDLReader reader =
javax.wsdl.factory.WSDLFactory.newInstance().newWSDLReader();
javax.wsdl.Definition defn = reader.readWSDL(wsdlPath);
Map tmp = defn.getAllServices();
for(javax.xml.namespace.QName key:tmp.keySet()){
ServiceImpl serviceImpl = tmp.get(key);
Map <String,PortImpl> mPorts = serviceImpl.getPorts();
for(String k1:mPorts.keySet()){
PortImpl portImpl = mPorts.get(k1);
List bindingOperations =
portImpl.getBinding().getBindingOperations();
for(BindingOperationImpl bindingOperation:bindingOperations){
System.out.println("operation:" + bindingOperation.getName());
BindingInput bindingInput = bindingOperation.getBindingInput();
}
}
}
Map messages = defn.getMessages();
Iterator msgIterator = messages.values().iterator();
while (msgIterator.hasNext()){
Message msg = (Message)msgIterator.next();
if (!msg.isUndefined()) {
System.out.println(msg.getQName());
}
}
Thoughts?
Best Regards,
Malaka Silva
Senior Technical Lead
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/
<http://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] OSGI Service to provision users and roles based on the SAML response.
Hi Ishara, I guess we can use application-authentication.xml for this purpose? We are maintaining the configs for local authenticators from store. On Mon, Sep 5, 2016 at 10:21 AM, Dimuthu Leelarathne <dimut...@wso2.com> wrote: > > Hi Ishara, > > On Fri, Sep 2, 2016 at 11:19 AM, Ishara Cooray <isha...@wso2.com> wrote: > >> Hi All, >> >> I thought of introducing a new Authenticator config to >> repository/conf/security/authenticators.xml >> And it will use only below properties to do the $Subject. >> >> >> 9 >> >> http >> ://wso2.org/claims/role >> , >> true >> PRIMARY >> >> >> >> Any objections? >> > > I think the existing SAMLSSOAuthenticator should allow JIT provisioning > when we switch on a configuration. If we keep adding more and more > Authenticators for small functionalities it will be cluttered collection in > the end. The same happened to Carbon components. We have so many components > and can't make the head or tail out of it. > > thanks, > Dimuthu > > >> Thanks & Regards, >> Ishara Cooray >> Senior Software Engineer >> Mobile : +9477 262 9512 >> WSO2, Inc. | http://wso2.com/ >> Lean . Enterprise . Middleware >> >> On Wed, Aug 31, 2016 at 1:43 PM, Ishara Cooray <isha...@wso2.com> wrote: >> >>> + Prabath, Johann >>> >>> Thanks & Regards, >>> Ishara Cooray >>> Senior Software Engineer >>> Mobile : +9477 262 9512 >>> WSO2, Inc. | http://wso2.com/ >>> Lean . Enterprise . Middleware >>> >>> On Wed, Aug 31, 2016 at 1:27 PM, Pamod Sylvester <pa...@wso2.com> wrote: >>> >>>> Would it make sense to have it under "user-mgt.xml" ? >>>> >>>> On Wed, Aug 31, 2016 at 1:00 PM, Ishara Cooray <isha...@wso2.com> >>>> wrote: >>>> >>>>> Hi, >>>>> I am working on the $Subject. >>>>> >>>>> *Motivation:* >>>>> I have a use case where i want to authorize users who are logged into >>>>> API publisher/ store but APIM does not have the access to underline user >>>>> store. >>>>> >>>>> *Plan:* >>>>> The plan is to write an osgi service that should do the Just In Time >>>>> provisioning before the permission check to authorize the user. And it >>>>> will >>>>> get the roles from the SAML response and do the provisioning. >>>>> >>>>> But we will have to do the same role/permission mapping manually for >>>>> now. >>>>> >>>>> If we write a generic service we can plug it into any wso2 product >>>>> that need JIT provision initiated by the Service provider. >>>>> However we need to maintain few configurations here. >>>>> >>>>>1. isServiceProvierInitiatedJITProvisioningEnabled >>>>>2. User store to be provisioned >>>>>3. Implementation class (extension point) >>>>> >>>>> What could be the best place to maintain this configuration if the >>>>> component is written as a generic component to any wso2 product? >>>>> >>>>> >>>>> Thanks & Regards, >>>>> Ishara Cooray >>>>> Senior Software Engineer >>>>> Mobile : +9477 262 9512 >>>>> WSO2, Inc. | http://wso2.com/ >>>>> Lean . Enterprise . Middleware >>>>> >>>>> ___ >>>>> Architecture mailing list >>>>> Architecture@wso2.org >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Pamod Sylvester * >>>> >>>> *WSO2 Inc.; http://wso2.com <http://wso2.com>* >>>> cell: +94 77 7779495 >>>> >>>> ___ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Dimuthu Leelarathne > Director, Solutions Architecture > > WSO2, Inc. (http://wso2.com) > email: dimut...@wso2.com > Mobile: +94773661935 > Blog: http://muthulee.blogspot.com > > Lean . Enterprise . Middleware > > ___ > Dev mailing list > d...@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Best Regards, Malaka Silva Senior Technical Lead 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/ <http://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] [PET] Support UniqueBatchWindow(Time, Length) for Siddhi
gt;> wrote: >>>>> >>>>>> Hi Suho, >>>>>> >>>>>> We really don't need to have both in the same implementation. But we >>>>>>> can have both in common repo called UniqueBatchWindow. >>>>>>> >>>>>>> Both are not in same implementations. >>>>>> >>>>>>> >>>>>>> I have planned to develop UniqueTimeBatchWindow, >>>>>>>> UniqueLengthBatchWindow Extension for Siddhi. We already have >>>>>>>> TimeWindow, >>>>>>>> TimeBatchWindow and UniqueTimeWindow. Same to length also. >>>>>>>> >>>>>>>> UniqueTimeBatchWindow, UniqueLengthBatchWindow are going to be two >>>>>> seperate extensions. >>>>>> >>>>>> Currently, I'm planning to implement UniqueBatchWindow which is >>>>>>>> support for both time and length. >>>>>>>> >>>>>>>> Please add your suggestions if you have. >>>>>>>> >>>>>>>> -- >>>>>>>> Thank you >>>>>>>> Best Regards >>>>>>>> >>>>>>>> *Rajjaz HM* >>>>>>>> Associate Software Engineer >>>>>>>> Platform Extension Team >>>>>>>> WSO2 Inc. <http://wso2.com/> >>>>>>>> lean | enterprise | middleware >>>>>>>> Mobile | +94752833834|+94777226874 >>>>>>>> Email | raj...@wso2.com >>>>>>>> LinkedIn <https://lk.linkedin.com/in/hmohammedrajjaz> | Blogger >>>>>>>> <http://rajjazhm.blogspot.com/> | WSO2 Profile >>>>>>>> <http://wso2.com/about/team/mohammer-rajjaz/> >>>>>>>> [image: https://wso2.com/signature] <https://wso2.com/signature> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> *S. Suhothayan* >>>>>>> Associate Director / Architect & Team Lead of WSO2 Complex Event >>>>>>> Processor >>>>>>> *WSO2 Inc. *http://wso2.com >>>>>>> * <http://wso2.com/>* >>>>>>> lean . enterprise . middleware >>>>>>> >>>>>>> >>>>>>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >>>>>>> http://suhothayan.blogspot.com/ >>>>>>> <http://suhothayan.blogspot.com/>twitter: >>>>>>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | >>>>>>> linked-in: >>>>>>> http://lk.linkedin.com/in/suhothayan >>>>>>> <http://lk.linkedin.com/in/suhothayan>* >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Thank you >>>>>> Best Regards >>>>>> >>>>>> *Rajjaz HM* >>>>>> Associate Software Engineer >>>>>> Platform Extension Team >>>>>> WSO2 Inc. <http://wso2.com/> >>>>>> lean | enterprise | middleware >>>>>> Mobile | +94752833834|+94777226874 >>>>>> Email | raj...@wso2.com >>>>>> LinkedIn <https://lk.linkedin.com/in/hmohammedrajjaz> | Blogger >>>>>> <http://rajjazhm.blogspot.com/> | WSO2 Profile >>>>>> <http://wso2.com/about/team/mohammer-rajjaz/> >>>>>> [image: https://wso2.com/signature] <https://wso2.com/signature> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> *S. Suhothayan* >>>>> Associate Director / Architect & Team Lead of WSO2 Complex Event >>>>> Processor >>>>> *WSO2 Inc. *http://wso2.com >>>>> * <http://wso2.com/>* >>>>> lean . enterprise . middleware >>>>> >>>>> >>>>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >>>>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: >>>>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: >>>>> http://lk.linkedin.com/in/suhothayan >>>>> <http://lk.linkedin.com/in/suhothayan>* >>>>> >>>> >>>> >>>> >>>> -- >>>> Thank you >>>> Best Regards >>>> >>>> *Rajjaz HM* >>>> Associate Software Engineer >>>> Platform Extension Team >>>> WSO2 Inc. <http://wso2.com/> >>>> lean | enterprise | middleware >>>> Mobile | +94752833834|+94777226874 >>>> Email | raj...@wso2.com >>>> LinkedIn <https://lk.linkedin.com/in/hmohammedrajjaz> | Blogger >>>> <http://rajjazhm.blogspot.com/> | WSO2 Profile >>>> <http://wso2.com/about/team/mohammer-rajjaz/> >>>> [image: https://wso2.com/signature] <https://wso2.com/signature> >>>> >>> >>> >>> >>> -- >>> Thank you >>> Best Regards >>> >>> *Rajjaz HM* >>> Associate Software Engineer >>> Platform Extension Team >>> WSO2 Inc. <http://wso2.com/> >>> lean | enterprise | middleware >>> Mobile | +94752833834|+94777226874 >>> Email | raj...@wso2.com >>> LinkedIn <https://lk.linkedin.com/in/hmohammedrajjaz> | Blogger >>> <http://rajjazhm.blogspot.com/> | WSO2 Profile >>> <http://wso2.com/about/team/mohammer-rajjaz/> >>> [image: https://wso2.com/signature] <https://wso2.com/signature> >>> >> >> >> >> -- >> *Dilini Muthumala* >> Senior Software Engineer, >> WSO2 Inc. >> >> *E-mail :* dil...@wso2.com >> *Mobile: *+94 713-400-029 >> > > > > -- > Thank you > Best Regards > > *Rajjaz HM* > Associate Software Engineer > Platform Extension Team > WSO2 Inc. <http://wso2.com/> > lean | enterprise | middleware > Mobile | +94752833834|+94777226874 > Email | raj...@wso2.com > LinkedIn <https://lk.linkedin.com/in/hmohammedrajjaz> | Blogger > <http://rajjazhm.blogspot.com/> | WSO2 Profile > <http://wso2.com/about/team/mohammer-rajjaz/> > [image: https://wso2.com/signature] <https://wso2.com/signature> > -- Best Regards, Malaka Silva Senior Technical Lead 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/ <http://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
[Architecture] DB event listener for ESB
Hi, There are requirements to do additional operations when there are changes done to organization data. One way to do this is to create triggers at database level. However there are limitations on actions users can perform using triggers. So if we implement custom inbound endpoint we can cover most of the use cases. [image: Inline image 1] There are several ways to do that. But we already know using JDBC is impossible at the moment. One way to achieve this is implementing a polling inbound to monitor the changes in the database object (such as a table in the database). If any change occurred, that inbound can invoke a sequence. But this is not a good practice. What if your database has more than ten tables? Then users have to create ten threads for each table and that would be a great mess regarding to the performance. There are also vendor specific solutions provided. [1] [2] JPA also provide this capability [3] However with this users need to create entities for there environment and using those with ESB is complex. Using Hibernate we can do the same and maintain the configuration in XML. Thoughts about this inbound are welcome? [1] http://stackoverflow.com/questions/12618915/how-to- implement-a-db-listener-in-java [2] http://www.ibm.com/support/knowledgecenter/SSSHYH_5.1.1/com.ibm. netcoolimpact.doc5.1.1/solution/imsg_db_listeners_ database_listener_overview_c.html [3] https://docs.jboss.org/hibernate/entitymanager/3.6/ reference/en/html/listeners.html [4] https://dunithd.wordpress.com/2009/10/27/create-database- triggers-like-features-using-hibernate-events/ Best Regards, Malaka Silva Senior Technical Lead 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/ <http://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] TOTP authenticator improvement to support federated authenticators in the first step
Also it's good practice if we can put this logic/code in a common place and reuse, if the same functionality is required by other authinticator. On Wed, Jun 29, 2016 at 1:07 PM, Thulasika Vijayanathan <thulas...@wso2.com> wrote: > Hi All, > > Currently, TOTP authenticator supports basic authentication as a first > step.Now I'm working on TOTP authenticator improvement to support federated > authenticators(facebook, google, etc..) in the first step. > > TOTP authenticator needs to retrieve the end user related attributes from > the local user store.To retrieve the local user store data, Username must > be decided in the following ways: > > 1. TOTP needs to retrieve some attributes from local user store, the > Therefore federated username must be stored in the local username as well. > > 2. If the local username is not equal to federated username, Federated > username must be associated with the local account in advance in the > Dashboard. So local username is retrieved from an association. > > 3. Local username is contained in a federated user's attribute. > > If you have enabled the "enableTOTP=false" Flow would be successful > without even an association. It is considered that TOTP has not been > enabled for given user. So it will authenticate successfully with federated > authenticator. > > Your comments and suggestions are highly appreciated. > > > Thanks, > Thulasika > > -- > Thulasika > Associate Software Engineer > Mobile:0778014295 > email: thulas...@wso2.com <sanj...@wso2.com> > -- Best Regards, Malaka Silva Senior Technical Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [C5] [Deployer] Using WatchService instead of FileSystem Polling
+1 We have used the same technique for local file connector using NIO watchers [1] [1] https://store.wso2.com/store/assets/esbconnector/c5573802-8f24-4681-8499-6c6054b7a69b On Thu, Jul 7, 2016 at 8:59 AM, Sameera Jayasoma <same...@wso2.com> wrote: > +1. > > Samiyuru, started working on this sometime back though. > > On Thu, Jul 7, 2016 at 3:42 AM, Rasika Perera <rasi...@wso2.com> wrote: > >> Hi All, >> >> The current way of monitoring artifacts changes in the Carbon-Deployment >> is to poll the File System for Last-Modified-Date[1]. >> >> java.nio.file package provides a WatchService which quite does the same >> job and has optimizations for the *native* support of the most of the File >> System implementations when it is available. >> >> As per the oracle docs[2] it is also recommended for a deployer task; >> >> It is also well suited for an application server that watches a >>> directory, perhaps waiting for .jsp or .jar files to drop, in order to >>> deploy them. >>> >>> >> >> >> WDYT? >> >> >> [1] >> https://github.com/wso2/carbon-deployment/blob/master/components/org.wso2.carbon.deployment.engine/src/main/java/org/wso2/carbon/deployment/engine/internal/Utils.java#L38 >> >> [2] http://docs.oracle.com/javase/tutorial/essential/io/notification.html >> >> -- >> With Regards, >> >> *Rasika Perera* >> Software Engineer >> M: +94 71 680 9060 E: rasi...@wso2.com >> LinkedIn: http://lk.linkedin.com/in/rasika90 >> >> WSO2 Inc. www.wso2.com >> lean.enterprise.middleware >> > > > > -- > Sameera Jayasoma, > Software Architect, > > WSO2, Inc. (http://wso2.com) > email: same...@wso2.com > blog: http://blog.sameera.org > twitter: https://twitter.com/sameerajayasoma > flickr: http://www.flickr.com/photos/sameera-jayasoma/collections > Mobile: 0094776364456 > > Lean . Enterprise . Middleware > > > _______ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, Malaka Silva Senior Technical Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [MB] Delayed Delivery for Rejected Messages.
Hi Hemika, Do we maintain retry count and retry delay properties for this? > On Tue, Jul 5, 2016 at 11:03 AM, Hemika Kodikara <hem...@wso2.com> wrote: > Hi All, > > Currently when a message is being rejected by a subscriber client, the > client is able to delay returning the message to the server. This is done > by setting the "AndesAckWaitTimeOut" system property. > > But the message cannot be delayed from the server side. I.E when a message > rejected is received, the message is requeued straight away to the > subscriber client. > > A delay should be able to added from the server side allowing the clients > not being pushed with rejected messages. > > Solution is to have a configurable value in the broker.xml which applies a > delay for each rejected message before being requeued. > > Each subscription(LocalSubscription) will have a delayed queue[1] which > will store the rejected messages with the configuration value in > broker.xml. When a rejected message is received, accepting new messages > will be stopped from getting delivered to the client by using the > LocalSubscription#hasRoomToAcceptMessages() method. New messages will only > be accepted only when these rejected messages are accepted by the client or > sent to the DLC. > Message can be rejected due to a business logic and can only be related to a particular message. We should not stop processing other messages or have this behavior configurable. > There will be a separate scheduled task which consists of subscriptions > that has rejected messages. The scheduler will go through each of those > subscriptions and deliver the messages to the outbound disruptor. > > > > > See redmine for more details[2] > > [1] - > https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/DelayQueue.html > [2] - https://redmine.wso2.com/issues/5248 > > Regards, > Hemika > > > Hemika Kodikara > Software Engineer > WSO2 Inc. > lean . enterprise . middleware > http://wso2.com > > Mobile : +9477762 > > _______ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, Malaka Silva Senior Technical Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] Fwd: Support for dynamic custom list items and blocking mode in Sharepoint connector
+architecture
Hi Vivekananthan,
What is the parameter required to pass to support this?
-- Forwarded message --
From: Vivekananthan Sivanayagam <vivekanant...@wso2.com>
Date: Sat, Jul 2, 2016 at 12:43 AM
Subject: Support for dynamic custom list items and blocking mode in
Sharepoint connector
To: Malaka Silva <mal...@wso2.com>
Hi Malaka,
I have added template and request here, using that I was able to create
custom list items If it is correct , I will send the PR.
[1] createCustomListItem Template
http://ws.apache.org/ns/synapse;>
{
"__metadata": { "type":"$1" },
$2
}
[2] Request:
{
"apiUrl":"https://vivesl.sharepoint.com;,
"type":"SP.Data.Custom002ListItem",
"customListItems": " 'Title': 'ListItem0010', 'Add_Col':'siva',
'mobile_No':'075 <0752676123>
0
', 'FirstName':'vivekananthan', 'LastName':'Sivanayagam' ",
"listTitle":"Custom002",
"accessToken":"
tt
xxx"
}
--
Best Regards,
Malaka Silva
Senior Technical Lead
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
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/
<http://wso2.com/about/team/malaka-silva/>
https://store.wso2.com/store/
Save a tree -Conserve nature & Save the world for your future. Print this
email only if it is absolutely necessary.
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Dynamic parameters with inbound endpoints
Hi Manuranga , Following will work. Refer [1] for more info. This is work ing since esb 4.9.0 for all inbound parameters. Only issue is we can't secure these and we may have to do that for ESB 5.0.0. I guess that is what Kasun is referring to. You only need to use following when using management console. $registry:conf:/repository/esb/esb-configurations/test [1] https://docs.wso2.com/display/ESB490/Working+with+Inbound+Endpoints On Fri, Jul 1, 2016 at 1:21 AM, Manuranga Perera <m...@wso2.com> wrote: > This may have not fixed in beta yet. There's separate thread on this >> "[Dev] Supporting registry based parameter values in all Inbound Endpoints" >> and I've created a L1 for ESB 5 to make sure that this is available before >> the GA. >> > > According to https://wso2.org/jira/browse/ESBJAVA-3595 it should work. > > -- > With regards, > *Manu*ranga Perera. > > phone : 071 7 70 20 50 > mail : m...@wso2.com > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, Malaka Silva Senior Technical Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] ESB Connector for Asana
Thank you for your contribution. On Thu, Jun 30, 2016 at 3:29 PM, Nirthika Rajendran < nirthika.rajend...@gmail.com> wrote: > Hi All, > > On behalf of my team I thank to all the supporters for gracing your > important time and work with us. > > Thanks > *Nirthika Rajendran* *Student**, University of Jaffna* > Jaffna | nirthika.rajend...@gmail.com > <http://www.facebook.com/nirthika.indran> > <http://lk.linkedin.com/in/nirthika> <http://twitter.com/nirthika_indran> > Get a signature like this: Click here! > <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0==540978356935427> > > On Thu, Jun 30, 2016 at 2:07 PM, Kesavan Yogarajah <kesav...@wso2.com> > wrote: > >> Hi All, >> >> Asana connector is published in the store [1]. >> >> [1] - >> https://store.wso2.com/store/assets/esbconnector/2b76bf40-2451-4b83-b182-2c3b47a72447 >> >> Thanks >> >> Kesavan Yogarajah >> Software Engineer >> Mobile :+94 (0) 779 758021 >> kesav...@wso2.com >> WSO2, Inc. >> lean . enterprise . middleware >> >> On Tue, Jun 28, 2016 at 10:54 AM, Nirthika Rajendran < >> nirthika.rajend...@gmail.com> wrote: >> >>> Thank you to all for your concern. >>> >>> By our team. >>> >>> On Tue, Jun 28, 2016 at 10:44 AM, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> Thx Nirthika, >>>> >>>> @Kesavan - Can we have a quick review and publish to the store? We had >>>> a code review with the team already. >>>> >>>> On Tue, Jun 28, 2016 at 10:37 AM, Nirthika Rajendran < >>>> nirthika.rajend...@gmail.com> wrote: >>>> >>>>> Hi Malaka, >>>>> >>>>> We have added documentation for Asana connector [1]. Please find it. >>>>> >>>>> [1] https://wso2.org/jira/browse/ESBCONNECT-104 >>>>> <https://www.google.com/url?q=https%3A%2F%2Fwso2.org%2Fjira%2Fbrowse%2FESBCONNECT-104=D=1=AFQjCNGHX9eLVNkIi5RWvIE1LmvFqq_fTA> >>>>> >>>>> Thank you. >>>>> >>>>> On Mon, Jun 27, 2016 at 2:49 PM, Malaka Silva <mal...@wso2.com> wrote: >>>>> >>>>>> Thx we will merge and release. >>>>>> >>>>>> Can you also share the documentation? >>>>>> >>>>>> @Kesavan - Can you followup on this please. >>>>>> >>>>>> On Mon, Jun 27, 2016 at 1:31 PM, Nirthika Rajendran < >>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>> >>>>>>> Hi Malaka, >>>>>>> >>>>>>> Please find the pull request[1] for Asana connector. >>>>>>> >>>>>>> [1] https://github.com/wso2-extensions/esb-connector-asana/pull/1 >>>>>>> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fwso2-extensions%2Fesb-connector-asana%2Fpull%2F1=D=1=AFQjCNGtpglKGXfH1Aus3NVg5mQv2aQFHg> >>>>>>> >>>>>>> Thank you. >>>>>>> *Nirthika Rajendran* *Student**, University of Jaffna* >>>>>>> Jaffna | nirthika.rajend...@gmail.com >>>>>>> <http://www.facebook.com/nirthika.indran> >>>>>>> <http://lk.linkedin.com/in/nirthika> >>>>>>> <http://twitter.com/nirthika_indran> >>>>>>> Get a signature like this: Click here! >>>>>>> <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0==896695207292705> >>>>>>> >>>>>>> On Fri, Jun 24, 2016 at 9:49 AM, Malaka Silva <mal...@wso2.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Nirthika and Team, >>>>>>>> >>>>>>>> Can you send the pull request to [1] please? >>>>>>>> >>>>>>>> [1] https://github.com/wso2-extensions/esb-connector-asana >>>>>>>> >>>>>>>> On Wed, Jun 8, 2016 at 11:16 AM, Nirthika Rajendran < >>>&
Re: [Architecture] ESB Connector for Asana
Thx Nirthika, @Kesavan - Can we have a quick review and publish to the store? We had a code review with the team already. On Tue, Jun 28, 2016 at 10:37 AM, Nirthika Rajendran < nirthika.rajend...@gmail.com> wrote: > Hi Malaka, > > We have added documentation for Asana connector [1]. Please find it. > > [1] https://wso2.org/jira/browse/ESBCONNECT-104 > <https://www.google.com/url?q=https%3A%2F%2Fwso2.org%2Fjira%2Fbrowse%2FESBCONNECT-104=D=1=AFQjCNGHX9eLVNkIi5RWvIE1LmvFqq_fTA> > > Thank you. > > On Mon, Jun 27, 2016 at 2:49 PM, Malaka Silva <mal...@wso2.com> wrote: > >> Thx we will merge and release. >> >> Can you also share the documentation? >> >> @Kesavan - Can you followup on this please. >> >> On Mon, Jun 27, 2016 at 1:31 PM, Nirthika Rajendran < >> nirthika.rajend...@gmail.com> wrote: >> >>> Hi Malaka, >>> >>> Please find the pull request[1] for Asana connector. >>> >>> [1] https://github.com/wso2-extensions/esb-connector-asana/pull/1 >>> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fwso2-extensions%2Fesb-connector-asana%2Fpull%2F1=D=1=AFQjCNGtpglKGXfH1Aus3NVg5mQv2aQFHg> >>> >>> Thank you. >>> *Nirthika Rajendran* *Student**, University of Jaffna* >>> Jaffna | nirthika.rajend...@gmail.com >>> <http://www.facebook.com/nirthika.indran> >>> <http://lk.linkedin.com/in/nirthika> >>> <http://twitter.com/nirthika_indran> >>> Get a signature like this: Click here! >>> <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0==896695207292705> >>> >>> On Fri, Jun 24, 2016 at 9:49 AM, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> Hi Nirthika and Team, >>>> >>>> Can you send the pull request to [1] please? >>>> >>>> [1] https://github.com/wso2-extensions/esb-connector-asana >>>> >>>> On Wed, Jun 8, 2016 at 11:16 AM, Nirthika Rajendran < >>>> nirthika.rajend...@gmail.com> wrote: >>>> >>>>> Ok sure thank you. >>>>> >>>>> On Wed, Jun 8, 2016 at 11:09 AM, Malaka Silva <mal...@wso2.com> wrote: >>>>> >>>>>> Looks good. I'll also join. >>>>>> >>>>>> On Tue, Jun 7, 2016 at 8:23 PM, Nirthika Rajendran < >>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>> >>>>>>> Hi Malaka, >>>>>>> >>>>>>> We had a peer review at the Jaffna office. We made the following >>>>>>> changes according to their comments. >>>>>>> >>>>>>> >>>>>>>- Change the init method to store the accesstoken in registry. >>>>>>>- Format the code according to the WSO2 standards. >>>>>>>- Add the INTEGRATION.txt file. >>>>>>>- Change the test cases for new init method. >>>>>>> >>>>>>> We are all ready, Shall we have the review on next Tuesday (14th of >>>>>>> June) at 4pm? >>>>>>> >>>>>>> Thank you >>>>>>> >>>>>>> On Tue, Jun 7, 2016 at 12:40 PM, Malaka Silva <mal...@wso2.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Nirthika, >>>>>>>> >>>>>>>> Did we had the review? If not shall we plan for this soon. >>>>>>>> >>>>>>>> On Fri, May 27, 2016 at 10:53 AM, Nirthika Rajendran < >>>>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>>>> >>>>>>>>> Yes, we can come to the office for review next week >>>>>>>>> >>>>>>>>> Thank you. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, May 27, 2016 at 7:54 AM, Malaka Silva <mal...@wso2.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi Nirthika, >>>>>>>>>> >>>>>>>>>> Great can we have a review before publishing next week. You can >>>>>>>>>> come t
Re: [Architecture] ESB Connector for Asana
Thx we will merge and release. Can you also share the documentation? @Kesavan - Can you followup on this please. On Mon, Jun 27, 2016 at 1:31 PM, Nirthika Rajendran < nirthika.rajend...@gmail.com> wrote: > Hi Malaka, > > Please find the pull request[1] for Asana connector. > > [1] https://github.com/wso2-extensions/esb-connector-asana/pull/1 > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fwso2-extensions%2Fesb-connector-asana%2Fpull%2F1=D=1=AFQjCNGtpglKGXfH1Aus3NVg5mQv2aQFHg> > > Thank you. > *Nirthika Rajendran* *Student**, University of Jaffna* > Jaffna | nirthika.rajend...@gmail.com > <http://www.facebook.com/nirthika.indran> > <http://lk.linkedin.com/in/nirthika> <http://twitter.com/nirthika_indran> > Get a signature like this: Click here! > <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0==896695207292705> > > On Fri, Jun 24, 2016 at 9:49 AM, Malaka Silva <mal...@wso2.com> wrote: > >> Hi Nirthika and Team, >> >> Can you send the pull request to [1] please? >> >> [1] https://github.com/wso2-extensions/esb-connector-asana >> >> On Wed, Jun 8, 2016 at 11:16 AM, Nirthika Rajendran < >> nirthika.rajend...@gmail.com> wrote: >> >>> Ok sure thank you. >>> >>> On Wed, Jun 8, 2016 at 11:09 AM, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> Looks good. I'll also join. >>>> >>>> On Tue, Jun 7, 2016 at 8:23 PM, Nirthika Rajendran < >>>> nirthika.rajend...@gmail.com> wrote: >>>> >>>>> Hi Malaka, >>>>> >>>>> We had a peer review at the Jaffna office. We made the following >>>>> changes according to their comments. >>>>> >>>>> >>>>>- Change the init method to store the accesstoken in registry. >>>>>- Format the code according to the WSO2 standards. >>>>>- Add the INTEGRATION.txt file. >>>>>- Change the test cases for new init method. >>>>> >>>>> We are all ready, Shall we have the review on next Tuesday (14th of >>>>> June) at 4pm? >>>>> >>>>> Thank you >>>>> >>>>> On Tue, Jun 7, 2016 at 12:40 PM, Malaka Silva <mal...@wso2.com> wrote: >>>>> >>>>>> Hi Nirthika, >>>>>> >>>>>> Did we had the review? If not shall we plan for this soon. >>>>>> >>>>>> On Fri, May 27, 2016 at 10:53 AM, Nirthika Rajendran < >>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>> >>>>>>> Yes, we can come to the office for review next week >>>>>>> >>>>>>> Thank you. >>>>>>> >>>>>>> >>>>>>> On Fri, May 27, 2016 at 7:54 AM, Malaka Silva <mal...@wso2.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Nirthika, >>>>>>>> >>>>>>>> Great can we have a review before publishing next week. You can >>>>>>>> come to our office or have it via google hangout? >>>>>>>> >>>>>>>> On Thu, May 26, 2016 at 8:20 PM, Nirthika Rajendran < >>>>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>>>> >>>>>>>>> Hi Malaka, >>>>>>>>> >>>>>>>>> We have completed most of the part of asana connector including >>>>>>>>> >>>>>>>>>1. Develop the methods >>>>>>>>>2. Implement integration testing. >>>>>>>>>3. Complete documentation. >>>>>>>>> >>>>>>>>> >>>>>>>>> Thank you, >>>>>>>>> Nirthika R >>>>>>>>> >>>>>>>>> On Wed, May 4, 2016 at 7:45 AM, Malaka Silva <mal...@wso2.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Good progress. Keep us posted. >>>>>>>>>> >>>>>>>>>> On Wed, May 4, 2016 at 5:39 AM, Nirthika Rajendran < >>
Re: [Architecture] ESB 5.0 Data Mapper plan - Dynamic schema generation for connectors.
Hariprasath will work on this feature. On Mon, Jun 20, 2016 at 4:15 PM, Dmitry Sotnikov <dmi...@wso2.com> wrote: > I guess, also there would be some sort of default schema built-in (e.g. > salesforce.com has some default schema out of the box) and like you guys > discussed ability to refresh from live connection. > > On Mon, Jun 20, 2016 at 8:13 AM, Malaka Silva <mal...@wso2.com> wrote: > >> >> Hi Maheeka, >> >> On Mon, Jun 20, 2016 at 10:22 AM, Maheeka Jayasuriya <mahe...@wso2.com> >> wrote: >> >>> >>> Hi Malaka, >>> >>> In order to get the dynamic schemas we need a connection to Salesforce. >>> Right now we are not providing the connection when getting the schema for a >>> connector. Refer screenshot below. >>> >> >> IMO design time connection should be independent from run time >> connections. >> >> >>> >>> [image: Inline image 1] >>> >>> How about we keep a property (a flag) in the connector meta-data whether >>> it is a dynamic schema connector or a static schema connector. If it is a >>> dynamic schema connector, in addition to above, we can add a field to >>> select the connection (from already created connections) and perform the >>> partner API call there. Instead of operation field we can load the entity >>> definitions to load the schema. >>> >> Yes those can be added later. Generating dynamic schema part should not >> be a part of connector. However some reference should be there and should >> be available to the tool on demand. >> >> First we need to find the best way to integrate this to tooling. Will >> arrange an discussion on this. >> >>> >>> >> Thanks, >>> Maheeka >>> >>> Maheeka Jayasuriya >>> Senior Software Engineer >>> Mobile : +9450661 >>> >>> On Sat, Jun 18, 2016 at 8:01 PM, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> Hi, >>>> >>>> Data mapper will be introduced with ESB 5.0.0 tooling soon. This >>>> discussion is related to using data mapper with connectors in your >>>> integration flow. >>>> >>>> Data mapper is a tool that work at design time. So for each connector >>>> operation we need to include a schema in order to make use of data mapping. >>>> >>>> Currently there are two types of connector operations. >>>> >>>>1. Static output and/or input required - If the connector always >>>>produce same output format no issue and we can simply generate the >>>> schema >>>>and bundle it with connector. >>>>2. Dynamic output and/or input required - This is becoming a >>>>changeling since output may change depend on the customization done on >>>>individual apps. >>>> >>>> Good example is Salesforce. Object structure from one Salesforce org to >>>> another org can be different. >>>> >>>> So we need some generic mechanism to run this dynamic schema generation >>>> within tooling and specific implementation should be included in the >>>> connector. >>>> >>>> However including this part in a connector can make the connector heavy >>>> and this may not require during the run time. Best we have those in some >>>> place and get to tooling on demand. >>>> >>>> I have done a POC how we can do this for Salesforce. Sample code is >>>> available in [1]. We may have to do the same for each method. >>>> >>>> Here we are using metadata api to get the sObject list. Partner api >>>> describe sObject method to get fields. >>>> >>>> So this way we can get the required input and output and using this we >>>> can generate the schema. This is purely written in java. >>>> >>>> Now the next challenge is to include this with ESB tooling and >>>> connectors. Please put your suggestions. >>>> >>>> [image: Inline image 1] >>>> >>>> [image: Inline image 2] >>>> >>>> Generated output. >>>> >>>> Query >>>> >>>> >>>> Account >>>> UK >>>> 2016-01-05T09:44:15.000Z >>>> >>>> Test >>>> >>>> >>>> . >>>> >
Re: [Architecture] ESB Connector for Asana
Hi Nirthika and Team, Can you send the pull request to [1] please? [1] https://github.com/wso2-extensions/esb-connector-asana On Wed, Jun 8, 2016 at 11:16 AM, Nirthika Rajendran < nirthika.rajend...@gmail.com> wrote: > Ok sure thank you. > > On Wed, Jun 8, 2016 at 11:09 AM, Malaka Silva <mal...@wso2.com> wrote: > >> Looks good. I'll also join. >> >> On Tue, Jun 7, 2016 at 8:23 PM, Nirthika Rajendran < >> nirthika.rajend...@gmail.com> wrote: >> >>> Hi Malaka, >>> >>> We had a peer review at the Jaffna office. We made the following >>> changes according to their comments. >>> >>> >>>- Change the init method to store the accesstoken in registry. >>>- Format the code according to the WSO2 standards. >>>- Add the INTEGRATION.txt file. >>>- Change the test cases for new init method. >>> >>> We are all ready, Shall we have the review on next Tuesday (14th of >>> June) at 4pm? >>> >>> Thank you >>> >>> On Tue, Jun 7, 2016 at 12:40 PM, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> Hi Nirthika, >>>> >>>> Did we had the review? If not shall we plan for this soon. >>>> >>>> On Fri, May 27, 2016 at 10:53 AM, Nirthika Rajendran < >>>> nirthika.rajend...@gmail.com> wrote: >>>> >>>>> Yes, we can come to the office for review next week >>>>> >>>>> Thank you. >>>>> >>>>> >>>>> On Fri, May 27, 2016 at 7:54 AM, Malaka Silva <mal...@wso2.com> wrote: >>>>> >>>>>> Hi Nirthika, >>>>>> >>>>>> Great can we have a review before publishing next week. You can come >>>>>> to our office or have it via google hangout? >>>>>> >>>>>> On Thu, May 26, 2016 at 8:20 PM, Nirthika Rajendran < >>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>> >>>>>>> Hi Malaka, >>>>>>> >>>>>>> We have completed most of the part of asana connector including >>>>>>> >>>>>>>1. Develop the methods >>>>>>>2. Implement integration testing. >>>>>>>3. Complete documentation. >>>>>>> >>>>>>> >>>>>>> Thank you, >>>>>>> Nirthika R >>>>>>> >>>>>>> On Wed, May 4, 2016 at 7:45 AM, Malaka Silva <mal...@wso2.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Good progress. Keep us posted. >>>>>>>> >>>>>>>> On Wed, May 4, 2016 at 5:39 AM, Nirthika Rajendran < >>>>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>>>> >>>>>>>>> Hi Malaka, >>>>>>>>> >>>>>>>>> Yesterday we meet our mentor Kesavan to clear some problem in >>>>>>>>> integration test. There we correct some errors and now we continue >>>>>>>>> the task. >>>>>>>>> >>>>>>>>> Thank you. >>>>>>>>> >>>>>>>>> On Tue, May 3, 2016 at 11:58 AM, Nirthika Rajendran < >>>>>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> ok, thank you. >>>>>>>>>> >>>>>>>>>> On Tue, May 3, 2016 at 11:21 AM, Malaka Silva <mal...@wso2.com> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> After finishing the integration tests should be fine. >>>>>>>>>>> >>>>>>>>>>> On Tue, May 3, 2016 at 9:18 AM, Nirthika Rajendran < >>>>>>>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Malaka, >>>>>>>>>>>> >>>>>>>>>>>> Thank you, we already have two mentors Miss. Keerthika and Mr. >>>>>>>>>>>> Kesavan. So if we have any other problem we will contact you. >>>>>>>>>>>> >>>>>>>>>>>> Ca
Re: [Architecture] RSA SecurID Authenticatior for IS
requested claims. >>>>>> >>>>>> >>>>>> *RSA Authentication Manager* >>>>>> RSA Authentication Manager is a multi-factor authentication system >>>>>> that verify the authentication requests and centrally administrate the >>>>>> authentication policies for enterprises[3]. >>>>>> >>>>>> *RSA Authentication Agent * >>>>>> It is a bridge for communicating to the Authentication Manager with >>>>>> client, and it is process authentication request. >>>>>> >>>>>> *RSA Authenticators* >>>>>> Hardware Authenticators : Dedicated devices (so called key fobs) >>>>>> Software Authenticatiors : Mobile Application Authenticators in >>>>>> Android, iOS, Blackberry, Windows Mobile and etc. [2]. >>>>>> >>>>>> [1] >>>>>> https://www.rsa.com/en-us/perspectives/resources/rsa-securid-software-tokens >>>>>> [2] >>>>>> https://www.rsa.com/en-us/products-services/identity-access-management/securid/software-tokens >>>>>> [3] RSA Authentication Manager Documentation >>>>>> >>>>>> -- >>>>>> Nifras Ismail >>>>>> Associate Software Engineer >>>>>> WSO2 >>>>>> Email : nif...@wso2.com >>>>>> Mobile : 0094 77 89 90 300 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Nifras Ismail >>>>> Associate Software Engineer >>>>> WSO2 >>>>> Email : nif...@wso2.com >>>>> Mobile : 0094 77 89 90 300 >>>>> >>>>> ___ >>>>> Architecture mailing list >>>>> Architecture@wso2.org >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Kathees >>>> Software Engineer, >>>> email: kath...@wso2.com >>>> mobile: +94772596173 >>>> >>>> ___ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> Nifras Ismail >>> Associate Software Engineer >>> WSO2 >>> Email : nif...@wso2.com >>> Mobile : 0094 77 89 90 300 >>> >> >> >> >> -- >> Nifras Ismail >> Associate Software Engineer >> WSO2 >> Email : nif...@wso2.com >> Mobile : 0094 77 89 90 300 >> > > > > -- > Nifras Ismail > Associate Software Engineer > WSO2 > Email : nif...@wso2.com > Mobile : 0094 77 89 90 300 > -- Best Regards, Malaka Silva Senior Technical Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Securing communication between Hazelcast and WSO2 servers
We need the commercial edition to support this. If someone is interested they need to purchase and use it. On Mon, Jun 13, 2016 at 10:36 PM, Hasitha Hiranya <hasit...@wso2.com> wrote: > Hi, > > When a cluster is setup out of WSO2 servers Hazelcast is configured to > > 1. Make cluster calls across nodes (push notifications) > 2. Use as a distributed cache among the nodes > > Is there any possibility for a third party Hazelcast client to come and > consume this data or push un-relevant notifications to the nodes? Also, are > we storing sensitive data in HZ cache? > > Hazelcast communication is happening inside MZ. But yet some companies > would like to make it secured. > > SSL can be configured at HZ client level as per [1], but not sure if it > only for enterprise. > > [1]. http://docs.hazelcast.org/docs/3.5/manual/html/ssl.html > > Thanks > > -- > *Hasitha Abeykoon* > Senior Software Engineer; WSO2, Inc.; http://wso2.com > *cell:* *+94 719363063* > *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> > > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, Malaka Silva Senior Technical Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] SMPP Connector for ESB
Hi Biruntha, Thx for the info. but some estimates are missing in the plan. eg: documentation, testing etc. On Thu, Jun 9, 2016 at 2:18 PM, Biruntha Gnaneswaran <birun...@wso2.com> wrote: > Hi All, > > Milestone plan for SMPP Connector : [1] > > [1] > https://docs.google.com/spreadsheets/d/1zgo8m-t41k8JrxfmdAoASC-ymL-ImoWj-Cr6QRJl2zM/edit#gid=0 > > > Biruntha > > Associate Software Engineer > WSO2 > Email : birun...@wso2.com > > On Thu, Jun 2, 2016 at 7:32 PM, Biruntha Gnaneswaran <birun...@wso2.com> > wrote: > >> Adding Malaka >> >> Biruntha >> >> Associate Software Engineer >> WSO2 >> Email : birun...@wso2.com >> >> On Thu, Jun 2, 2016 at 11:41 AM, Biruntha Gnaneswaran <birun...@wso2.com> >> wrote: >> >>> Hi All, >>> >>> I have planned to implement $subject as described below, >>> >>> SMPP (Short Message Peer to Peer) protocol [1] is an open, industry >>> standard protocol designed to provide a flexible data communications >>> interface for transfer of short message data between a Message Center, such >>> as a Short Message Service Center (SMSC). >>> >>> >>> Architecture diagram - [2] >>> >>> [1] >>> http://www.inviosmart.it/en/messaging-services/send-sms-smpp-gateway-multiple-bulk-messages >>> >>> [2] >>> https://docs.google.com/document/d/1FZ9ZO3RhEtrrScsS1_QR1figccjVvg58MzoBoDvVHWc/edit >>> >>> Thankyou, >>> >>> Biruntha >>> >>> Associate Software Engineer >>> WSO2 >>> Email : birun...@wso2.com >>> >> >> > -- Best Regards, Malaka Silva Senior Technical Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [PET] Connector improvement - People HR connector
Hi Vivekananthan, What is the api version that current connector is written. Also what are the apis and versions available with peoplehr? On Thu, Jun 9, 2016 at 9:38 AM, Vivekananthan Sivanayagam < vivekanant...@wso2.com> wrote: > Hi All, > > I am going to improve a People HR connector, in the existing one, it has > the following methods. I've planned to improve the additional methods which > are highlighted below. > > 1) Absence > >- createAbsenceRecord >- getAbsenceRecord >- updateAbsenceRecord >- deleteAbsence > > 2) Employee > >- createEmployee >- getAllEmployeeDetail >- getEmployee >- updateEmployee >- getEmployeeDetailById >- updateEmployeeId >- markAsLeaverById > > 3) ProjectTimesheet > >- createProjectTimesheet >- getProjectTimesheet >- updateProjectTimesheet >- deleteProjectTimesheet > > 4) Salary > >- createSalary >- getSalary >- deleteSalary > > 5) Timesheet > >- createTimesheet >- getTimesheet >- updateTimesheet >- deleteTimesheet > > 6) Queries > >- query > > 7) Holiday > >- getHolidayDetail >- createHoliday >- updateHoliday >- deleteHoliday > > 8) Holiday Entitlement > >- getHolidayEntitlement >- getNextYearHolidayEntitlement >- updateHolidayEntitlement >- updateNextYearHolidayEntitlement > > 9) History > >- getHistoryByEmployeeIdAndFieldName > > 10) Document > >- uploadEmployeeDocument >- getAllDocument >- GetDocumentById > > Please let me know if you have any requirements/suggestion on above > methods to implement. > > > > > > *Thank youVivekananthan Sivanayagam* > > *Associate Software Engineer | WSO2* > > *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>* > *M:+94752786138 <%2B94752786138>* > -- Best Regards, Malaka Silva Senior Technical Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Archiecture] ESB - Feature Request - JMS transactions with non-blocking transports
On Tue, Jun 7, 2016 at 10:06 PM, Isuru Udana <isu...@wso2.com> wrote: > Hi Manu, > > +1. Good idea. > I also think it is doable in the way you suggested, however we need to > investigate little bit more on this. > > > > > > > > On Tue, Jun 7, 2016 at 10:00 PM, Manuranga Perera <m...@wso2.com> wrote: > >> AFAIK, correct me if I am wrong, the transaction is closed when the >> thread returns [1].This means we can't use call mediator (or send) with JMS >> proxy with transactions. >> > You can use call mediator in blocking mode. > >> If we keep JMS session/context in the message context and only close >> after the mediation flow is over, we will be able to handle more concurrent >> JMS requests. WDUT? >> > Transactions are bind to jms session and creating multiple sessions on demand are expensive. If you want to implement concurrency still you can do this with transport.jms.ConcurrentConsumers with proxies. With inbound you can do this with adding multiple workers. > >> [1] https://docs.wso2.com/display/ESB460/JMS+Transactions >> >> -- >> With regards, >> *Manu*ranga Perera. >> >> phone : 071 7 70 20 50 >> mail : m...@wso2.com >> > > > > -- > *Isuru Udana* > Technical Lead > WSO2 Inc.; http://wso2.com > email: isu...@wso2.com cell: +94 77 3791887 > blog: http://mytecheye.blogspot.com/ > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, Malaka Silva Senior Technical Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] ESB Connector for Asana
Looks good. I'll also join. On Tue, Jun 7, 2016 at 8:23 PM, Nirthika Rajendran < nirthika.rajend...@gmail.com> wrote: > Hi Malaka, > > We had a peer review at the Jaffna office. We made the following changes > according to their comments. > > >- Change the init method to store the accesstoken in registry. >- Format the code according to the WSO2 standards. >- Add the INTEGRATION.txt file. >- Change the test cases for new init method. > > We are all ready, Shall we have the review on next Tuesday (14th of June) > at 4pm? > > Thank you > > On Tue, Jun 7, 2016 at 12:40 PM, Malaka Silva <mal...@wso2.com> wrote: > >> Hi Nirthika, >> >> Did we had the review? If not shall we plan for this soon. >> >> On Fri, May 27, 2016 at 10:53 AM, Nirthika Rajendran < >> nirthika.rajend...@gmail.com> wrote: >> >>> Yes, we can come to the office for review next week >>> >>> Thank you. >>> >>> >>> On Fri, May 27, 2016 at 7:54 AM, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> Hi Nirthika, >>>> >>>> Great can we have a review before publishing next week. You can come to >>>> our office or have it via google hangout? >>>> >>>> On Thu, May 26, 2016 at 8:20 PM, Nirthika Rajendran < >>>> nirthika.rajend...@gmail.com> wrote: >>>> >>>>> Hi Malaka, >>>>> >>>>> We have completed most of the part of asana connector including >>>>> >>>>>1. Develop the methods >>>>>2. Implement integration testing. >>>>>3. Complete documentation. >>>>> >>>>> >>>>> Thank you, >>>>> Nirthika R >>>>> >>>>> On Wed, May 4, 2016 at 7:45 AM, Malaka Silva <mal...@wso2.com> wrote: >>>>> >>>>>> Good progress. Keep us posted. >>>>>> >>>>>> On Wed, May 4, 2016 at 5:39 AM, Nirthika Rajendran < >>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>> >>>>>>> Hi Malaka, >>>>>>> >>>>>>> Yesterday we meet our mentor Kesavan to clear some problem in >>>>>>> integration test. There we correct some errors and now we continue the >>>>>>> task. >>>>>>> >>>>>>> Thank you. >>>>>>> >>>>>>> On Tue, May 3, 2016 at 11:58 AM, Nirthika Rajendran < >>>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>>> >>>>>>>> ok, thank you. >>>>>>>> >>>>>>>> On Tue, May 3, 2016 at 11:21 AM, Malaka Silva <mal...@wso2.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> After finishing the integration tests should be fine. >>>>>>>>> >>>>>>>>> On Tue, May 3, 2016 at 9:18 AM, Nirthika Rajendran < >>>>>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Hi Malaka, >>>>>>>>>> >>>>>>>>>> Thank you, we already have two mentors Miss. Keerthika and Mr. >>>>>>>>>> Kesavan. So if we have any other problem we will contact you. >>>>>>>>>> >>>>>>>>>> Can we have the hangout after finishing the integration test or >>>>>>>>>> it is necessary to do now? >>>>>>>>>> >>>>>>>>>> Thank you. >>>>>>>>>> >>>>>>>>>> On Mon, May 2, 2016 at 9:31 PM, Malaka Silva <mal...@wso2.com> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Nirthika, >>>>>>>>>>> >>>>>>>>>>> Let us know if you need any assistance to complete this? >>>>>>>>>>> >>>>>>>>>>> We can have a hangout to review the work you have done so far if >>>>>>>>>>> possible? >>>>>>>>>>> >>>>>>>>>>> On Wed, Mar 9, 2016 at 4:08 PM, Nirthika Rajendran < >>>>>>>>>>> nirthika.rajend...@gmail.com> wr
Re: [Architecture] Writing an ESB connector for BPMN rest API.
+1 On Fri, Jun 3, 2016 at 4:02 PM, Nandika Jayawardana <nand...@wso2.com> wrote: > +1 > > Nandika > > On Fri, Jun 3, 2016 at 3:32 PM, Hasitha Aravinda <hasi...@wso2.com> wrote: > >> Hi all, >> >> Shall we do the $Subject for BPMN rest API [1]. Basically, connector >> should cover basic functions such as >> >>- Start process instance >>- Receive messages (Correlation) >>- List and get process instances and their variables >>- HumanTask's related operations. etc. >> >> With this connector, we can simply integrate other systems with BPS >> Workflow engine/HumanTask engine. >> >> Any thoughts. ? >> >> [1] - https://docs.wso2.com/display/BPS351/BPMN+REST+API >> >> Thanks, >> Hasitha. >> >> -- >> -- >> Hasitha Aravinda, >> Associate Technical Lead, >> WSO2 Inc. >> Email: hasi...@wso2.com >> Mobile : +94 718 210 200 >> > > > > -- > Nandika Jayawardana > WSO2 Inc ; http://wso2.com > lean.enterprise.middleware > -- Best Regards, Malaka Silva Senior Technical Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [PET] [CEP] File Writer for CEP
Is the scope should only cover local file system? Then IMO this should be the optimum way. On Tue, May 31, 2016 at 10:25 AM, Rajjaz Mohammed <raj...@wso2.com> wrote: > Hi All, > > I have planed to develop $Subject using NIO[1] . NIO was created to allow > Java programmers to implement high-speed I/O without having to write custom > native code. NIO moves the most time-consuming I/O activities (namely, > filling and draining buffers) back into the operating system, thus allowing > for a great increase in speed[2]. > > Hope NIO was the best choice for CEP file writer. If you have any > suggestions please add in this thread. > > [1] > https://docs.oracle.com/javase/7/docs/api/java/nio/package-summary.html > [2] http://www.ibm.com/developerworks/java/tutorials/j-nio/j-nio.html > > -- > Thank you > Best Regards > > *Rajjaz HM* > Associate Software Engineer > Platform Extension Team > WSO2 Inc. <http://wso2.com/> > lean | enterprise | middleware > Mobile | +94752833834|+94777226874 > Email | raj...@wso2.com > LinkedIn <https://lk.linkedin.com/in/hmohammedrajjaz> | Blogger > <http://wso2experience.blogspot.com/> | WSO2 Profile > <http://wso2.com/about/team/mohammer-rajjaz/> > -- Best Regards, Malaka Silva Senior Tech Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Manage ESB Endpoint configs dynamically
On Tue, May 31, 2016 at 10:11 AM, Kalyani Yogeswaranathan <kaly...@wso2.com>
wrote:
> Noted Malaka. I'll start work on this.
>
> On Tue, May 31, 2016 at 10:08 AM, Malaka Silva <mal...@wso2.com> wrote:
>
>> Hi Kalyani,
>>
>> Can we check this with ESB 5.0.0 beta.
>>
>> Ravi has already fixed this and we should be able to incorporate this to
>> connectors.
>>
> Sorry should be Kevin not Ravi
>
>> We can start with Salesforce connector. (Soap Connector)
>>
>> -- Forwarded message --
>> From: Malaka Silva <mal...@wso2.com>
>> Date: Thu, Feb 25, 2016 at 8:27 PM
>> Subject: Re: [Architecture] Manage ESB Endpoint configs dynamically
>> To: architecture <architecture@wso2.org>
>>
>>
>> Hi Gayan,
>>
>> There are currently limitation from esb side to support this from
>> connectors. So firstly this improvement needs to go to next esb version and
>> will implement this afterwards.
>>
>> Currently only option is to manually update the connector.
>>
>> [1] [Dev] [PET] Couldn't retrieve the endpoint template
>>
>> On Thu, Feb 25, 2016 at 2:21 PM, Gayan Gunarathne <gay...@wso2.com>
>> wrote:
>>
>>> Did we update the ESB Salesforce connector new version with this
>>> endpoint configs? Is that available in cartridge store?
>>>
>>> Thanks,
>>> Gayan
>>>
>>> On Fri, Feb 5, 2016 at 5:48 PM, Vivekananthan Sivanayagam <
>>> vivekanant...@wso2.com> wrote:
>>>
>>>> Hi ,
>>>>
>>>> I have created end point template manually and called it in connector,
>>>> It is working fine. The problem occurred when I was creating the end point
>>>> template within connector.
>>>>
>>>>
>>>>
>>>>
>>>> *Thank youVivekananthan Sivanayagam*
>>>>
>>>> *Associate Software Engineer | WSO2*
>>>>
>>>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>>>> *M:+94752786138 <%2B94752786138>*
>>>>
>>>> On Fri, Feb 5, 2016 at 5:22 PM, Vivekananthan Sivanayagam <
>>>> vivekanant...@wso2.com> wrote:
>>>>
>>>>> Hi ,
>>>>>
>>>>> I created the endpoint template as follow.
>>>>>
>>>>>
>>>>> >>>> xmlns="http://ws.apache.org/ns/synapse;>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> http://wso.com; format="soap11">
>>>>>
>>>>> $initialDuration
>>>>>
>>>>> $progressionFactor
>>>>> $maximumDuration
>>>>>
>>>>>
>>>>> $duration
>>>>> $responseAction
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> And I called the template in INIT method.
>>>>>
>>>>>
>>>>>
>>>>> >>>> value="{ctx:salesforce.initialDuration}" />
>>>>> >>>> value="{ctx:salesforce.progressionFactor}" />
>>>>> >>>> value="{ctx:salesforce.maximumDuration}" />
>>>>>
>>>>> >>>> value="{ctx:salesforce.responseAction}" />
>>>>>
>>>>>
>>>>>
>>>>> It shows the following Error.
>>>>>
>>>>>
>>>>> WARN - TemplateEndpoint Template salesforceEndPoint cannot be found for
>>>>> the endpoint ep1
>>>>> [2016-02-05 17:12:44,432] INFO - LogMediator Connection = Login to
>>>>> Salesforce .
>>>>> [2016-02-05 17:12:44,434] WARN - TemplateEndpoint Couldn't retrieve the
>>>>> endpoint template with the key:salesforceEndPoint
>>>>> [2016-02-05 17:12:44,435] INFO - LogMediator To:
>>>>> https://login.salesforce.com/services/Soap/u/27.0, WSAction:
>>>>> urn:partner.soap.sforce.com/Soap/loginRequest, SOAPAction:
>>>>> urn:partner.soap.sforce.com/Soap/loginRequ
[Architecture] Fwd: Manage ESB Endpoint configs dynamically
Hi Kalyani,
Can we check this with ESB 5.0.0 beta.
Ravi has already fixed this and we should be able to incorporate this to
connectors.
We can start with Salesforce connector. (Soap Connector)
-- Forwarded message --
From: Malaka Silva <mal...@wso2.com>
Date: Thu, Feb 25, 2016 at 8:27 PM
Subject: Re: [Architecture] Manage ESB Endpoint configs dynamically
To: architecture <architecture@wso2.org>
Hi Gayan,
There are currently limitation from esb side to support this from
connectors. So firstly this improvement needs to go to next esb version and
will implement this afterwards.
Currently only option is to manually update the connector.
[1] [Dev] [PET] Couldn't retrieve the endpoint template
On Thu, Feb 25, 2016 at 2:21 PM, Gayan Gunarathne <gay...@wso2.com> wrote:
> Did we update the ESB Salesforce connector new version with this endpoint
> configs? Is that available in cartridge store?
>
> Thanks,
> Gayan
>
> On Fri, Feb 5, 2016 at 5:48 PM, Vivekananthan Sivanayagam <
> vivekanant...@wso2.com> wrote:
>
>> Hi ,
>>
>> I have created end point template manually and called it in connector, It
>> is working fine. The problem occurred when I was creating the end point
>> template within connector.
>>
>>
>>
>>
>> *Thank youVivekananthan Sivanayagam*
>>
>> *Associate Software Engineer | WSO2*
>>
>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>> *M:+94752786138 <%2B94752786138>*
>>
>> On Fri, Feb 5, 2016 at 5:22 PM, Vivekananthan Sivanayagam <
>> vivekanant...@wso2.com> wrote:
>>
>>> Hi ,
>>>
>>> I created the endpoint template as follow.
>>>
>>>
>>> http://ws.apache.org/ns/synapse;>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> http://wso.com; format="soap11">
>>>
>>> $initialDuration
>>>
>>> $progressionFactor
>>> $maximumDuration
>>>
>>>
>>> $duration
>>> $responseAction
>>>
>>>
>>>
>>>
>>>
>>> And I called the template in INIT method.
>>>
>>>
>>>
>>> >> value="{ctx:salesforce.initialDuration}" />
>>> >> value="{ctx:salesforce.progressionFactor}" />
>>> >> value="{ctx:salesforce.maximumDuration}" />
>>>
>>> >> value="{ctx:salesforce.responseAction}" />
>>>
>>>
>>>
>>> It shows the following Error.
>>>
>>>
>>> WARN - TemplateEndpoint Template salesforceEndPoint cannot be found for the
>>> endpoint ep1
>>> [2016-02-05 17:12:44,432] INFO - LogMediator Connection = Login to
>>> Salesforce .
>>> [2016-02-05 17:12:44,434] WARN - TemplateEndpoint Couldn't retrieve the
>>> endpoint template with the key:salesforceEndPoint
>>> [2016-02-05 17:12:44,435] INFO - LogMediator To:
>>> https://login.salesforce.com/services/Soap/u/27.0, WSAction:
>>> urn:partner.soap.sforce.com/Soap/loginRequest, SOAPAction:
>>> urn:partner.soap.sforce.com/Soap/loginRequest, MessageID:
>>> urn:uuid:d8efb9e0-7b89-4421-b95a-425458b19310, Direction: request, MESSAGE
>>> = Executing default 'fault' sequence, ERROR_CODE = 305100, ERROR_MESSAGE =
>>> Couldn't find the endpoint with the name ep1 & template :
>>> salesforceEndPoint, Envelope: >> encoding='utf-8'?>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/;
>>> xmlns:urn="urn:partner.soap.sforce.com">vsvivevi...@gmail.comvive@wso2RtKuSKM9w1ra8ahIuloG7FHBP
>>> [2016-02-05 17:12:44,436] DEBUG - wire << "HTTP/1.1 202 Accepted[\r][\n]"
>>>
>>> I followed doc[1] and malaka's suggestion.
>>>
>>> [1] https://docs.wso2.com/display/ESB480/Endpoint+Template
>>>
>>> Can you help me to solve this issue?
>>>
>>>
>>>
>>>
>>> *Thank youVivekananthan Sivanayagam*
>>>
>>> *Associate Software Engineer | WSO2*
>>>
>>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>>> *M:+94752786138 <%2B94752786138>*
>>>
>>> On Wed, Jan 27, 2016 at 11:20 AM, Kanapriya Kul
Re: [Architecture] Deprecating File Connector V1
Shall we deprecate v1 since we have released v2 with all functions? On Mon, May 23, 2016 at 8:55 AM, Yashothara Shanmugarajah < yashoth...@wso2.com> wrote: > Yep. I have profiled the memory and it is same as ESB profiling. > > Best Regards, > Yashothara.S > > Software Engineer > WSO2 > > > On Mon, May 23, 2016 at 8:53 AM, Malaka Silva <mal...@wso2.com> wrote: > >> Did we profile the memory while doing this? >> >> On Mon, May 23, 2016 at 8:49 AM, Yashothara Shanmugarajah < >> yashoth...@wso2.com> wrote: >> >>> Hi all, >>> >>> I have completed the adding streaming feature to file read method in >>> File connector version 2. It works fine until 1 Gb as ESB. >>> >>> Thanks. >>> >>> Best Regards, >>> Yashothara.S >>> >>> Software Engineer >>> WSO2 >>> >>> >>> On Wed, May 4, 2016 at 10:40 AM, Vivekananthan Sivanayagam < >>> vivekanant...@wso2.com> wrote: >>> >>>> Hi , >>>> >>>> The method FileRename includes in file connector version 1, but not in >>>> a version 2. We can do this using FileMove operation. We can deprecate V1. >>>> >>>> >>>> >>>> >>>> *Thank youVivekananthan Sivanayagam* >>>> >>>> *Associate Software Engineer | WSO2* >>>> >>>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>* >>>> *M:+94752786138 <%2B94752786138>* >>>> >>>> On Wed, May 4, 2016 at 9:18 AM, Yashothara Shanmugarajah < >>>> yashoth...@wso2.com> wrote: >>>> >>>>> We can add streaming parameter to read operation in version 2. >>>>> >>>>> Best Regards, >>>>> Yashothara.S >>>>> >>>>> Software Engineer >>>>> WSO2 >>>>> >>>>> >>>>> On Wed, May 4, 2016 at 9:11 AM, Malaka Silva <mal...@wso2.com> wrote: >>>>> >>>>>> Yashothara yes you are correct. Best is we incorporate streaming to >>>>>> read operation with the new sender operation (you are already writing) >>>>>> then >>>>>> deprecate V1. >>>>>> >>>>>> Any other use cases? >>>>>> >>>>>> On Wed, May 4, 2016 at 9:01 AM, Yashothara Shanmugarajah < >>>>>> yashoth...@wso2.com> wrote: >>>>>> >>>>>>> In file connector Version 2, there is no streaming parameter in file >>>>>>> read method. But in version 1 it has. Is it ok? >>>>>>> >>>>>>> Best Regards, >>>>>>> Yashothara.S >>>>>>> >>>>>>> Software Engineer >>>>>>> WSO2 >>>>>>> >>>>>>> >>>>>>> On Wed, May 4, 2016 at 8:09 AM, Malaka Silva <mal...@wso2.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Currently we have two connector versions for file operations with >>>>>>>> ESB. [1] >>>>>>>> >>>>>>>> Reason we implemented another version is to make the ESB >>>>>>>> integration flows more user friendly and better error handling >>>>>>>> >>>>>>>> Use cases covered by v1 is already covered with v2 in addition to >>>>>>>> new methods. >>>>>>>> >>>>>>>> If there are objections please raise with a valid reason. >>>>>>>> >>>>>>>> [1] https://store.wso2.com/store/assets/esbconnector/?query=File >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> >>>>>>>> Malaka Silva >>>>>>>> Senior Tech Lead >>>>>>>> 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
Re: [Architecture] ESB Connector for Asana
Hi Nirthika, Great can we have a review before publishing next week. You can come to our office or have it via google hangout? On Thu, May 26, 2016 at 8:20 PM, Nirthika Rajendran < nirthika.rajend...@gmail.com> wrote: > Hi Malaka, > > We have completed most of the part of asana connector including > >1. Develop the methods >2. Implement integration testing. >3. Complete documentation. > > > Thank you, > Nirthika R > > On Wed, May 4, 2016 at 7:45 AM, Malaka Silva <mal...@wso2.com> wrote: > >> Good progress. Keep us posted. >> >> On Wed, May 4, 2016 at 5:39 AM, Nirthika Rajendran < >> nirthika.rajend...@gmail.com> wrote: >> >>> Hi Malaka, >>> >>> Yesterday we meet our mentor Kesavan to clear some problem in >>> integration test. There we correct some errors and now we continue the task. >>> >>> Thank you. >>> >>> On Tue, May 3, 2016 at 11:58 AM, Nirthika Rajendran < >>> nirthika.rajend...@gmail.com> wrote: >>> >>>> ok, thank you. >>>> >>>> On Tue, May 3, 2016 at 11:21 AM, Malaka Silva <mal...@wso2.com> wrote: >>>> >>>>> After finishing the integration tests should be fine. >>>>> >>>>> On Tue, May 3, 2016 at 9:18 AM, Nirthika Rajendran < >>>>> nirthika.rajend...@gmail.com> wrote: >>>>> >>>>>> Hi Malaka, >>>>>> >>>>>> Thank you, we already have two mentors Miss. Keerthika and Mr. >>>>>> Kesavan. So if we have any other problem we will contact you. >>>>>> >>>>>> Can we have the hangout after finishing the integration test or it is >>>>>> necessary to do now? >>>>>> >>>>>> Thank you. >>>>>> >>>>>> On Mon, May 2, 2016 at 9:31 PM, Malaka Silva <mal...@wso2.com> wrote: >>>>>> >>>>>>> Hi Nirthika, >>>>>>> >>>>>>> Let us know if you need any assistance to complete this? >>>>>>> >>>>>>> We can have a hangout to review the work you have done so far if >>>>>>> possible? >>>>>>> >>>>>>> On Wed, Mar 9, 2016 at 4:08 PM, Nirthika Rajendran < >>>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>>> >>>>>>>> Thank you Malaka, >>>>>>>> >>>>>>>> Sure we also expect that. >>>>>>>> >>>>>>>> On Wed, Mar 9, 2016 at 3:38 PM, Malaka Silva <mal...@wso2.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi Nirthika, >>>>>>>>> >>>>>>>>> Good progress. We are also planning to arrange a meetup at Jaffna >>>>>>>>> office in April. Feel free to come. >>>>>>>>> >>>>>>>>> On Wed, Mar 9, 2016 at 1:35 PM, Nirthika Rajendran < >>>>>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Hi Malaka, >>>>>>>>>> >>>>>>>>>> Every members in my team nearly take 10 methods and do the >>>>>>>>>> documentation and integration test for their part also. >>>>>>>>>> >>>>>>>>>> Now we all finished about 40 methods and user documentation. >>>>>>>>>> >>>>>>>>>> This month we have final semi examination, So we plan to continue >>>>>>>>>> the remaining part after the exam. >>>>>>>>>> >>>>>>>>>> Thank you >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> Nirthika Rajendran >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Sun, Feb 21, 2016 at 7:24 AM, Malaka Silva <mal...@wso2.com> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Nirthika, >>>>>>>>>>> >>>>>>>>>>> Good progress. >>>>>>>>>>> >>>>>>>>>>
Re: [Architecture] Deprecating File Connector V1
Did we profile the memory while doing this? On Mon, May 23, 2016 at 8:49 AM, Yashothara Shanmugarajah < yashoth...@wso2.com> wrote: > Hi all, > > I have completed the adding streaming feature to file read method in File > connector version 2. It works fine until 1 Gb as ESB. > > Thanks. > > Best Regards, > Yashothara.S > > Software Engineer > WSO2 > > > On Wed, May 4, 2016 at 10:40 AM, Vivekananthan Sivanayagam < > vivekanant...@wso2.com> wrote: > >> Hi , >> >> The method FileRename includes in file connector version 1, but not in a >> version 2. We can do this using FileMove operation. We can deprecate V1. >> >> >> >> >> *Thank youVivekananthan Sivanayagam* >> >> *Associate Software Engineer | WSO2* >> >> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>* >> *M:+94752786138 <%2B94752786138>* >> >> On Wed, May 4, 2016 at 9:18 AM, Yashothara Shanmugarajah < >> yashoth...@wso2.com> wrote: >> >>> We can add streaming parameter to read operation in version 2. >>> >>> Best Regards, >>> Yashothara.S >>> >>> Software Engineer >>> WSO2 >>> >>> >>> On Wed, May 4, 2016 at 9:11 AM, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> Yashothara yes you are correct. Best is we incorporate streaming to >>>> read operation with the new sender operation (you are already writing) then >>>> deprecate V1. >>>> >>>> Any other use cases? >>>> >>>> On Wed, May 4, 2016 at 9:01 AM, Yashothara Shanmugarajah < >>>> yashoth...@wso2.com> wrote: >>>> >>>>> In file connector Version 2, there is no streaming parameter in file >>>>> read method. But in version 1 it has. Is it ok? >>>>> >>>>> Best Regards, >>>>> Yashothara.S >>>>> >>>>> Software Engineer >>>>> WSO2 >>>>> >>>>> >>>>> On Wed, May 4, 2016 at 8:09 AM, Malaka Silva <mal...@wso2.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> Currently we have two connector versions for file operations with >>>>>> ESB. [1] >>>>>> >>>>>> Reason we implemented another version is to make the ESB integration >>>>>> flows more user friendly and better error handling >>>>>> >>>>>> Use cases covered by v1 is already covered with v2 in addition to new >>>>>> methods. >>>>>> >>>>>> If there are objections please raise with a valid reason. >>>>>> >>>>>> [1] https://store.wso2.com/store/assets/esbconnector/?query=File >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> Malaka Silva >>>>>> Senior Tech Lead >>>>>> 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 >>>>>> http://www.wso2.com/ >>>>>> http://www.wso2.com/about/team/malaka-silva/ >>>>>> <http://wso2.com/about/team/malaka-silva/> >>>>>> https://store.wso2.com/store/ >>>>>> >>>>>> Save a tree -Conserve nature & Save the world for your future. Print >>>>>> this email only if it is absolutely necessary. >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> Best Regards, >>>> >>>> Malaka Silva >>>> Senior Tech Lead >>>> 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 >>>> http://www.wso2.com/ >>>> http://www.wso2.com/about/team/malaka-silva/ >>>> <http://wso2.com/about/team/malaka-silva/> >>>> https://store.wso2.com/store/ >>>> >>>> Save a tree -Conserve nature & Save the world for your future. Print >>>> this email only if it is absolutely necessary. >>>> >>> >>> >> > -- Best Regards, Malaka Silva Senior Tech Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] Working With VFS Sender in ESB
Hi Yashothara, Have we implemented this feature? On Wed, May 4, 2016 at 12:54 PM, Yashothara Shanmugarajah < yashoth...@wso2.com> wrote: > Hi all, > > I have herewith attached the link [1] to my milestone plan for the File > Connector project. Please be kind enough to provide necessary feedback, at > your convenience. > > Please let me know if there's anything else that I should work on or that > you think I missed. > > [1] > https://docs.google.com/spreadsheets/d/15AZGjb4IvdGizUlybLIyD9hHKvWLstyqGm8_f1ocdBI/edit#gid=0 > > Best Regards, > Yashothara.S > > Software Engineer > WSO2 > > > On Wed, May 4, 2016 at 8:05 AM, Yashothara Shanmugarajah < > yashoth...@wso2.com> wrote: > >> Current File connector V2 doesn't have feature for VFS sender. I will >> share the milestone. >> >> Best Regards, >> Yashothara.S >> >> Software Engineer >> WSO2 >> >> >> On Wed, May 4, 2016 at 8:00 AM, Malaka Silva <mal...@wso2.com> wrote: >> >>> Can you share a milestone plan please. >>> >>> Also my understanding is current requirement is not covered with file >>> connector v2? >>> >>> On Wed, May 4, 2016 at 7:57 AM, Yashothara Shanmugarajah < >>> yashoth...@wso2.com> wrote: >>> >>>> Hi, >>>> >>>> I have started to implement new method for doing the VFS sender feature >>>> in file connector. Try to finish as soon as possible. >>>> >>>> Best Regards, >>>> Yashothara.S >>>> >>>> Software Engineer >>>> WSO2 >>>> >>>> >>>> On Wed, May 4, 2016 at 7:51 AM, Malaka Silva <mal...@wso2.com> wrote: >>>> >>>>> Hi Yashothara, >>>>> >>>>> What is the update. how are you proceeding with the feature? >>>>> >>>>> On Mon, Apr 25, 2016 at 8:29 AM, Yashothara Shanmugarajah < >>>>> yashoth...@wso2.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> As the summary of my results of file connector (file move), herewith >>>>>> I have attached two graphs which is specifying heap memory usage when >>>>>> streaming in default VFS sender in ESB and using File connector. >>>>>> >>>>>> Best Regards, >>>>>> Yashothara.S >>>>>> >>>>>> Software Engineer >>>>>> WSO2 >>>>>> >>>>>> >>>>>> On Mon, Apr 25, 2016 at 6:23 AM, Malaka Silva <mal...@wso2.com> >>>>>> wrote: >>>>>> >>>>>>> Yashothara the idea should be if this (VFS sender) is currently not >>>>>>> supported with file connector, incorporate the functionality to the >>>>>>> connector. >>>>>>> >>>>>>> On Sun, Apr 24, 2016 at 6:04 PM, Yashothara Shanmugarajah < >>>>>>> yashoth...@wso2.com> wrote: >>>>>>> >>>>>>>> This was default vfs sender. But I have used file connector as the >>>>>>>> sender and I got snapshots for that. I will update the graph for file >>>>>>>> connector soon. >>>>>>>> >>>>>>>> Thank you. >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> Yashothara.S >>>>>>>> >>>>>>>> Software Engineer >>>>>>>> WSO2 >>>>>>>> >>>>>>>> >>>>>>>> On Sun, Apr 24, 2016 at 8:03 AM, Malaka Silva <mal...@wso2.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Did you use fileconnector as the sender? or default vfs sender? >>>>>>>>> >>>>>>>>> On Fri, Apr 22, 2016 at 1:43 PM, Yashothara Shanmugarajah < >>>>>>>>> yashoth...@wso2.com> wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> As the summary of my results herewith I have attached two graphs >>>>>>>>>> which is specifying heap memory usage when streaming and not >>>>>>>>>> streaming. >>>>>>>>>> >>>>>>&
Re: [Architecture] [PET][IS] Improve Duo security Authenticator and Provisioning
Hi Thulasika, Find my comments inline. On Wed, May 11, 2016 at 3:03 PM, Thulasika Vijayanathan <thulas...@wso2.com> wrote: > Hi , > > I have planned to improve the DUO security Authenticator and Provisioning > connector. > > Existing Duo security authenticator and provisioning was implemented with > IS 5.0.0.I am working to improve the authenticator and Provisioning to > support with IS 5.1.0 and improve the provisioning such that authenticator > provisions the user in Duo security just-in-time of the first > authentication using its > > provisioning APIs. > You mean provision user to local user store. If that is the case why do we need provisioning APIs . Can you explain this a bit please? > > Duo Security is a two-step verification service the provides additional > security for access to data.If users want to authenticate themselves, they > can use their personal, one-time-valid, dynamic pass code consisting of > digits which is generated using mobile Duo app or sent via SMS. It mainly > uses Mobile Phone two-factor authentication to ensure secure login[1]. > > > [1]. https://duo.com/docs/adminapi#overview > > Thanks. > > -- > Thulasika > Associate Software Engineer > Mobile:0778014295 > email: thulas...@wso2.com <sanj...@wso2.com> > -- Best Regards, Malaka Silva Senior Tech Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [ESB Connectors] Handling call mediator blocking mode using a synapse level property
Hi, Can we finalize this before ESB 5.0.0 beta release please? On Wed, Apr 20, 2016 at 9:47 PM, Malaka Silva <mal...@wso2.com> wrote: > Find my comments, > > On Wed, Apr 20, 2016 at 6:12 PM, Akila Ravihansa Perera < > raviha...@wso2.com> wrote: > >> Hi Malaka, >> >> Call mediator already supports "blocking" mode as per [1]. Is it >> something else that you are looking for? >> > Same is what I mentioned in the above example . > >> >> Can you explain the requirement to do blocking mode operations in context >> of connectors? The mediation is paused anyway when using call mediator. >> > Call mediation will continue from that point on wards when response comes > back to ESB. I am referring to the thread behavior. After requests are sent > to BE thread will be released. When response comes it'll use a different > thread. > > Some use cases are, handling transactions with JMS,(ESB - > MB guaranteed delivery use cases) implementing sequential execution (When > throttling is there in apis) with iterator mediator, etc. > >> >> [1] https://docs.wso2.com/display/ESB490/Call+Mediator >> >> Thanks. >> >> On Wed, Apr 20, 2016 at 5:33 PM, Malaka Silva <mal...@wso2.com> wrote: >> >>> Hi All, >>> >>> Currently in all connectors we are using call mediator almost in every >>> method. Sometimes there is a requirement to use the call mediator in >>> blocking mode within connectors. >>> >>> If we need to do that we may have to modify the connectors like >>> following using filter mediator. >>> >>> Shall we introduce a property(synapse level) to control this behavior >>> from ESB 5.0.0? or are there any better solutions? >>> >>> >>> >>> >>> >>> >>> >>> 6 >>> fault >>> >>> >>> 2000 >>> >>> 1.0 >>> 3000 >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> 6 >>> fault >>> >>> >>> 2000 >>> >>> 1.0 >>> 3000 >>> >>> >>> >>> >>> >>> >>> >>> Best Regards, >>> >>> Malaka Silva >>> Senior Tech Lead >>> 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 >>> http://www.wso2.com/ >>> http://www.wso2.com/about/team/malaka-silva/ >>> <http://wso2.com/about/team/malaka-silva/> >>> https://store.wso2.com/store/ >>> >>> Save a tree -Conserve nature & Save the world for your future. Print >>> this email only if it is absolutely necessary. >>> >>> ___ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Akila Ravihansa Perera >> WSO2 Inc.; http://wso2.com/ >> >> Blog: http://ravihansa3000.blogspot.com >> >> _______ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > Best Regards, > > Malaka Silva > Senior Tech Lead > 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://mrma
Re: [Architecture] Token2 Provisioning connector and Authenticator for IS
Hi Kanapriya, Can't we pretty much cover the same requirement with SMS OTP, Google TOTP authenticators? Shall we go for a hardware based two factor authinticator with token2? On Thu, May 5, 2016 at 4:37 PM, Kanapriya Kuleswararajan <kanapr...@wso2.com > wrote: > Hi All, > > I have planned to create Token2 Provisioning connector and Two Factor IS > authenticator. > > Token2 [1] is a simple hosted two factor authentication provider designed > to protect primarily Web based applications (e.g. member area of a CMS > based website). > > It is providing various security solutions, such as hardware token, a > mobile application, TOTPRadius server and Token2 API > > In the authenticator, I am going to choose Token2 Mobile OTP [2]. > >- By using Token2 API , can create user. > > >- In the response we can get the user_id and QR Image url and mapping >those in user claims by association. > > >- With the user_id and Token2 API , can generate and send the OTP by >mail or sms and authenticate the user. > > >- With the QR Image URL , can scan the QR image and authenticate the >user. > > Herewith I have attached the provisioning and authenticator diagram. > > > > > > Please let me know if there's any suggestion that I should work on. > > [1] https://token2.com/?content=about > [2] https://token2.com/?content=mobileapp > > > Thanks > Kanapriya Kuleswararajan > Associate Software Engineer > Mobile : - 0774894438 > Mail : - kanapr...@wso2.com > -- Best Regards, Malaka Silva Senior Tech Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Deprecating File Connector V1
Yashothara yes you are correct. Best is we incorporate streaming to read operation with the new sender operation (you are already writing) then deprecate V1. Any other use cases? On Wed, May 4, 2016 at 9:01 AM, Yashothara Shanmugarajah < yashoth...@wso2.com> wrote: > In file connector Version 2, there is no streaming parameter in file read > method. But in version 1 it has. Is it ok? > > Best Regards, > Yashothara.S > > Software Engineer > WSO2 > > > On Wed, May 4, 2016 at 8:09 AM, Malaka Silva <mal...@wso2.com> wrote: > >> Hi, >> >> Currently we have two connector versions for file operations with ESB. [1] >> >> Reason we implemented another version is to make the ESB integration >> flows more user friendly and better error handling >> >> Use cases covered by v1 is already covered with v2 in addition to new >> methods. >> >> If there are objections please raise with a valid reason. >> >> [1] https://store.wso2.com/store/assets/esbconnector/?query=File >> >> Best Regards, >> >> Malaka Silva >> Senior Tech Lead >> 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 >> http://www.wso2.com/ >> http://www.wso2.com/about/team/malaka-silva/ >> <http://wso2.com/about/team/malaka-silva/> >> https://store.wso2.com/store/ >> >> Save a tree -Conserve nature & Save the world for your future. Print this >> email only if it is absolutely necessary. >> > > -- Best Regards, Malaka Silva Senior Tech Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] Deprecating File Connector V1
Hi, Currently we have two connector versions for file operations with ESB. [1] Reason we implemented another version is to make the ESB integration flows more user friendly and better error handling Use cases covered by v1 is already covered with v2 in addition to new methods. If there are objections please raise with a valid reason. [1] https://store.wso2.com/store/assets/esbconnector/?query=File Best Regards, Malaka Silva Senior Tech Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] ESB Connector for Asana
Good progress. Keep us posted. On Wed, May 4, 2016 at 5:39 AM, Nirthika Rajendran < nirthika.rajend...@gmail.com> wrote: > Hi Malaka, > > Yesterday we meet our mentor Kesavan to clear some problem in integration > test. There we correct some errors and now we continue the task. > > Thank you. > > On Tue, May 3, 2016 at 11:58 AM, Nirthika Rajendran < > nirthika.rajend...@gmail.com> wrote: > >> ok, thank you. >> >> On Tue, May 3, 2016 at 11:21 AM, Malaka Silva <mal...@wso2.com> wrote: >> >>> After finishing the integration tests should be fine. >>> >>> On Tue, May 3, 2016 at 9:18 AM, Nirthika Rajendran < >>> nirthika.rajend...@gmail.com> wrote: >>> >>>> Hi Malaka, >>>> >>>> Thank you, we already have two mentors Miss. Keerthika and Mr. Kesavan. >>>> So if we have any other problem we will contact you. >>>> >>>> Can we have the hangout after finishing the integration test or it is >>>> necessary to do now? >>>> >>>> Thank you. >>>> >>>> On Mon, May 2, 2016 at 9:31 PM, Malaka Silva <mal...@wso2.com> wrote: >>>> >>>>> Hi Nirthika, >>>>> >>>>> Let us know if you need any assistance to complete this? >>>>> >>>>> We can have a hangout to review the work you have done so far if >>>>> possible? >>>>> >>>>> On Wed, Mar 9, 2016 at 4:08 PM, Nirthika Rajendran < >>>>> nirthika.rajend...@gmail.com> wrote: >>>>> >>>>>> Thank you Malaka, >>>>>> >>>>>> Sure we also expect that. >>>>>> >>>>>> On Wed, Mar 9, 2016 at 3:38 PM, Malaka Silva <mal...@wso2.com> wrote: >>>>>> >>>>>>> Hi Nirthika, >>>>>>> >>>>>>> Good progress. We are also planning to arrange a meetup at Jaffna >>>>>>> office in April. Feel free to come. >>>>>>> >>>>>>> On Wed, Mar 9, 2016 at 1:35 PM, Nirthika Rajendran < >>>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>>> >>>>>>>> Hi Malaka, >>>>>>>> >>>>>>>> Every members in my team nearly take 10 methods and do the >>>>>>>> documentation and integration test for their part also. >>>>>>>> >>>>>>>> Now we all finished about 40 methods and user documentation. >>>>>>>> >>>>>>>> This month we have final semi examination, So we plan to continue >>>>>>>> the remaining part after the exam. >>>>>>>> >>>>>>>> Thank you >>>>>>>> >>>>>>>> Regards, >>>>>>>> Nirthika Rajendran >>>>>>>> >>>>>>>> >>>>>>>> On Sun, Feb 21, 2016 at 7:24 AM, Malaka Silva <mal...@wso2.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi Nirthika, >>>>>>>>> >>>>>>>>> Good progress. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Sat, Feb 20, 2016 at 7:51 PM, Nirthika Rajendran < >>>>>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Thank you Malaka, >>>>>>>>>> >>>>>>>>>> Now we finished nearly 35 Methods, and going to develop >>>>>>>>>> documentation. >>>>>>>>>> We contact some staff from Jaffna branch as our mentors (Ms. M. >>>>>>>>>> Keerthika). They also help us >>>>>>>>>> >>>>>>>>>> I will put the time window soon. >>>>>>>>>> >>>>>>>>>> Thank you, >>>>>>>>>> Nirthika Rajendran. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Sat, Feb 20, 2016 at 12:26 PM, Malaka Silva <mal...@wso2.com> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Looks good. Guess you are covering quite a lot of methods
Re: [Architecture] [Dev] [Pet Project] Velocity Template Mediator for ESB
gt;>>> >>>>> >>>>>>>>> property-type="string|om" scope="synapse|axis2|operation" /> >>>>> >>>>> >>>>> >>>>> Thanks, >>>>> Asanka D >>>>> >>>>> -- >>>>> >>>>> >>>>> *Asanka DissanayakeSoftware Engineer* >>>>> *WSO2 Inc. - lean . enterprise . middleware | wso2.com >>>>> <http://wso2.com/>* >>>>> >>>>> *email: asan...@wso2.com <ruch...@wso2.com>, blog: >>>>> cyberwaadiya.blogspot.com >>>>> <http://cyberwaadiya.blogspot.com>, asankastechtalks.wordpress.com >>>>> <http://asankastechtalks.wordpress.com> mobile: +94 71 8373821* >>>>> >>>>> ___ >>>>> Architecture mailing list >>>>> Architecture@wso2.org >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Thank you and Best Regards, >>>> Chanaka Fernando >>>> Senior Technical Lead >>>> WSO2, Inc.; http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> mobile: +94 773337238 >>>> Blog : http://soatutorials.blogspot.com >>>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 >>>> Twitter:https://twitter.com/chanakaudaya >>>> >>>> >>>> >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> d...@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> >>> >>> *Asanka DissanayakeSoftware Engineer* >>> *WSO2 Inc. - lean . enterprise . middleware | wso2.com >>> <http://wso2.com/>* >>> >>> *email: asan...@wso2.com <ruch...@wso2.com>, blog: >>> cyberwaadiya.blogspot.com >>> <http://cyberwaadiya.blogspot.com>, asankastechtalks.wordpress.com >>> <http://asankastechtalks.wordpress.com> mobile: +94 71 8373821* >>> >> >> >> >> -- >> Thank you and Best Regards, >> Chanaka Fernando >> Senior Technical Lead >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> mobile: +94 773337238 >> Blog : http://soatutorials.blogspot.com >> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 >> Twitter:https://twitter.com/chanakaudaya >> >> >> >> >> > > > -- > > > *Asanka DissanayakeSoftware Engineer* > *WSO2 Inc. - lean . enterprise . middleware | wso2.com <http://wso2.com/>* > > *email: asan...@wso2.com <ruch...@wso2.com>, blog: > cyberwaadiya.blogspot.com > <http://cyberwaadiya.blogspot.com>, asankastechtalks.wordpress.com > <http://asankastechtalks.wordpress.com> mobile: +94 71 8373821* > > ___ > Dev mailing list > d...@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Best Regards, Malaka Silva Senior Tech Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] ESB Connector for Asana
After finishing the integration tests should be fine. On Tue, May 3, 2016 at 9:18 AM, Nirthika Rajendran < nirthika.rajend...@gmail.com> wrote: > Hi Malaka, > > Thank you, we already have two mentors Miss. Keerthika and Mr. Kesavan. So > if we have any other problem we will contact you. > > Can we have the hangout after finishing the integration test or it is > necessary to do now? > > Thank you. > > On Mon, May 2, 2016 at 9:31 PM, Malaka Silva <mal...@wso2.com> wrote: > >> Hi Nirthika, >> >> Let us know if you need any assistance to complete this? >> >> We can have a hangout to review the work you have done so far if possible? >> >> On Wed, Mar 9, 2016 at 4:08 PM, Nirthika Rajendran < >> nirthika.rajend...@gmail.com> wrote: >> >>> Thank you Malaka, >>> >>> Sure we also expect that. >>> >>> On Wed, Mar 9, 2016 at 3:38 PM, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> Hi Nirthika, >>>> >>>> Good progress. We are also planning to arrange a meetup at Jaffna >>>> office in April. Feel free to come. >>>> >>>> On Wed, Mar 9, 2016 at 1:35 PM, Nirthika Rajendran < >>>> nirthika.rajend...@gmail.com> wrote: >>>> >>>>> Hi Malaka, >>>>> >>>>> Every members in my team nearly take 10 methods and do the >>>>> documentation and integration test for their part also. >>>>> >>>>> Now we all finished about 40 methods and user documentation. >>>>> >>>>> This month we have final semi examination, So we plan to continue the >>>>> remaining part after the exam. >>>>> >>>>> Thank you >>>>> >>>>> Regards, >>>>> Nirthika Rajendran >>>>> >>>>> >>>>> On Sun, Feb 21, 2016 at 7:24 AM, Malaka Silva <mal...@wso2.com> wrote: >>>>> >>>>>> Hi Nirthika, >>>>>> >>>>>> Good progress. >>>>>> >>>>>> >>>>>> On Sat, Feb 20, 2016 at 7:51 PM, Nirthika Rajendran < >>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>> >>>>>>> Thank you Malaka, >>>>>>> >>>>>>> Now we finished nearly 35 Methods, and going to develop >>>>>>> documentation. >>>>>>> We contact some staff from Jaffna branch as our mentors (Ms. M. >>>>>>> Keerthika). They also help us >>>>>>> >>>>>>> I will put the time window soon. >>>>>>> >>>>>>> Thank you, >>>>>>> Nirthika Rajendran. >>>>>>> >>>>>>> >>>>>>> On Sat, Feb 20, 2016 at 12:26 PM, Malaka Silva <mal...@wso2.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Looks good. Guess you are covering quite a lot of methods. What is >>>>>>>> the time window for this project? >>>>>>>> >>>>>>>> When we say complete connector, it should be all of the following. >>>>>>>> >>>>>>>>1. Develop the methods and do developer testing. >>>>>>>>2. Implement integration testing. >>>>>>>>3. Complete documentation. >>>>>>>> >>>>>>>> It's good if you can cover all the methods you mention. However if >>>>>>>> there are any time contains better to limit only important methods for >>>>>>>> the >>>>>>>> first version. >>>>>>>> >>>>>>>> On Sat, Feb 20, 2016 at 10:38 AM, Nirthika Rajendran < >>>>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>>>> >>>>>>>>> Hi All, >>>>>>>>> We plan to implement Asana connector as our 3rd year project for >>>>>>>>> "Rapid Application Development" course. We plan to include the >>>>>>>>> following >>>>>>>>> methods into the connector: >>>>>>>>> >>>>>>>>> - Attachments >>>>>>>>> <https://asana.com/developers/api-reference/attachments> >>>>>>>>> >
Re: [Architecture] ESB Connector for Asana
Hi Nirthika, Let us know if you need any assistance to complete this? We can have a hangout to review the work you have done so far if possible? On Wed, Mar 9, 2016 at 4:08 PM, Nirthika Rajendran < nirthika.rajend...@gmail.com> wrote: > Thank you Malaka, > > Sure we also expect that. > > On Wed, Mar 9, 2016 at 3:38 PM, Malaka Silva <mal...@wso2.com> wrote: > >> Hi Nirthika, >> >> Good progress. We are also planning to arrange a meetup at Jaffna office >> in April. Feel free to come. >> >> On Wed, Mar 9, 2016 at 1:35 PM, Nirthika Rajendran < >> nirthika.rajend...@gmail.com> wrote: >> >>> Hi Malaka, >>> >>> Every members in my team nearly take 10 methods and do the documentation >>> and integration test for their part also. >>> >>> Now we all finished about 40 methods and user documentation. >>> >>> This month we have final semi examination, So we plan to continue the >>> remaining part after the exam. >>> >>> Thank you >>> >>> Regards, >>> Nirthika Rajendran >>> >>> >>> On Sun, Feb 21, 2016 at 7:24 AM, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> Hi Nirthika, >>>> >>>> Good progress. >>>> >>>> >>>> On Sat, Feb 20, 2016 at 7:51 PM, Nirthika Rajendran < >>>> nirthika.rajend...@gmail.com> wrote: >>>> >>>>> Thank you Malaka, >>>>> >>>>> Now we finished nearly 35 Methods, and going to develop documentation. >>>>> We contact some staff from Jaffna branch as our mentors (Ms. M. >>>>> Keerthika). They also help us >>>>> >>>>> I will put the time window soon. >>>>> >>>>> Thank you, >>>>> Nirthika Rajendran. >>>>> >>>>> >>>>> On Sat, Feb 20, 2016 at 12:26 PM, Malaka Silva <mal...@wso2.com> >>>>> wrote: >>>>> >>>>>> Looks good. Guess you are covering quite a lot of methods. What is >>>>>> the time window for this project? >>>>>> >>>>>> When we say complete connector, it should be all of the following. >>>>>> >>>>>>1. Develop the methods and do developer testing. >>>>>>2. Implement integration testing. >>>>>>3. Complete documentation. >>>>>> >>>>>> It's good if you can cover all the methods you mention. However if >>>>>> there are any time contains better to limit only important methods for >>>>>> the >>>>>> first version. >>>>>> >>>>>> On Sat, Feb 20, 2016 at 10:38 AM, Nirthika Rajendran < >>>>>> nirthika.rajend...@gmail.com> wrote: >>>>>> >>>>>>> Hi All, >>>>>>> We plan to implement Asana connector as our 3rd year project for >>>>>>> "Rapid Application Development" course. We plan to include the following >>>>>>> methods into the connector: >>>>>>> >>>>>>> - Attachments >>>>>>> <https://asana.com/developers/api-reference/attachments> >>>>>>> >>>>>>>- Get single attachment >>>>>>>- Get all attachments >>>>>>>- Upload an attachment >>>>>>> >>>>>>> - Events <https://asana.com/developers/api-reference/events> >>>>>>> >>>>>>>- Get events on resource >>>>>>> >>>>>>> - Projects >>>>>>> <https://asana.com/developers/api-reference/projects> >>>>>>> >>>>>>>- Create a project >>>>>>>- Get single project >>>>>>>- Update a project >>>>>>>- Delete a project >>>>>>>- Query for projects >>>>>>>- Get project tasks >>>>>>>- Get project sections >>>>>>> >>>>>>> <https://asana.com/developers/api-reference/projects> >>>>>>> - Stories >>>>>>> <https://asana.com/developers/api-reference/stories> >>>>>>> >>>>>>>- Get stories on object >>>>>>>- Ge
Re: [Architecture] [ESB Connectors] Handling call mediator blocking mode using a synapse level property
Find my comments, On Wed, Apr 20, 2016 at 6:12 PM, Akila Ravihansa Perera <raviha...@wso2.com> wrote: > Hi Malaka, > > Call mediator already supports "blocking" mode as per [1]. Is it something > else that you are looking for? > Same is what I mentioned in the above example . > > Can you explain the requirement to do blocking mode operations in context > of connectors? The mediation is paused anyway when using call mediator. > Call mediation will continue from that point on wards when response comes back to ESB. I am referring to the thread behavior. After requests are sent to BE thread will be released. When response comes it'll use a different thread. Some use cases are, handling transactions with JMS,(ESB - MB guaranteed delivery use cases) implementing sequential execution (When throttling is there in apis) with iterator mediator, etc. > > [1] https://docs.wso2.com/display/ESB490/Call+Mediator > > Thanks. > > On Wed, Apr 20, 2016 at 5:33 PM, Malaka Silva <mal...@wso2.com> wrote: > >> Hi All, >> >> Currently in all connectors we are using call mediator almost in every >> method. Sometimes there is a requirement to use the call mediator in >> blocking mode within connectors. >> >> If we need to do that we may have to modify the connectors like following >> using filter mediator. >> >> Shall we introduce a property(synapse level) to control this behavior >> from ESB 5.0.0? or are there any better solutions? >> >> >> >> >> >> >> >> 6 >> fault >> >> >> 2000 >> 1.0 >> 3000 >> >> >> >> >> >> >> >> >> >> >> 6 >> fault >> >> >> 2000 >> 1.0 >> 3000 >> >> >> >> >> >> >> >> Best Regards, >> >> Malaka Silva >> Senior Tech Lead >> 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 >> http://www.wso2.com/ >> http://www.wso2.com/about/team/malaka-silva/ >> <http://wso2.com/about/team/malaka-silva/> >> https://store.wso2.com/store/ >> >> Save a tree -Conserve nature & Save the world for your future. Print this >> email only if it is absolutely necessary. >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Akila Ravihansa Perera > WSO2 Inc.; http://wso2.com/ > > Blog: http://ravihansa3000.blogspot.com > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, Malaka Silva Senior Tech Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] [ESB Connectors] Handling call mediator blocking mode using a synapse level property
Hi All, Currently in all connectors we are using call mediator almost in every method. Sometimes there is a requirement to use the call mediator in blocking mode within connectors. If we need to do that we may have to modify the connectors like following using filter mediator. Shall we introduce a property(synapse level) to control this behavior from ESB 5.0.0? or are there any better solutions? 6 fault 2000 1.0 3000 6 fault 2000 1.0 3000 Best Regards, Malaka Silva Senior Tech Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] Fwd: Using service account authentication to get accesstoken in esb connectors
+architecture -- Forwarded message -- From: Hariprasath Thanarajah <haripras...@wso2.com> Date: Sun, Apr 17, 2016 at 8:51 AM Subject: Using service account authentication to get accesstoken in esb connectors To: Malaka Silva <mal...@wso2.com> Cc: Kathees Rajendram <kath...@wso2.com>, Chanaka Fernando <chana...@wso2.com>, Kesavan Yogarajah <kesav...@wso2.com> Hi All, We usually create getAccessTokenFromCode, getAccessTokenFromRefreshToken and init to get accesstoken and authentication flow for ESB connectors. But in most of the API's, those all have the facility to get the accessToken using the JWT(Json Web Token). We have already developed the getAccessTokenFromServiceAccout for Google BigQuery. We can create this method for all Google API's since those all API's have the facility to get the AccessToken from the Service Account. I think we can create this method for other API's as well. If we create this method(/flow) then we don't need to create several flow for one API. You can find more on this in below links in [1], [1], https://developers.google.com/identity/protocols/OAuth2ServiceAccount, <https://developers.google.com/identity/protocols/OAuth2ServiceAccount> https://github.com/wso2-extensions/esb-connector-bigquery/blob/master/src/main/resources/bigquery-config/getAccessTokenFromServiceAccount.xml, <https://github.com/wso2-extensions/esb-connector-bigquery/blob/master/src/main/resources/bigquery-config/getAccessTokenFromServiceAccount.xml> https://github.com/wso2-extensions/esb-connector-bigquery/tree/master/src/main/java/org/wso2/carbon/connector, <https://github.com/wso2-extensions/esb-connector-bigquery/tree/master/src/main/java/org/wso2/carbon/connector> https://help.salesforce.com/HTViewHelpDoc?id=remoteaccess_oauth_jwt_flow.htm=en_US -- *Thank you and Regards**Hariprasath Thanarajah* Associate Software Engineer | WSO2 E: haripras...@wso2.com M: +94752806528, 0777216903 -- Best Regards, Malaka Silva Senior Tech Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Replacing current JS engine used in script mediator with new rhino and nashorn script engines
We have to check if all use cases are supported if we are going to upgrade or going for an alternative solutions. Also some connectors are heavily using script mediator. IMO we should not plan to do this for the immediate release. On Mon, Apr 11, 2016 at 12:34 PM, Vanjikumaran Sivajothy <va...@wso2.com> wrote: > With JDK 8, there is an in-build JS engine called Nashorn. Isn't that > worth to leverage the JS support by using native implementation to JDK 8? > > > [1] > http://www.oracle.com/technetwork/articles/java/jf14-nashorn-2126515.html > > On Sun, Apr 10, 2016 at 11:57 PM, Malaka Silva <mal...@wso2.com> wrote: > >> PrabathAR has already found a way to support this using existing rhino >> version. There is a configuration to optimize the execution. >> >> @PrabathAR - Can you give us more details on this please? >> >> On Mon, Apr 11, 2016 at 12:22 PM, Nuwan Pallewela <nuw...@wso2.com> >> wrote: >> >>> Hi All, >>> >>> There is a limitation in wso2 script mediator when we try to manipulate >>> payloads with JavaScript as the scripting language, when the Payload size >>> is larger than 64KB, ESB throws an exception. Cause for this is Rhino >>> version which is used by the script mediator has a limitation of handling >>> JavaScript objects of size 64KB or more. But rhino have fixed it in the >>> later versions. So we can include new rhino and nashorn engines as the >>> script engine for JS in script mediator and avoid the limitation of >>> handling larger payloads. >>> Can we do this improvement to ESB 5.0.0 release? >>> >>> Thanks, >>> Nuwan >>> >>> -- >>> -- >>> >>> *Nuwan Chamara Pallewela* >>> >>> >>> *Software Engineer* >>> >>> *WSO2, Inc. *http://wso2.com >>> *lean . enterprise . middleware* >>> >>> Email *nuw...@wso2.com <nuw...@wso2.com>* >>> Mobile *+94719079739 <%2B94719079739>@* >>> >>> >>> >>> _______ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> >> Best Regards, >> >> Malaka Silva >> Senior Tech Lead >> 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 >> http://www.wso2.com/ >> http://www.wso2.com/about/team/malaka-silva/ >> <http://wso2.com/about/team/malaka-silva/> >> https://store.wso2.com/store/ >> >> Save a tree -Conserve nature & Save the world for your future. Print this >> email only if it is absolutely necessary. >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Vanjikumaran Sivajothy > *Associate Technical Lead* > *WSO2 Inc. http://wso2.com <http://wso2.com/>* > *+1-925-464-6816* > [image: Facebook] <https://www.facebook.com/vanjikumaran> [image: Twitter] > <https://twitter.com/vanjikumaran> [image: LinkedIn] > <http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293> [image: > Blogger] <http://vanjikumaran.blogspot.com/> [image: SlideShare] > <http://www.slideshare.net/vanjikumaran> > > 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, re-transmit, 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@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, Malaka Silva Senior Tech Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Replacing current JS engine used in script mediator with new rhino and nashorn script engines
PrabathAR has already found a way to support this using existing rhino version. There is a configuration to optimize the execution. @PrabathAR - Can you give us more details on this please? On Mon, Apr 11, 2016 at 12:22 PM, Nuwan Pallewela <nuw...@wso2.com> wrote: > Hi All, > > There is a limitation in wso2 script mediator when we try to manipulate > payloads with JavaScript as the scripting language, when the Payload size > is larger than 64KB, ESB throws an exception. Cause for this is Rhino > version which is used by the script mediator has a limitation of handling > JavaScript objects of size 64KB or more. But rhino have fixed it in the > later versions. So we can include new rhino and nashorn engines as the > script engine for JS in script mediator and avoid the limitation of > handling larger payloads. > Can we do this improvement to ESB 5.0.0 release? > > Thanks, > Nuwan > > -- > -- > > *Nuwan Chamara Pallewela* > > > *Software Engineer* > > *WSO2, Inc. *http://wso2.com > *lean . enterprise . middleware* > > Email *nuw...@wso2.com <nuw...@wso2.com>* > Mobile *+94719079739 <%2B94719079739>@* > > > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, Malaka Silva Senior Tech Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [PET] Implement a Outlook Mail Connector and Authorization Code Grant Flow in Azure AD
yes On Thu, Mar 31, 2016 at 10:23 AM, Vivekananthan Sivanayagam < vivekanant...@wso2.com> wrote: > Hi Malaka, > > These are for "Azure AD Token Lifetime" > >- Access tokens last 1 hour >- Refresh tokens last for 14 days, > > If we use a refresh token within those 14 days, you will receive a new one > with a new validity window shifted forward of another 14 days. We can > repeat this trick for up to 90 days of total validity, then we’ll have to > re-authenticate. > > When we request additional access tokens with a refresh token , we can get > new access token along with refresh token. > > Do we have to take the new refresh token to replace the old one and store > in a registry? > > > > > *Thank youVivekananthan Sivanayagam* > > *Associate Software Engineer | WSO2* > > *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>* > *M:+94752786138 <%2B94752786138>* > > On Wed, Mar 30, 2016 at 10:56 PM, Vivekananthan Sivanayagam < > vivekanant...@wso2.com> wrote: > >> Hi Malaka, >> >> As you suggested , there are two types of consent , User Consent (consent >> provided by an end user), Admin Consent (consent provided by an >> administrator). When we call the Authorization Code Request , we can set >> using "prompt" parameter. Possible values are >> >>- login: The user should be prompted to re-authenticate. >>- consent: User consent has been granted, but needs to be updated. >>The user should be prompted to consent. >>- admin_consent: An administrator should be prompted to consent on >>behalf of all users in their organization. >> >> >> >> https://login.microsoftonline.com/common/oauth2/authorize?response_type=code_id=x_uri=http://www.wso2.com=login >> >> >> [1] https://msdn.microsoft.com/en-us/library/azure/dn645542.aspx >> [2] >> https://blogs.msdn.microsoft.com/exchangedev/2014/03/25/using-oauth2-to-access-calendar-contact-and-mail-api-in-office-365-exchange-online/ >> >> >> >> >> >> >> *Thank youVivekananthan Sivanayagam* >> >> *Associate Software Engineer | WSO2* >> >> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>* >> *M:+94752786138 <%2B94752786138>* >> >> On Thu, Mar 17, 2016 at 12:52 PM, Vivekananthan Sivanayagam < >> vivekanant...@wso2.com> wrote: >> >>> Hi Malaka, >>> >>> Noted. >>> >>> >>> >>> >>> *Thank youVivekananthan Sivanayagam* >>> >>> *Associate Software Engineer | WSO2* >>> >>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>* >>> *M:+94752786138 <%2B94752786138>* >>> >>> On Thu, Mar 17, 2016 at 10:58 AM, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> Hi Vivekananthan/Thulasika, >>>> >>>> In this typical OAUTH flow you mentioned, there is an user interaction. >>>> >>>> But for SAAS app use cases MS has provided Admin Consent to access the >>>> api. >>>> >>>> IMO we should have both the options in our connectors. >>>> >>>> [1] >>>> https://blogs.msdn.microsoft.com/exchangedev/2014/06/05/managing-user-consent-for-applications-using-office-365-apis/ >>>> [2] >>>> https://msdn.microsoft.com/en-us/office/office365/howto/common-app-authentication-tasks >>>> [3] https://msdn.microsoft.com/en-us/library/office/dn707383.aspx >>>> >>>> On Thu, Mar 17, 2016 at 1:00 AM, Vivekananthan Sivanayagam < >>>> vivekanant...@wso2.com> wrote: >>>> >>>>> Hi All, >>>>> >>>>> I am going to implement a connector for Microsoft office Outllook >>>>> Mail, for that I did a research on authentication part first and I have >>>>> shared below what I understood during the initial research. >>>>> >>>>> The Office 365 API[1] services use Azure Active Directory (Azure AD) >>>>> to provide secure authentication to users' Office 365 data. To access the >>>>> Office 365 APIs, we need to register our app with Azure AD[2]. At run >>>>> time, >>>>> created app can continue to use Azure AD and OAuth to authenticate >>>>> application requests[3]. >>>>> >>>>> Authorization Code Grant Flow Diagram >>>>> >>>>> [image: Inline image 1] >>>>> >>>>>1. The cli
Re: [Architecture] [C5] Artifact deployment coordination support for C5
loose the events even if listener is restarted. >>>>>>>> >>>>>>>> --Srinath. >>>>>>>> >>>>>>>> On Wed, Mar 23, 2016 at 10:45 AM, KasunG Gajasinghe < >>>>>>>> kas...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> Given several issues we discovered with automatic artifact >>>>>>>>> synchronization with DepSync in C4, we have discussed how to approach >>>>>>>>> this >>>>>>>>> problem in C5. >>>>>>>>> >>>>>>>>> We are thinking of not doing the automated artifact >>>>>>>>> synchronization in C5. Rather, users should use their own mechanism to >>>>>>>>> synchronize the artifacts across a cluster. Common approaches are >>>>>>>>> RSync as >>>>>>>>> a cron job and shell scripts. >>>>>>>>> >>>>>>>>> But, it is vital to know the artifact deployment status of the >>>>>>>>> nodes in the entire cluster from a central place. For that, we are >>>>>>>>> providing this deployment coordination feature. There will be two >>>>>>>>> ways to >>>>>>>>> use this. >>>>>>>>> >>>>>>>>> 1. JMS based publishing - the deployment status will be published >>>>>>>>> by each node to a jms topic/queue >>>>>>>>> >>>>>>>>> 2. Log based publishing - publish the logs by using a syslog >>>>>>>>> appender [1] or our own custom appender to a central location. >>>>>>>>> >>>>>>>>> The log publishing may not be limited to just the deployment >>>>>>>>> coordination. In a containerized deployment, the carbon products will >>>>>>>>> run >>>>>>>>> in disposable containers. But sometimes, the logs need to be backed >>>>>>>>> up for >>>>>>>>> later reference. This will help with that. >>>>>>>>> >>>>>>>>> Any thoughts on this matter? >>>>>>>>> >>>>>>>>> [1] >>>>>>>>> https://logging.apache.org/log4j/2.x/manual/appenders.html#SyslogAppender >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> KasunG >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> ~~--~~ >>>>>>>>> Sending this mail via my phone. Do excuse any typo or short replies >>>>>>>>> >>>>>>>>> ___ >>>>>>>>> Architecture mailing list >>>>>>>>> Architecture@wso2.org >>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> ==== >>>>>>>> Srinath Perera, Ph.D. >>>>>>>>http://people.apache.org/~hemapani/ >>>>>>>>http://srinathsview.blogspot.com/ >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Sameera Jayasoma, >>>>>>> Software Architect, >>>>>>> >>>>>>> WSO2, Inc. (http://wso2.com) >>>>>>> email: same...@wso2.com >>>>>>> blog: http://blog.sameera.org >>>>>>> twitter: https://twitter.com/sameerajayasoma >>>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections >>>>>>> Mobile: 0094776364456 >>>>>>> >>>>>>> Lean . Enterprise . Middleware >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Sameera Jayasoma, >>>>>> Software Architect, >>>>>> >>>>>> WSO2, Inc. (http://wso2.com) >>>>>> email: same...@wso2.com >>>>>> blog: http://blog.sameera.org >>>>>> twitter: https://twitter.com/sameerajayasoma >>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections >>>>>> Mobile: 0094776364456 >>>>>> >>>>>> Lean . Enterprise . Middleware >>>>>> >>>>>> >>>>>> ___ >>>>>> Architecture mailing list >>>>>> Architecture@wso2.org >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. >>>>> email: kasung AT spamfree wso2.com >>>>> linked-in: http://lk.linkedin.com/in/gajasinghe >>>>> blog: http://kasunbg.org >>>>> >>>>> >>>>> >>>>> ___ >>>>> Architecture mailing list >>>>> Architecture@wso2.org >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Nandika Jayawardana >>>> WSO2 Inc ; http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> ___ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> >>> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. >>> email: kasung AT spamfree wso2.com >>> linked-in: http://lk.linkedin.com/in/gajasinghe >>> blog: http://kasunbg.org >>> >>> >>> >>> ___ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Nandika Jayawardana >> WSO2 Inc ; http://wso2.com >> lean.enterprise.middleware >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. > email: kasung AT spamfree wso2.com > linked-in: http://lk.linkedin.com/in/gajasinghe > blog: http://kasunbg.org > > > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, Malaka Silva Senior Tech Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [PET] Improvement on Redmine connector
Hi Kalyani, Can we check if we can further improve the existing improved methods? eg:- Support all optional parameters, etc. On Wed, Mar 16, 2016 at 6:36 PM, Kalyani Yogeswaranathan <kaly...@wso2.com> wrote: > Hi All, > > I am going to improve Redmine connector[1]. For that I have analysed the > Redmine REST API. There are 3 type of status (stable,beta, alpha) methods > are available in the API [2]. > >- stable ( feature complete, no major changes planned ) >- beta (usable for integrations with some bugs or missing minor >functionality) >- alpha (major functionality in place, needs feedback from API users >and integrators ) > > All stable and beta type of methods were already implemented. And one of > the alpha type of method also implemented. > > For the improvement I am planning to do rest of the alpha methods. > > Now I am doing further research to find the methods in priority. When I > finished the further research I'll update this mail thread soon. > > Please let me know if you have any improvements/suggestion on Redmine > connector to implement. > > [1] https://docs.wso2.com/display/ESBCONNECTORS/Redmine+Connector > [2] http://www.redmine.org/projects/redmine/wiki/Rest_api > > -- > > *Kalyani Yogeswaranathan* > > *Associate software engineer* > *WSO2 Inc.* > > *Mobile: 0776390284 <0776390284>* > -- Best Regards, Malaka Silva Senior Tech Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [IS] Proposed Architectural Change for Authentication Framework
chain is completed the Coordinator will call the >> InboundProcessor to build the protocol specific response to be responded >> back. >> >> >> Any suggestions and thoughts are highly appreciated. >> >> Thanks. >> -- >> *Pulasthi Mahawithana* >> Software Engineer >> WSO2 Inc., http://wso2.com/ >> Mobile: +94-71-5179022 >> Blog: http://blog.pulasthi.org >> > > > > -- > *Pulasthi Mahawithana* > Software Engineer > WSO2 Inc., http://wso2.com/ > Mobile: +94-71-5179022 > Blog: http://blog.pulasthi.org > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, Malaka Silva Senior Tech Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [PET] Implement a Outlook Mail Connector and Authorization Code Grant Flow in Azure AD
Hi Vivekananthan/Thulasika, In this typical OAUTH flow you mentioned, there is an user interaction. But for SAAS app use cases MS has provided Admin Consent to access the api. IMO we should have both the options in our connectors. [1] https://blogs.msdn.microsoft.com/exchangedev/2014/06/05/managing-user-consent-for-applications-using-office-365-apis/ [2] https://msdn.microsoft.com/en-us/office/office365/howto/common-app-authentication-tasks [3] https://msdn.microsoft.com/en-us/library/office/dn707383.aspx On Thu, Mar 17, 2016 at 1:00 AM, Vivekananthan Sivanayagam < vivekanant...@wso2.com> wrote: > Hi All, > > I am going to implement a connector for Microsoft office Outllook Mail, > for that I did a research on authentication part first and I have shared > below what I understood during the initial research. > > The Office 365 API[1] services use Azure Active Directory (Azure AD) to > provide secure authentication to users' Office 365 data. To access the > Office 365 APIs, we need to register our app with Azure AD[2]. At run time, > created app can continue to use Azure AD and OAuth to authenticate > application requests[3]. > > Authorization Code Grant Flow Diagram > > [image: Inline image 1] > >1. The client application starts the flow by redirecting the user >agent to the Azure AD authorization endpoint. The user authenticates and >consents, if consent is required. >2. The Azure AD authorization endpoint redirects the user agent back >to the client application with an authorization code. The user agent >returns authorization code to the client application’s redirect URI. >3. The client application requests an access token from the Azure AD >token issuance endpoint. It presents the authorization code to prove that >the user has consented. >4. The Azure AD token issuance endpoint returns an access token and a >refresh token. The refresh token can be used to request additional access >tokens. >5. The client application uses the access token to authenticate to the >Web API. >6. After authenticating the client application, the web API returns >the requested data [4]. > > [1] > https://msdn.microsoft.com/en-us/office/office365/howto/rest-api-overview > <https://msdn.microsoft.com/en-us/office/office365/howto/rest-api-overview> > [2] > https://azure.microsoft.com/en-us/documentation/articles/active-directory-integrating-applications/#BKMK_Native > [3] https://msdn.microsoft.com/en-us/library/azure/dn645543.aspx > <https://msdn.microsoft.com/en-us/library/azure/dn645543.aspx> > [4] https://www.youtube.com/watch?v=TjuJE7Zc1Qk > > > > > *Thank youVivekananthan Sivanayagam* > > *Associate Software Engineer | WSO2* > > *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>* > *M:+94752786138 <%2B94752786138>* > -- Best Regards, Malaka Silva Senior Tech Lead 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 http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [PET] Office 365 Connector
Hi Vivekananthan, Please share the milestone plan. On Mon, Mar 14, 2016 at 1:44 PM, Vivekananthan Sivanayagam < vivekanant...@wso2.com> wrote: > Hi Malaka, > > Yes, I can. > > > > > *Thank youVivekananthan Sivanayagam* > > *Associate Software Engineer | WSO2* > > *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>* > *M:+94752786138 <%2B94752786138>* > > On Mon, Mar 14, 2016 at 1:40 PM, Malaka Silva <mal...@wso2.com> wrote: > >> Hi Vivekananthan, >> >> Can you start this please? >> >> On Thu, Mar 10, 2016 at 10:38 AM, Thulasika Vijayanathan < >> thulas...@wso2.com> wrote: >> >>> Hi Malaka, >>> >>> Yes, I will include the following methods for the initial version of >>> outlook connector. >>> >>> Messages >>> - Get a message by ID. >>> - Get a message collection >>> - Send a new message >>> - Reply to sender >>> - Reply to all >>> - Forward a message directly >>> - Delete a message >>> - Move a message >>> - Copy a message >>>Attachments >>> - Get an attachment collection >>> - Get an attachment >>> - Create a file attachment >>> - Delete attachments >>>Folders >>> - Get a folder collection >>> - Get a folder >>> >>> Thanks. >>> >>> On Thu, Mar 10, 2016 at 9:53 AM, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> Hi Thulashika, >>>> >>>> +1 for outlook connector. However we can limit the methods for the >>>> initial version. >>>> >>>> eg:- >>>>Messages >>>> - Get a message by ID. >>>> - Get a message collection >>>> - Send a new message >>>> - Reply to sender >>>> - Reply to all >>>> - Forward a message directly >>>> - Delete a message >>>>Attachments >>>> - Get an attachment collection >>>> - Get an attachment >>>> - Create a file attachment >>>> - Delete attachments >>>> >>>> WDYT? >>>> >>>> On Wed, Mar 9, 2016 at 4:08 PM, Thulasika Vijayanathan < >>>> thulas...@wso2.com> wrote: >>>> >>>>> Hi Malaka, >>>>> >>>>> Then we can implement multiple connectors for each APIs. So First I >>>>> will start to implement the connector for Mail API with following methods. >>>>> >>>>> Mail API :The Mail API lets you read, create, and send messages and >>>>> attachments, view and respond to event messages, and manage folders that >>>>> are secured by Azure Active Directory in Office 365. >>>>>Messages >>>>> - Get a message by ID. >>>>> - Get a message collection >>>>> - Send a new message >>>>> - Create a draft message >>>>> - Send a draft message >>>>> - Reply to sender >>>>> - Reply to all >>>>> - Create a draft reply message >>>>> - Create a draft reply-all message >>>>> - Forward a message directly >>>>> - Create a draft forward message >>>>> - Update a message >>>>> - Delete a message >>>>> - Move a message >>>>> - Copy a message >>>>>Attachments >>>>> - Get an attachment collection >>>>> - Get an attachment >>>>> - Create a file attachment >>>>> - Delete attachments >>>>>Folders >>>>> - Get a folder collection >>>>> - Get a folder >>>>> - Create a folder >>>>> - Update a folder >>>>> - Delete a folder >>>>> - Move a folder >>>>> - Copy a folder >>>>> >>>>> >>>>> Thanks. >>>>> >>>>> >>>>> On Wed, Mar 9, 2016 at 3:04 PM, Malaka Silva <mal...@wso2.com> wrote: >>>>> >>>>>> Hi Thulasika, >>>>>> >>>>>> Are we planning to do one connector or multiple connectors? >>>>>> >>>>>> IMO we should have separate connector for each domain. >>>>>> >>>>>> On Tue, Mar 8, 2016 at 8:53 PM, Thulasika Vijayanathan < >>>>>> thulas...@wso2.com> wrote: >>>&
