Re: [Architecture] ESB Connector for Nest API
Shakila, pls copy the attachment content onto the mail thread as not everyone on this thread will have access to the google doc On Tue, Nov 25, 2014 at 4:02 PM, Shakila Sivagnanarajah shak...@wso2.com wrote: Hi All, I have attached usecase for Nest ESB connector here. https://docs.google.com/a/wso2.com/document/d/1nufdnY3smyXoWXiYUEcep8Jku1HKBW8Zwdhf1TZtkP8/edit On Mon, Nov 24, 2014 at 10:18 PM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Need usecase for this. On Monday, November 24, 2014, Shakila Sivagnanarajah shak...@wso2.com wrote: Hi All, I (shak...@wso2.com) have planned to develop $subject. Please find the project plan here, *Introduction: * Nest API is a real-time data API (connect people with devices in their homes), offering subscription based access to data shared by Nest-devices. The Nest clients (created to access Nest device data) will use Firebase. Firebase provides a real time data synchronization service. *Operations:* Nest Learning Thermostat - View current temperature - View or set target temperature - Set fan timer - View or set temperature mode - View humidity - View online status and last connection information Nest Protect Smoke + CO Alarm - View CO or smoke status - View battery health state - View last manual test status and timestamp for last manual test - View online status and last connection information Home - View a list of devices in the home - View energy event status (Rush Hour Rewards) - View or set Away state - View postal or zip code - Set ETA *Authentication:* OAuth 2.0 (authorization) *API Summary:* Nest API v1.1 *Documentation URL:* https://developer.nest.com/documentation -- Shakila Sivagnanarajah Associate Software Engineer Mobile :+94 (0) 770 760240 shak...@wso2.com -- S.Uthaiyashankar VP Engineering WSO2 Inc. http://wso2.com/ - lean . enterprise . middleware Phone: +94 714897591 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Shakila Sivagnanarajah Associate Software Engineer Mobile :+94 (0) 770 760240 shak...@wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] ESB Connector for ZOHO Invoice
Ashalya, there are a lot of methods here which may not be doable in 3 weeks. Pls identify the main use cases around this app and build methods related to those. On Mon, Nov 24, 2014 at 1:04 PM, Sriashalya Srivathsan asha...@wso2.com wrote: I have planned to develop the $subject.Please find the project plan below. *Introduction* Zoho Invoice API gives the programmatic access to the Zoho Invoice service, allows to expand and build on the Zoho Invoice platform for small businesses across the globe[1]. *API Operations* *Contacts* -List contacts -Get contact -Create a contact -Update a contact -Delete a contact -Mark as active -Mark as inactive -Enable payment reminders -Disable payment reminders -Email statement -Get statement mail content -Email contact -List comments -List refunds *Estimates* -List estimates -Get an estimate -Create an estimate -Update an estimate -Delete an estimate -Mark an estimate as sent -Mark an estimate as accepted -Mark an estimate as declined -Email an estimate -Email an estimate -Get estimate email content -Bulk export estimates -Bulk print estimates -Update billing address -Update shipping address -List estimate template -Update estimate template *Invoices* -List invoices -Get an invoice -Create an invoice -Update an invoice -Delete an invoice -Mark an invoice as sent -Void an invoice -Mark as draft -Email an invoice -Email invoices -Get invoice email content -Remind customer -Bulk invoice reminder -Get payment reminder mail content -Bulk export invoices -Bulk print invoices -Disable payment reminder -Enable payment reminder -Write off invoice -Cancel write off -Update billing address -Update shipping address -List invoice templates -Update invoice template *Payment and credit* -List invoice payments -List credits applied -Apply credits -Delete a payment -Delete applied credit *Attachment* -Get an invoice attachment -Add attachment to an invoice -Update attachment preference -Delete an attachment -Delete the expense receipt *Recurring Invoices* -List recurring invoices -Get a recurring invoice -Create a recurring invoice -Update a recurring invoice -Delete a recurring invoice -Stop a recurring invoice -Resume a recurring invoice -Update recurring invoice template -List recurring invoice history *Credit Notes* -List credit notes -Get credit note -Create a credit note -Update credit note -Delete credit note -Convert to open -Void credit note -Email credit note -Email history -Get email content -Update billing address -Update shipping address -List credit note template -Update credit note template *Apply to invoice* -List invoices credited -Credit to an invoice -Delete invoices credited *Refunds* -List credit note refunds -List refunds of a credit note -Get credit note refund -Refund credit note -Update credit note refund -Delete credit note refund Customer Payments -List customer payments -Get a customer payment -Create a customer payment -Update a customer payment -Delete a customer payment Expenses -List expenses -Get an expense -Create an expense -Update an expense -Delete an expense -List expense comments history *Receipt* -Get an expense receipt -Add receipt to an expense -Delete a receipt *Authentication* Supports authtoken [1]https://www.zoho.com/invoice/api/v3 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] ESB Connector for Nest API
Shakila, if you need to use a third party library for this pls follow the the following tread (from Isabelle) to get it approved: subject - Must-follow process to bring 3rd party libraries into the WSO2 platform On Mon, Nov 24, 2014 at 12:56 PM, Shakila Sivagnanarajah shak...@wso2.com wrote: I will send the milestone plan by today On Mon, Nov 24, 2014 at 12:52 PM, Samisa Abeysinghe sam...@wso2.com wrote: What is the milestone plan? Thanks, Samisa... Samisa Abeysinghe Vice President Delivery WSO2 Inc. http://wso2.com On Mon, Nov 24, 2014 at 12:48 PM, Shakila Sivagnanarajah shak...@wso2.com wrote: Hi All, I (shak...@wso2.com) have planned to develop $subject. Please find the project plan here, *Introduction: * Nest API is a real-time data API (connect people with devices in their homes), offering subscription based access to data shared by Nest-devices. The Nest clients (created to access Nest device data) will use Firebase. Firebase provides a real time data synchronization service. *Operations:* Nest Learning Thermostat - View current temperature - View or set target temperature - Set fan timer - View or set temperature mode - View humidity - View online status and last connection information Nest Protect Smoke + CO Alarm - View CO or smoke status - View battery health state - View last manual test status and timestamp for last manual test - View online status and last connection information Home - View a list of devices in the home - View energy event status (Rush Hour Rewards) - View or set Away state - View postal or zip code - Set ETA *Authentication:* OAuth 2.0 (authorization) *API Summary:* Nest API v1.1 *Documentation URL:* https://developer.nest.com/documentation -- Shakila Sivagnanarajah Associate Software Engineer Mobile :+94 (0) 770 760240 shak...@wso2.com -- Shakila Sivagnanarajah Associate Software Engineer Mobile :+94 (0) 770 760240 shak...@wso2.com -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] ESB Connector | Yammer
Ok, that's fine Manil, pls send a handover mail denoting whats pending On Mon, Oct 27, 2014 at 12:15 PM, Manil Liyanage liyanagema...@gmail.com wrote: Hi Shevan, I have completed the configuration coding for the connector. But I haven't finished the Integration Testing. Is it possible for me to give the connector configurations I have completed or would it possible for me get more time for it since I'm doing it parallel with my final year project and it needs to be given by end of this year. Would it be possible for someone else to continue on this? Please advice me on this. On Mon, Oct 27, 2014 at 10:50 AM, Shevan Goonetilleke she...@wso2.com wrote: Hi Manil, Do you plan to progress this further? Thanks Shevan On Tue, Sep 16, 2014 at 4:36 PM, Manil Liyanage liyanagema...@gmail.com wrote: Hi Vanji, We dont have a much progress from the last place we stopped. But we are working on it now and we will be finishing it soon. Thanks, Manil On Tue, Sep 2, 2014 at 1:26 PM, Vanjikumaran Sivajothy va...@wso2.com wrote: Hi Manil, Is there any update on your connector project progress? Best Regards, Vanji On Fri, Jul 18, 2014 at 10:53 AM, Ramindu Deshapriya rasad...@gmail.com wrote: Hi Lasantha, Your point is correct, the decision needs to be made whether we would actually need to send an old message via email later on. Thanks. On Thu, Jul 17, 2014 at 8:01 AM, Lasantha Fernando lasan...@wso2.com wrote: Hi Ramindu, I haven't gone through the API deeply. But isn't emailing messages method there to email any message to the user, not just newly created ones? I mean, would a user be able to email any received message by invoking the 'Emailing messages' endpoint? If so, chaining the two methods together might mean a loss functionality for the user. I might have understood the API incorrectly, and if so please correct me... :-). Thanks, Lasantha On 16 July 2014 16:23, Ramindu Deshapriya rasad...@gmail.com wrote: Hi Manil, Looks like you're giving good coverage to all methods. That's great. I think you'd be able to cover the Emailing messages method when creating a message (specify whether or not to send the message as an email). I know it needs another API call, but you could chain them together to provide more easy-to-use functionality for the client. Vanjikumaran, the attachments api provides the ability to create a pending attachment, for which you will be given an ID which can then be attached to an individual message, thread etc. Thanks. On Wed, Jul 16, 2014 at 3:49 PM, Vanjikumaran Sivajothy va...@wso2.com wrote: I am not clear with the attachments API, Please do some more reading on that. Send your project plan with the detail work breakdown. Rest of them are looking good. On Wed, Jul 16, 2014 at 12:18 PM, Manil Liyanage liyanagema...@gmail.com wrote: *Introduction* Yammer is a private social network that helps employees collaborate across departments, locations and business apps. The Yammer API is a rest based one. It has GET, POST, PUT and DELETE methods. *Yammer Connector Summary* • Connector Name: yammer-connector-1.0.0 • Version: 1.0.0 • Technology: REST *Authentication* Yammer API uses OAuth2 based authentication *Selected API Methods* *Messages* Public messages Feed Algorithmic feed Following Sent Private Received Create a new message Remove a message *Pending Attachments* Create Delete *Emailing Messages* Emailing Messages method *Viewing Threads*Viewing Threads method *Emailing* Emailing method *Likes* Post a like Remove a like *Topics*Get by ID Get by Hashtag *Groups* Join Leave *Users* Users in current users network About current user About a user By Alias Users in a group *Relationships* Show Add Remove *Notifications* Notifications method *Suggestions *Show Decline *Subscriptions* Check for user Check for thread Check for topic Subscribe to topic Unsubscribe to topic *Autocomplete* Autocomplete method *Invitations*Invitations method *Search * Search method *Network* Network Method Above are the methods that is going to be implemented in the yammer connector. We have taken all the methods that are supported by the current yammer API except add, update and suspend user due to its a paid user's functionality.[1] [1]https://developer.yammer.com/restapi/ http://developers.soundcloud.com/docs/api/reference Please let us know the feedback on the above. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Sivajothy Vanjikumaran *Senior Software Engineer* *Integration Technologies Team* *WSO2 Inc. http://wso2.com http://wso2.com/* *Mobile:(+94)777219209* [image: Facebook] https://www.facebook.com/vanjikumaran [image: Twitter] https://twitter.com/vanjikumaran
Re: [Architecture] ESB Connector | Yammer
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 -- Au revoir! Ramindu Deshapriya. Member - Sahana Software Foundation http://sahanafoundation.org http://rdeshapriya.com http://www.facebook.com/rdeshapriya http://twitter.com/#%21/rami_desh https://plus.google.com/113801459480978566130 http://www.linkedin.com/profile/view?id=84017607trk=tab_pro http://rdeshapriya.com http://lmakuthan.blogspot.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Au revoir! Ramindu Deshapriya. Member - Sahana Software Foundation http://sahanafoundation.org http://rdeshapriya.com http://www.facebook.com/rdeshapriya http://twitter.com/#%21/rami_desh https://plus.google.com/113801459480978566130 http://www.linkedin.com/profile/view?id=84017607trk=tab_pro http://rdeshapriya.com http://lmakuthan.blogspot.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Sivajothy Vanjikumaran *Senior Software Engineer* *Integration Technologies Team* *WSO2 Inc. http://wso2.com http://wso2.com/* *Mobile:(+94)777219209* [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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Proposed ESB connector scenario - Integrating ActiveCollab with ZohoCRM, Google Tasks, BugHerd, Freshdesk and Yammer
if only one freshdesk method needs to be developed to support this scenario its probably not worth doing this connector now itself. We can do freshdesk later if we come up with more elaborate scenarios that will use it. On Fri, Aug 15, 2014 at 5:30 PM, Rasika Hettige rasi...@gmail.com wrote: Hi, FFI, following methods will be implemented under following connectors: *ActiveCollab Connector* createClient - Adding a User to a company. createProject - Adding a new project. assignMembers - Add one or more Users to the Project and set their Project Permissions. createMilestone - Creates a new Milestone. createTask - Creates a new Task in the selected project. updateTask - Updates the properties of an existing Task. getTask - Displays the Task details. createDiscussion - Creates a new Discussion in the specified project. getDiscussion - Retrieves a particular discussion. *Freshdesk Connector* createTicket - To create a new ticket in your help desk. Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Proposed-ESB-connector-scenario-Integrating-ActiveCollab-with-ZohoCRM-Google-Tasks-BugHerd-Freshdeskr-tp101182p101483.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Proposed ESB connector scenario - Integrating ZOHO CRM with Campaign Monitor, CallRail, Twitter, Facebook, Quickbooks and JIRA
Step 6: - Create Vendors by retrieving vendors from Quickbooks. - Create Products by retrieving Items from Quickbooks. - Create Purchase Orders using the Vendors and Products in ZohoCRM and create them in Quickbooks for accounting purposes. - Associate purchase orders with relevant contacts in ZohoCRM. Advantages of integrating with Quickbooks API - QuickBooks helps to record inventory management details such as items, vendors and purchase orders in ZohoCRM. 3.4 Support Step 7: - Create cases for feedback received for products in Zoho CRM. - Track these cases as issues in JIRA and follow them up. The issue comments in JIRA can be updated in Zoho CRM. Advantages of integrating with JIRA API - Cases in ZohoCRM are used to track feedback received for products. JIRA API can be used as a product tracking tool to discuss any product related issues and track them until a solution is provided. This can be used in the support phase of the ZohoCRM by mapping the solutions to cases. Thanks Regards Rasika ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector: BaseCRM
Hi Rasika, This list looks good to go. Thanks Shevan On Thu, Jun 26, 2014 at 10:43 AM, Rasika Hettige rasi...@gmail.com wrote: Hi Shevan, Please find the final method list below: *Deals * *listDeals *- Retrieves collection of deals which belongs to a user. *setDeal*- Updates a deal. *createDeal *- Creates a new deal. *getDealNotes *- Retrieves a list of notes of a specific deal *createDealNote *- Creates a new note for a specific deal. *getDealReminders *- Retrieves a list of reminders of a specific deal. *createDealReminder *- Creates a new reminder. *Contacts* *listContacts *- Retrieves a list of contacts. Will return all account contacts if authenticated user is an admin. Otherwise will return all of authenticated user's contacts and shared contacts of other users within the account. *setContact *- Updates contact information. *createContact *- Creates a new contact. Contact can be either an individual (e.x. Mark Johnson) or an organization (e.x. Google) *getContactNotes *- Retrieves a list of notes of a specific contact *createContactNote *- Creates a new note for a specific contact *getContactReminders *- Retrieves a list of reminders of a specific contact *createConatctReminder*- Creates a new reminder. *listContactDeals* - Retrieves collection of deals which belong to a contact. *Leads* *listLeads *- Retrieves a list of leads. Will return all account leads if authenticated user is an admin. Otherwise will return all of authenticated user's leads. *setLead *- Updates lead information. *createLead *- Creates a new lead. *deleteLead *- Removes a specific lead. Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-BaseCRM-tp98354p98598.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector: BaseCRM
Hi Rasika, Can you publish the final method list pls? Thanks Shevan On Tue, Jun 24, 2014 at 10:51 AM, Rasika Hettige rasi...@gmail.com wrote: Hi Malaka, Based on our analysis following were the reasons to add methods which you have dropped. When you consider a CRM, reminders are one of the most useful task in reminding about a deal/contact. So we have included following methods. *getDealReminders *- Retrieves a list of reminders of a specific deal. *createDealReminder *- Creates a new reminder. *getContactReminders *- Retrieves a list of reminders of a specific contact. *createConatctReminder*- Creates a new reminder. And also creating note for a deal is important as deal is a sales opportunity which may frequently get associated with notes. Hence we have included following: *createDealNote * Since there is no way of retrieving a list of deals associated to a particular contact, following method is crucial. *listContactDeals* Managing deal/contact/leads are also important as they are frequently being updated in a CRM. Hence following functions were included: *setDeal*- Updates a deal. *setContact *- Updates contact information. *setLead *- Updates lead information. *deleteLead *- Removes a specific lead. (This we have considered as their existence are not permanent at a given time period.) Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-BaseCRM-tp98354p98506.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector: AmazonSES
Hi Rasika, Let's finalize this for v1.0 Thanks Shevan On Wed, Jun 25, 2014 at 10:35 AM, Rasika Hettige rasi...@gmail.com wrote: Hi Shevan, Please find the final method list below: *deleteIdentity *- Deletes the specified identity (email address or domain) from the list of verified identities. *listIdentityDkimAttributes *- Takes a list of identities as input and returns the current status of Easy DKIM signing for an entity. For domain name identities, this action also returns the DKIM tokens that are required for Easy DKIM signing, and whether Amazon_SES has successfully verified that these tokens have been published. *listIdentityNotificationAttributes *- Given a list of verified identities (email addresses and/or domains), returns a structure describing identity notification attributes. *listIdentityVerificationAttributes *- Given a list of identities (email addresses and/or domains), returns the verification status and (for domain identities) the verification token for each identity. *listIdentities *- Returns a list containing all of the identities (email addresses and domains) for a specific AWS Account, regardless of verification status. *sendEmail *- Composes an email message based on input data, and then immediately queues the message for sending. *sendRawEmail *- Sends an email message, with header and content specified by the client. The SendRawEmail action is useful for sending multipart MIME emails. The raw text of the message must comply with Internet email standards; otherwise, the message cannot be sent. *setIdentityDkimEnabled *- Enables or disables Easy DKIM signing of email sent from an identity. *setIdentityFeedbackForwardingEnabled *- Given an identity (email address or domain), enables or disables whether Amazon_SES forwards feedback notifications as email. Feedback forwarding may only be disabled when both complaint and bounce topics are set. *setIdentityNotificationTopic *- Given an identity (email address or domain), sets the AmazonSNS topic to which Amazon_SES will publish bounce and complaint notifications for emails sent with that identity as the Source. Publishing to topics may only be disabled when feedback forwarding is enabled. *getDomainDkim *- Returns a set of DKIM tokens for a domain. DKIM tokens are character strings that represent your domain's identity. *verifyDomainIdentity *- Verifies a domain. *verifyEmailIdentity *- Verifies an email address. This action causes a confirmation email message to be sent to the specified address. Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-AmazonSES-tp98318p98561.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector: AmazonSES
Hi Rasika, are these the final set of methods? If not, can you pls publish the final set? Thanks Shevan On Tue, Jun 24, 2014 at 10:55 AM, Rasika Hettige rasi...@gmail.com wrote: Hi All, To further explain on why we have selected the following methods: *listIdentityDkimAttributes/getIdentityVerificationAttributes*: these are require if we need to send secure emails because ‘listIdentityDkimAttributes’ method returns DKIM tokens that are required for Easy DKIM signing. ‘getIdentityVerificationAttributes’ is used to get the verification token. *setIdentityNotificationTopic/getIdentityNotificationAttributes*: these method helps to set Bounce/Delivery/Complaint attributes, we thought it will be use full to set bounced/delivered settings as it will help to keep track of delivered/bounced emails. *setIdentityFeedbackForwardingEnabled*: this helps to enable/disable forwarding bounce and complaint notifications as email. This is coupled with Amazon SNS and as we are doing SNS connector, we thought to select this. Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-AmazonSES-tp98318p98507.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector: BugHerd
Hi Rasika, Ok, let's proceed with the available delete operations. Thanks Shevan On Mon, Jun 23, 2014 at 12:22 PM, Rasika Hettige rasi...@gmail.com wrote: Hi Shevan The API does not provide any *delete* operations for Tasks and Comments. But we can include *deleteTaskAttachment* to delete attachments. *uploadTaksAttachment* and *createTaskAttachment* behave in a similar manner hence we have included only *uploadTaksAttachment* which supports additional functionalities. Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-BugHerd-tp98366p98464.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector: ClevertimCRM
given that this is a CRM, I would think being able to manage companies and contacts is also important. It would also help to be able to delete opportunities/tasks etc On Thu, Jun 19, 2014 at 7:45 PM, Malaka Silva mal...@wso2.com wrote: Hi, I guess following is good for v1. Any thoughts? Methods Selected: *Company* *listCompanies* *Contacts* *createContact* *listContacts* - Retrieves all contacts. *Case* *listCases* - Retrieves all Cases. *createCase* - Creates a Case. *Opportunity* *listOpportunities* - Reirieves all Opportunities. *getOpportunity* - Retrieves a specific Opportunity. *createOpportunity* - Creates an Opportunity. *updateOpportunity* - Updates an Opportunity. *Tasks* *listTasks* - Retrieves all Tasks. *createTask* - Creates a new Task. *Note* *listNotes* - Retrieves all notes. *createNote* - Adds a new note. *Comment* *listComments* - Retrieves all comments. *createComment* - Adds a new comment. Best Regards, Malaka On Thu, Jun 19, 2014 at 8:20 AM, Rasika Hettige rasi...@gmail.com wrote: *Introduction* Clevertim is an easy to learn use, web based CRM and contact manager for small businesses. *API (REST)* https://github.com/clevertim/clevertim-crm-api *ClevertimCRM Connector Summary* • Connector Name: clevertimcrm -connector-1.0.0 • Version: 1.0.0 • Technology: REST *Authentication* The API uses basic HTTP authentication with the API key as user and 'X' as password. Refer API documentation for more details. *Methods* Methods Selected: *Contacts* *listContacts* - Retrieves all contacts. *Case* *listCases* - Retrieves all Cases. *createCase* - Creates a Case. *updateCase* - Updates a Case. *Opportunity* *listOpportunities* - Retrieves all Opportunities. *createOpportunity* - Creates an Opportunity. *updateOpportunity* - Updates an Opportunity. *Tasks* *listTasks* - Retrieves all Tasks. *createTask* - Creates a new Task. *updateTask* - Updates a Task. *Note* *listNotes* - Retrieves all notes. *createNote* - Adds a new note. *updateNote* - Updates a note. *Comment* *listComments* - Retrieves all comments. *createComment* - Adds a new comment. Methods not selected: Following methods are not taken as they are more of a administrative/infrequent tasks. *createContact* *updateContact* *listCompanies* *getCompany* *createCompany* *updateCompany* *listCustomFields* *getCustomField* *createCustomField* *updateCustomField* We have also not considered following delete operations for version 1. *deleteCase* *deleteOpportunity* *deleteTask* *deleteNote* *deleteComment* *deleteContact* *deleteCompany* *deleteCustomField* The functionality of following getters can also be retrieved through their respective list operations. Hence they have not selected for version 1. *getContact* *getCase* *getOpportunity* *getTask* *getNote* *getComment* Thanks and Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-ClevertimCRM-tp98371.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 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/ 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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector: AmazonSES
Should we limit this to just the methods required to send domain key identified mail (for v1)? Not sure if attribute listing, feedback forwarding, SNS integration are useful for now. On Wed, Jun 18, 2014 at 5:22 PM, Ramindu Deshapriya rasad...@gmail.com wrote: Introduction Amazon_SES is a highly scalable and cost-effective email-sending service for businesses and developers. It eliminates the complexity and expense of building an in-house email solution or licensing, installing, and operating a third-party email service for this type of email communication. In addition, the service integrates with other AWS services, making it easy to send emails from applications being hosted on AWS. With Amazon_SES there is no long-term commitment, minimum spend or negotiation required — businesses can utilize a free usage tier, and beyond that pay only low fees for the number of emails sent plus data transfer fees. API (REST) http://docs.aws.amazon.com/ses/latest/APIReference/Welcome.html Amazon_SES Connector Summary • Connector Name: amazonses-connector-1.0.0 • Version: 1.0.0 • Technology: REST Authentication This uses the standard HTTP Authorization header to pass authentication information. Developers are issued an AWS access key ID and AWS secret access key when they register. For request authentication, the AWSAccessKeyId element identifies the access key ID that was used to compute the signature and, indirectly, the developer making the request. To generate the signature it uses Signature Version3 methodology. Methods Methods Selected: deleteIdentity - Deletes the specified identity (email address or domain) from the list of verified identities. listIdentityDkimAttributes - Takes a list of identities as input and returns the current status of Easy DKIM signing for an entity. For domain name identities, this action also returns the DKIM tokens that are required for Easy DKIM signing, and whether Amazon_SES has successfully verified that these tokens have been published. listIdentityNotificationAttributes - Given a list of verified identities (email addresses and/or domains), returns a structure describing identity notification attributes. listIdentityVerificationAttributes - Given a list of identities (email addresses and/or domains), returns the verification status and (for domain identities) the verification token for each identity. listIdentities - Returns a list containing all of the identities (email addresses and domains) for a specific AWS Account, regardless of verification status. sendEmail - Composes an email message based on input data, and then immediately queues the message for sending. sendRawEmail - Sends an email message, with header and content specified by the client. The SendRawEmail action is useful for sending multipart MIME emails. The raw text of the message must comply with Internet email standards; otherwise, the message cannot be sent. setIdentityDkimEnabled - Enables or disables Easy DKIM signing of email sent from an identity. setIdentityFeedbackForwardingEnabled - Given an identity (email address or domain), enables or disables whether Amazon_SES forwards feedback notifications as email. Feedback forwarding may only be disabled when both complaint and bounce topics are set. setIdentityNotificationTopic - Given an identity (email address or domain), sets the AmazonSNS topic to which Amazon_SES will publish bounce and complaint notifications for emails sent with that identity as the Source. Publishing to topics may only be disabled when feedback forwarding is enabled. getDomainDkim - Returns a set of DKIM tokens for a domain. DKIM tokens are character strings that represent your domain's identity. verifyDomainIdentity - Verifies a domain. verifyEmailIdentity - Verifies an email address. This action causes a confirmation email message to be sent to the specified address. Methods not selected: Following methods are deprecated, hence not considered. deleteVerifiedEmailAddress listVerifiedEmailAddresses verifyEmailAddress Following methods are nice to have functions and are not considered as important business functions. getSendQuota getSendStatistics Regards, Ramindu. -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-AmazonSES-tp98318.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector: BugHerd
can we pls include the remaining CRUD operations for tasks/comments/attachments? Currently no methods to delete a task or update/delete comments. On Thu, Jun 19, 2014 at 2:54 PM, Rasika Hettige rasi...@gmail.com wrote: *Introduction* This is one of the world's simplest bug tracking tool. It allows you to turn client feedback into actionable tasks.Team collaboration, client feedback, and task management designed for web projects. *API (REST)* http://www.bugherd.com/api_v2 *BugHerd Connector Summary* • Connector Name: bugherd-connector-1.0.0 • Version: 1.0.0 • Technology: REST *Authentication* The Api uses basic HTTP authentication with the API key as user and 'x' as password. Refer API documentation for more details. *Methods* Methods Selected: *Projects* *listProjects* - Get a list of all projects within your account. *Tasks* *listProjectTasks* - Get a full list of tasks for a project, including archived tasks. *createProjectTask* - Add a new task in a project. *updateProjectTask* - Update one of the tasks in a project. *Comments* *listTaksComments* - Get a paginated list of comments for a task. *addTaskComment* - Adds a new comment to the specified task. *Attachments* *listTaskAttachments* - Get a paginated list of attachments for a task. *uploadTaksAttachment* - Upload a new attachment and add it to the specified task. The file contents need to be specified as the POST data on this request. Methods not selected: Following methods are not taken as they are more of a administrative/infrequent tasks. *listAccountDetails* *listUsers* *listMemebers* *listGuestUsers* *listActiveProjects* *getProjectDetails* *createProject* *addMember* *addGuest* *updateProjectDetails* *deleteProject* *getProjectTask* *getAttachmentDetails* *createTaskAttachment* *uploadTaksAttachment* *deleteTaskAttachment* *Webhooks Category* Thanks and Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-BugHerd-tp98366.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:BitBucket
Hi Rasika, Let's proceed without these two methods Thanks Shevan On Mon, Jun 16, 2014 at 2:43 PM, Rasika Hettige rasi...@gmail.com wrote: Hi Shevan, We have not considered the following 2 methods because they do not cover the major functionality. *revokePullRequestByID *- Revoke your approval on a pull request. (You can remove approvals on behalf of the authenticated account) *aprovePullRequestByID *- Give your approval on a pull request. (You can only approve a request on behalf of the authenticated account.) But if you feel above two are important, we can include. Please let us know. Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-BitBucket-tp98058p98217.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:BitBucket
Should we including the following 2 methods in V1? revokePullRequestByID aprovePullRequestByID On Wed, Jun 11, 2014 at 5:49 PM, Rasika Hettige rasi...@gmail.com wrote: *Introduction* The Bitbucket REST API allows third-party application developers the means for writing applications for the Bitbucket service. Our REST API is based on open standards, you can use any web development language to access the API. Using the API, users can sign in and grant your application the right to make calls on their behalf. Then, through the API, your application can access Bitbucket resources such as an individual (or team) account, repositories, and aspects of these resources such as changesets or comments. *API* https://confluence.atlassian.com/display/BITBUCKET/Use+the+Bitbucket+REST+APIs;jsessionid=34852CBC70565AD39156EA091CE47A4D.node1 *BigBucket Connector Summary* • Connector Name: bigbucket-connector-1.0.0 • Version: 1.0.0 • Technology: REST *Authentication* To authenticate, it uses OAuth 1.0a *Methods Selected:* *Pull Requests* *listPullRequest* - Get a list of of a repository's open pull requests. *createPullRequest* - Creates a new pull request. The request URL you provide is the destination repository URL. For this reason, you must specify an explicit source repository in the request object if you want to pull from a different repository. *getPullRequest* - Gets an specific pull request. *updatePullRequest* -Updates an existing pull request. The pull request's status must be open. *mergePullRequest* - Accept a pull request and merges into the destination branch. This requires write access on the destination repository. *discardPullRequest* - Rejects a pull request. This requires write access on the destination repository. *listPullRequestComments* - Gets the array of comments on the specified pull request. *getPullRequestDiff* -Gets the diff or patch for a pull request. *Repositories* *getRepository* - Returns a single repository. *createRepository* - To create a new repository, POST directly to the desired URL, providing a JSON request body that contains the properties of the new repository. *deleteRepository* - Removes a repository. *Commits* *listCommits* - Gets the information associated with an individual commit. *listCommitComments* - Gets the array of comments on the specified pull request. *Methods Not Selected:* Methods under following categories are not selected. Branch restriction Teams Users And also following administration functionalities are not considered. getPullRequestActivityList getPullRequestActivityByID getPullRequestCommits revokePullRequestByID aprovePullRequestByID getPatchSpecification getRepositoryFolks getRepositoryWatches setApprovalOnCommit revokeApprovalOnCommit getPullRequestCommentByID - The functionality of following method can also be achieved through getPullRequestComments getCommitComments - The functionality of following method can also be achieved through listCommitComments Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-BitBucket-tp98058.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:Skype
yes, this was taken out of scope. Jarachanthan selected another On Thu, Jun 12, 2014 at 9:25 PM, Dushan Abeyruwan dus...@wso2.com wrote: Hi I am having the same concern, as what Malaka has, I don't think this has a proper use case to go with ESB On Thu, Jun 12, 2014 at 6:00 PM, Malaka Silva mal...@wso2.com wrote: Hi Jarachanthan, I think skype only provides an api just to connect to client running on a device. This connector does not provide any useful use case for an ESB. I guess there are better options for you like hubspot. http://developers.hubspot.com/docs/endpoints Best Regards, Malaka On Thu, Jun 12, 2014 at 4:22 AM, Jarachanthan Ratnakumar ratmin...@hotmail.com wrote: Hi all, To create an Skype connector for ESB, there is no comfortable API for that [1]. But there is Skype URI API [2]. Currently supporting - switch focus to client. - initiate video - audio call - instant messaging These can be done only when the Skype is already installed. So, how can I get a solution on creating a Skype connector? [1] http://www.infoworld.com/t/application-development/ microsoft-kills-skype-third-party-tools-the-desktop-230101 http://www.infoworld.com/t/application-development/microsoft-kills-skype-third-party-tools-the-desktop-230101%29.But [2] https://developer.skype.com/skype-uris Thank you R.Jarachanthan ___ 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/ 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 -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:AmazonDynamoDB
This list seems good to go for v1 On Wed, Jun 11, 2014 at 10:33 AM, Rasika Hettige rasi...@gmail.com wrote: Hi Malaka, We have not considered the DDL functionalities (Administration functionalities) in first version as they do not have a significant business value. Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-AmazonDynamoDB-tp97980p98027.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:Basecamp
attachables (Uploads, Messages, or Comments) with a 200 OK response Uploads createUploads -create a new entry in the Files section on the given project, with the given attachment token. Attaching files requires both the token and the name of the attachment createUpload - show the content, comments, and attachments for this upload Calendar Events: listCalendarEvents - return upcoming/past calendar events for the project/calendar depending on the endpoint getCalendarEvent - return the specified calendar event createCalendarEvent - create a new calendar event for a project updateCalendarEvent - update the specific calendar event on a project deleteCalendarEvent - delete the calendar event specified and return 204 No Content if that was successful Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-Basecamp-tp98063.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 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/ 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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:Magento
/mailman/listinfo/architecture -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:Magento
ok, thanks On Fri, Jun 13, 2014 at 9:34 AM, Ramindu Deshapriya rasad...@gmail.com wrote: Hi Shevan, Shevan Goonetilleke wrote Do the following also fall into the 'back-office' category? If so we can leave them out for now. *Catalog Product Tier Price* *getCatalogProductTierPriceInfo* - Retrieve information about product tier prices *updateCatalogProductTierPrice *- Update the product tier prices We'd need tier price info to assign discounts on purchases. Shevan Goonetilleke wrote *Catalog Inventory* *listStockData *- Retrieve the list of stock data by product IDs *updateStockData*- Update the stock data for a list of products You'd need listStockData to figure out whether stock is available when making a sale. updateStockData is needed to update the amount available in stock after a sale is confirmed. Thanks. -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-Magento-tp97825p98125.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:AmazonSNS
Thanks for the confirmation. Let's go with the selected list. On Wed, Jun 4, 2014 at 1:13 PM, Rasika Hettige rasi...@gmail.com wrote: Hi Shevan, Platform Applications come into play in the context of using SNS to send push notifications to devices that subscribe, which enables the ability to send notification messages directly to apps on mobile devices. Supported Push Notification services by AWS SNS are : 1. Apple Push Notification Service (APNS) 2. Google Cloud Messaging for Android (GCM) 3. Amazon Device Messaging (ADM) A PlatformApplication object would be created for one of the supported push notification services, to which the devices, apps register. Configurations such as follows need to be set for it. 1. PlatformCredential - The credential received from the notification service. For APNS/APNS_SANDBOX, PlatformCredential is private key. For GCM, PlatformCredential is API key. For ADM, PlatformCredential is client secret. 2. PlatformPrincipal - The principal received from the notification service. For APNS/APNS_SANDBOX, PlatformPrincipal is SSL certificate. For GCM, PlatformPrincipal is not applicable. For ADM, PlatformPrincipal is client id. 3. EventEndpointCreated - Topic ARN to which EndpointCreated event notifications should be sent. 4. EventEndpointDeleted - Topic ARN to which EndpointDeleted event notifications should be sent. 5. EventEndpointUpdated - Topic ARN to which EndpointUpdate event notifications should be sent. 6. EventDeliveryFailure - Topic ARN to which DeliveryFailure event notifications should be sent upon Direct Publish delivery failure (permanent) to one of the application's endpoints. More Information can be referred from [1]. Related methods have been de-prioritized on the basis that these parameters are more like one time configuration data. listPlatformApplications should also return one or more of the above 3 (APNS, GCM, ADM) [1] http://docs.aws.amazon.com/sns/latest/dg/SNSMobilePush.html http://docs.aws.amazon.com/sns/latest/dg/SNSMobilePush.html Please let us know, any concerns on this? -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-AmazonSNS-tp97747p97830.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:GooglePrediction
Let's go with this method list for v1 On Tue, Jun 3, 2014 at 11:06 AM, Rasika Hettige rasi...@gmail.com wrote: Hi Seshika, As per the Google prediction documentation [1], you can train the models using regression model (if the answer column is numeric) or categorical model (if the answer column is string). [1] https://developers.google.com/prediction/docs/developer-guide Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-GooglePrediction-tp97528p97699.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:AmazonSQS
can we delete a single message using the *deleteMessageBatch method? On Mon, Jun 2, 2014 at 6:56 PM, Rasika Hettige rasi...@gmail.com wrote: *Introduction* Amazon Simple Queue Service (Amazon SQS) is a messaging queue service that handles message or workflows between other components in a system *API (REST)* http://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/Welcome.html *AmazonSQS Connector Summary* • Connector Name: amazonsqs-connector-1.0.0 • Version: 1.0.0 • Technology: REST *Authentication* This uses the standard HTTP Authorization header to pass authentication information. Developers are issued an AWS access key ID and AWS secret access key when they register. For request authentication, the AWSAccessKeyId element identifies the access key ID that was used to compute the signature and, indirectly, the developer making the request. *Methods Selected* Following methods are selected for the first version of this connector. *Permission* addPermission - Adds a permission to a queue for a specific principal. This allows for sharing access to the queue. removePermission - Revokes any permissions in the queue policy. *Queue* createQueue - Creates a new queue, or returns the URL of an existing one. getQueueAttributes - Gets attributes for the specified queue. setQueueAttributes - Sets the value of one or more queue attributes. listQueues - Returns a list of your queues. deleteQueue - Deletes the queue specified by the queue URL, regardless of whether the queue is empty. *Message* SendMessageBatch - Delivers a message to the specified queue. receiveMessage - Retrieves one or more messages from the specified queue. deleteMessageBatch - Deletes multiple messages. *Methods not selected* Following methods have not been considered for first version. *getQueueUrl *- Returns the URL of an existing queue. Queues can also be retrieved using *listQueues *method and hence this is not considered. *listDeadLetterSourceQueues *- Returns a list of your queues that have the RedrivePolicy queue attribute configured with a dead letter queue. The results of this method can also be retrieved through *getQueueAttributes *method. Hence this is not considered. *sendMessage *- Delivers a message to the specified queue. This functionality can be achieved through sendMessageBatch method. Hence this method is not selected. *changeMessageVisibility* / *changeMessageVisibilityBatch *- Changes the visibility timeout of message(s) in a queue to a new value. Since these methods are at configuration level, we have not considered. *deleteMessage *- Deletes the specified message from the specified queue. The same functionality can be achieved *deleteMessageBatch *method. Hence we have not considered this for the first version. Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-AmazonSQS-tp97657.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:Log-gly
Hi Malaka, any further comments on the method names? Can we close this out now? Thanks Shevan On Mon, Jun 2, 2014 at 12:17 PM, Rasika Hettige rasi...@gmail.com wrote: Hi Malaka, Tracking Pixel - This is used to track the page visit/count automatically and when enabled the search will be easy. But this is not an API call. So we have not considered this as a method. Following are the sections available with the method names which we are proposing on each. *API: Sending Data* Bulk Endpoint – sendBulkLogs File Upload - uploadLogFile *API: Retrieving Data* Search Endpoint - createSearchQuery Events Endpoint - getSearchedEvents Field Search - getSearchFields *API: Account Info* Account Info - getAccountInfo Please let us know your thoughts, if you feel these method names are not clear enough to what the API requires. Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-Log-gly-tp97526p97612.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:AmazonSNS
What exactly is a Platform Application in this context? Is it worth adding listPlatformApplications? On Tue, Jun 3, 2014 at 5:50 PM, Rasika Hettige rasi...@gmail.com wrote: *Introduction* Amazon Simple Notification Service (Amazon SNS) is a web service that enables you to build distributed web-enabled applications. Applications can use Amazon SNS to easily push real-time notification messages to interested subscribers over multiple delivery protocols. (Document was last updated on 3rd June, 2014) *API (REST)* http://docs.aws.amazon.com/sns/latest/APIReference/API_Operations.html *AmazonSNS Connector Summary* • Connector Name: amazonsns-connector-1.0.0 • Version: 1.0.0 • Technology: REST *Authentication* This uses the standard HTTP Authorization header to pass authentication information. Developers are issued an AWS access key ID and AWS secret access key when they register. For request authentication, the AWSAccessKeyId element identifies the access key ID that was used to compute the signature and, indirectly, the developer making the request. *Methods Selected:* *Endpoint* *createEndpoint* - Creates an endpoint for a device and mobile app on one of the supported push notification services, such as GCM and APNS. *deleteEndpoint* - Deletes the endpoint from Amazon SNS. This action is idempotent. *listEndpoints* - Lists the endpoints and endpoint attributes for devices in a supported push notification service. *subscribe* - Prepares to subscribe an endpoint by sending the endpoint a confirmation message. *unsubscribe* - Deletes a subscription. *confirmSubscription* - Verifies an endpoint owner's intent to receive messages by validating the token sent to the endpoint by an earlier Subscribe action *listSubscriptions* - Returns a list of the requester's subscriptions. Each call returns a limited list of subscriptions, up to 100. *listSubscriptionsByTopic* - Returns a list of the subscriptions to a specific topic. Each call returns a limited list of subscriptions, up to 100. *Topic* *createTopic* - Creates a topic to which notifications can be published. Users can create at most 3000 topics. *deleteTopic* - Deletes a topic and all its subscriptions. Deleting a topic might prevent some messages previously sent to the topic frombeing delivered to subscribers. *listTopics* - Returns a list of the requester's topics. Each call returns a limited list of topics, up to 100. *publish* - Sends a message to all of a topic's subscribed endpoints. *Methods not selected:* The following methods handle configuration level data, hence we have not considered. *addPermission removePermission createPlatformApplication deletePlatformApplication listPlatformApplications* Following setters and getters are deprioritized from initial release since these can be initially set when creating operation. And similarly they can be retrieved from respective list operations. *getPlatformApplicationAttributes setEndpointAttributes setEndpointAttributes getSubscriptionAttributes setSubscriptionAttributes setTopicAttributes getTopicAttributes* Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-AmazonSNS-tp97747.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:NetSuite
Can you please list out the methods that were not selected (don't have access to the API documentation). Thanks Shevan On Wed, May 28, 2014 at 6:38 PM, Rasika Hettige rasi...@gmail.com wrote: *Introduction* SuiteTalk exposes NetSuite as a data source for programmatic access, hence most of the data operations developers expect, such as insert, update, delete, and select/search are supported. There are also a number of operations that are available as supporting operations for data read/write operations. *API (SOAP)* https://system.na1.netsuite.com/app/help/helpcenter.nl?topic=CARD_-29 *Netsuite Connector Summary* • Connector Name: netsuiteconnector-1.0.0 • Version: 1.0.0 • Technology: SOAP *Authentication* Use Request Level Credentials which are sent in SOAP header while maintaining https proxy. *Methods* *addList *- Use to add one or more records into the system. The system returns a NetSuite identifier (internalId) that is unique for each record created within a record type. *attach *- Use to attach another record or file to/from another record *detach *- Use to detach another record or file to/from another record *deleteList *- Use to delete one or more records in the system. The records to be deleted are identified by either the internal or external ID and the record type. *getList *- Use to query the system for one or more records. You must provide either the internal or external ID and the record type for each query item. *getAll *- Use to return a list of records that do not have a search interface. *getBudgetExchangeRate*- Use to get and filter all data related to the Budget Exchange Rates table. *getCurrencyRate *- Use to get currency exchange rates from the Currency Exchange Rate table. *getConsolidatedExchangeRate* - Use to get and filter all data related to the Consolidated Exchange Rates table. *getItemAvailability *- Use to retrieve the inventory availability for a given list of items. *getPostingTransactionSummary *- Use to retrieve a summary of the actual data in an account. *searchMoreWithId *- Used to retrieve more records after an initial search operation is invoked. *updateList *- Use to update one or more existing records in the system by providing new values for the fields to be updated for each record. The records to be updated are identified by either the internal or external ID and the record type. *getDataCenterUrls *- Use for dynamic discovery of data-center-specific URLs for partner applications' access to NetSuite. Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-NetSuite-tp97380.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:Gooddata
Is there a use-case to do createLogin via an API call to this platform? Also, aren't these also more config related? listProcesses - List Processes in a project. createProcessWithMultipart - Create new data loading process with one single multipart http request. listProcessExecution - List Processes of the given User in all Projects. executeProcess - Execute a Process. On Tue, May 27, 2014 at 11:21 AM, Rasika Hettige rasi...@gmail.com wrote: Hi Malaka/Dushan, For this connector we have considered the methods which are essential to fulfill the basic functionality of Gooddata. Please see the reasons for not selecting the below categories. *Projects/User/Dashboard* These categories contain the master data which is at the configuration level. Therefore we have not taken the methods of these categories. *Project Model* This category has only 2 GET methods and there is no way of creating the model. Hence we have not considered. *Generate MAQL DDL to update project* This category just gives you a Diff between the two model states - operations that should be applied to current project model to make it equal to the submitted targetModel. Hence we have considered this as not essential. *Notifications* Notifications allow users to be informed about some specific events in the Project. Notifications are based on Channel Configuration, where user specifies what is the channel, where he wants to send the notification. Hence we have not considered. *Metadata/Mandatory User Filters (MUFs)/Dependency/Object Identifiers/Reports and Dashboards by email/Schedules/White Labeling/Data Storage Service * We have considered the methods under these categories as not essential to represent in the first version as most are at the configuration level. But if you think we should include all of these, please let us know. Thanks Regards Rasika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-Gooddata-tp97207p97312.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 -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] YouTube ESB Connector
Jason, we don't need to support all available functions. Let's define a set of use cases that we think are a must have for a first version and implement them. We can always do a V2 later based on user response/feedback. On Mon, Apr 21, 2014 at 5:54 PM, Jason Catlin ja...@wso2.com wrote: Hey guys, So I was a bit mistaken before when I said this was a small API, cause I was looking at the Youtube ANALYTICS api, which only has one function that returns a report about usage. The actual mainline Youtube api is HUGE, with all these functions for manipulating playlists and subscriptions and channels and everything else. So Malaka is right that this could take long, especially if I'm going to take an actual Youtube account and test every one of these functions. Now that's fine, I don't mind doing a big api, but this could take a while. I'm just about done coding the very first version of the connector, which just has the minimum functionality for each part. I'll keep you guys posted about what happens next. jc On Fri, Apr 18, 2014 at 10:05 PM, Nuwan Bandara nu...@wso2.com wrote: Hi Jason, Hows the connector dev work progressing ? Regards, /Nuwan On Thu, Apr 10, 2014 at 4:33 AM, Jason Catlin ja...@wso2.com wrote: Hey guys, As you know, the ESB has the ability to use connector plugins so that you can easily make calls to common services without having to re-implement the details. We want a rich library of these, and I'll be contributing a few. I'll be starting with a youtube connector, something relativley simple, and then doing more complicated ones later. So I looked through all the connectors already implemented and determined that the twitter connector is probably the most similar to what I'll be doing. The authentication is very similar, and then both just have a few simple queries made through REST interfaces. A few points of interest: Even though the ESB Connector system has a way to specify REST connectors, the twitter connector doesn't use this, and rather uses a Java coded one instead. Does anyone know what the reason for this is? Also, I noticed that the twitter connector forms an OAuth token inside the Java code, and it gets its authentication details from properties that it reads form the configuration of the connector. This is one way to do it. Another way, which might make more sense to me, is for the connector to ignore the OAuth all together, and have the user add that header outside the connector. This might give them much more control over it. Does anyone know why they set up the twitter connector that way? In general, I think this will probably be a pretty open and shut project. I'd be suprised if it takes more than a week. JC -- Thanks Regards, Nuwan Bandara | Senior Technical Lead - Solutions Architecture, WSO2 Inc. +1 812.606.7390 | +1 650.745.4499 Ext 4210 | http://nuwanbando.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Proposed code repository restructuring move to GitHub
Harshana have already started working on a PoC. Thoughts welcome. Those who were in these discussions, please add anything I may have missed. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/* *email: **az...@wso2.com* az...@wso2.com * cell: +94 77 3320919 %2B94%2077%203320919 blog: * *http://blog.afkham.org* http://blog.afkham.org *twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* *Lean . Enterprise . Middleware* ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/* *email: **az...@wso2.com* az...@wso2.com * cell: +94 77 3320919 %2B94%2077%203320919 blog: * *http://blog.afkham.org* http://blog.afkham.org *twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* *Lean . Enterprise . Middleware* -- *Senaka Fernando* Senior Technical Lead; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org http://apache.orgE-mail: senaka AT wso2.com http://wso2.com**P: +1 408 754 7388 %2B1%20408%20754%207388; ext: 51736*; *M: +94 77 322 1818 %2B94%2077%20322%201818 Linked-In: http://linkedin.com/in/senakafernando http://linkedin.com/in/senakafernando* Lean . Enterprise . Middleware -- Sameera Jayasoma, Architect, WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://sameera.adahas.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware -- S.Uthaiyashankar VP Engineering WSO2 Inc. http://wso2.com/ - lean . enterprise . middleware Phone: +94 714897591 -- Sameera Jayasoma, Architect, WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://sameera.adahas.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/* *email: **az...@wso2.com* az...@wso2.com * cell: +94 77 3320919 %2B94%2077%203320919 blog: * *http://blog.afkham.org* http://blog.afkham.org *twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* *Lean . Enterprise . Middleware* -- *[image: http://wso2.com] http://wso2.com Senaka Fernando* Senior Technical Lead; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org http://apache.orgE-mail: senaka AT wso2.com http://wso2.com**P: +1 408 754 7388 %2B1%20408%20754%207388; ext: 51736*; *M: +94 77 322 1818 %2B94%2077%20322%201818 Linked-In: http://linkedin.com/in/senakafernando http://linkedin.com/in/senakafernando*Lean . Enterprise . Middleware -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
