[Architecture] Making BAM Activity Monitoring a generic feature
Current implementation of BAM Activity Monitoring is based on a the activity ID field and sorting the timestamps. It has some limitations. 1. Only one activity monitoring scenario is possible per tenant 2. Activity ID the the hard coded parameter used for correlating among events 3. Ordering mechanism is based only on sorting operation of timestamp field 4. Tightly bound with Cassandra custom indexes With the introduction of custom data stores in BAM we should support activity monitoring for RDBMS indexes. There we can use SQL queries as tasks for updating indexes. This enables us to use multiple activity monitoring scenarios per each stream. For example all session ID, transaction ID and username can be considered as activities for different monitoring requirements at the same time. With the toolbox deployment we can define all the activity monitoring scenarios so that indexes are created for each field. And also we can make it possible to configure the sorting mechanism per each activity. The user can be able to select whatever field like timestamp or hop_number as the sorting field. This would enable user to introduce their own field to order the activity results. WDYT? *Maninda Edirisooriya* Senior Software Engineer *WSO2, Inc.*lean.enterprise.middleware. *Blog* : http://maninda.blogspot.com/ *E-mail* : mani...@wso2.com *Skype* : @manindae *Twitter* : @maninda ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Fwd: Stripe Web Connector for WSO2 ESB
Hi all, Please find the requested use case for Stripe ESB connector below. Use Case for Stripe ESB connector https://docs.google.com/a/wso2.com/document/d/1qZqNicpoxGir3PcjUslgKk3lNQsGI_qn9gauipoKAJQ/edit?usp=drive_web Thanks regards, On Mon, Nov 24, 2014 at 10:20 PM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Need usecase please. On Monday, November 24, 2014, Keerthika Mahendralingam keerth...@wso2.com wrote: Ok noted. I will create the milestone plan accordingly. On Mon, Nov 24, 2014 at 1:52 PM, Shevan Goonetilleke she...@wso2.com wrote: Keerthika, there are a lot of methods here too...pls define the some useful scenarios around this and implement only those methods (given that you have only 3 weeks to complete). On Mon, Nov 24, 2014 at 12:54 PM, Keerthika Mahendralingam keerth...@wso2.com wrote: I will share the milestone plan by today evening. On Mon, Nov 24, 2014 at 12:53 PM, Samisa Abeysinghe sam...@wso2.com wrote: Milestone plan for this? Thanks, Samisa... Samisa Abeysinghe Vice President Delivery WSO2 Inc. http://wso2.com On Mon, Nov 24, 2014 at 12:49 PM, Keerthika Mahendralingam keerth...@wso2.com wrote: Hi all, I have planned to develop $subject as described below. *Introduction* Stripe provides simple RESTful HTTP interfaces to handle payments. *Stripe API Methods* 1. Cards: Creates a new card for a customer. Retrieves an existing card details stored on a customer. Updates a card details. Deletes a card. Lists all cards belonging to a customer. 2. Tokens: Creates a card token that wraps the details of a credit card. Creates a bank account token that wraps the details of a bank account. Retrieves an existing token. 3. Customers: Creates a new customer. Retrieves the details of an existing customer. Updates the specified customer. Permanently deletes a customer. Returns a list of all customers. 4. Charges: Creates a new charge. Retrieves the details of an existing charge. Updates the specified charge. Captures the payment of an existing charge. returns a list of all charges. 5. Refunds: Creates a new refund for a charge. Retrieves details about an existing refund. Updates the specified refund. Returns a list all refunds belonging to a specific charge. 6. Subscriptions: Creates a new subscription on an existing customer. Retrieves details about a specific active subscription for a customer. Updates an existing subscription on a customer. Cancels a customer's subscription. Lists active subscriptions. 7.Plans: Creates a plan. Retrieves a plan with the given ID. Updates the name a plan. Deletes a plan. Lists all plans. 8. Coupons: Creates a coupon. Retrieves a coupon with the given ID. Updates the metadata of a coupon. Deletes a coupon. Returns a list of coupons. 9. Discounts: Removes the currently applied discount on a customer. Removes the currently applied discount on a subscription. 10. Invoices: Creates an invoice. Retrieves the invoice with the give ID. Retrieves an invoice’s line items. Retrieves a customer’s upcoming invoice for a customer. Updates an existing invoice. Pays an invoice. Lists invoices for a specific customer. 11. Invoice items: Adds an arbitrary charge to the customer's upcoming invoice. Retrieves an invoice item with the given ID. Updates the amount or description of an upcoming invoice. Deletes an invoice item from the upcoming invoice. Lists all invoice items. 12.Transfers: Creates a new transfer. Retrieves the details of an existing transfer. Updates the specified transfer. Cancels a transfer. Lists all existing transfers. 13. Disputes: Updates a dispute. Closes a dispute for a charge. 14. Recipients: Creates a new recipient and verifies recipient's identity and bank account information or credit card. Retrieves the details of an existing recipient. Updates the specified recipient. Deletes a recipient. Lists all recipients. 15. Account: Retrieves the details of an account details. 16. Balance: Retrieves the current account balance. Retrieves the balance transection with the given ID. Returns a list of transections that have contributed to the Stripe account balance. 17. Application Fees: Retrieves the details of an application fee. Returns a list of application fees. 18. Application fee refunds: Refunds an application fee that has
Re: [Architecture] ESB Connector for ZOHO Invoice
Here I'm attaching the usecases for Zoho Invoice-ESB Connector ZOHO Invoice-ESB connectors https://docs.google.com/a/wso2.com/document/d/1hHvRe1trjr6OUAb8x4nBlQh-G_VMkhE3Xi2aPWk_4bA/edit?usp=drive_web Thanks, Regards, Ashalya. On Mon, Nov 24, 2014 at 10:19 PM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Can you propose the usecase please On Monday, November 24, 2014, Sriashalya Srivathsan asha...@wso2.com wrote: ok ,noted,I'll consider the main methods only,Thank you. On Mon, Nov 24, 2014 at 1:43 PM, Shevan Goonetilleke she...@wso2.com wrote: 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 -- 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] ESB Connector for Nest API
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
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
[Architecture] Machine Processable Metadata and GUI Generation
Here is the link to the technology called OSCL I was mentioning: http://open-services.net/resources/tutorials/oslc-primer/what-is-oslc/ Best regards, Frank ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] ESB Connector for Nest API
Hi, Please find the usecase for Nest ESB connector here. On Tue, Nov 25, 2014 at 4:20 PM, Shevan Goonetilleke she...@wso2.com wrote: 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 -- Shakila Sivagnanarajah Associate Software Engineer Mobile :+94 (0) 770 760240 shak...@wso2.com Usecase.pdf Description: Adobe PDF document ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] Message Deletion For Topics - MB 3.0.0
Hi, There is an identified concern on the $Subject. We are saving topic messages to durable store to share the messages across the nodes and prevent OOM. Consider following scenario 1. Sub1 subscribes to topic1 on MB1 node 2. Sub2 subscribes to topic1 on MB1 node 3. Sub3 subscribes to topic1 on MB1 node Sub1 closes. We cannot delete messages as messages are shared by all subscribers for topic1 (Sub2 and Sub3 are still alive) Now Sub4 subscribes to topic1 on MB1 node It will get above mentioned messages which we did not delete (we just send message to all relevant subs on the node). But as per topic behavior this should not happen. What would be possible solutions for this? In MB 2.2.0, we did not get this problem as messages were fire-and-forget (without considering acks, but in MB 3.0.0 we consider acks for topic messages). What would be the possible solutions? 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
Re: [Architecture] [Fast Track Training Project] ESB Connector for Teamwork
Hi, Please find the use case for Teamwork ESB connector below. Usecase for teamwork ESB Connector https://docs.google.com/a/wso2.com/document/d/1C5LhQ5bdkMfcfSDA_AeDtu8sKvAwd04c69_vhi1JFC8/edit?usp=drive_web Regards, Kesavan Yogarajah Associate Software Engineer WSO2 Inc. Mob: +94 779758021 On Tue, Nov 25, 2014 at 6:30 AM, Samisa Abeysinghe sam...@wso2.com wrote: Milestone plan looks good. Thanks, Samisa... Samisa Abeysinghe Vice President Delivery WSO2 Inc. http://wso2.com On Mon, Nov 24, 2014 at 4:46 PM, Kesavan Yogarajah kesav...@wso2.com wrote: Hi Samisa, I have selected the $subject as my fast track training project. Herewith I have attached my milestone plan for your kind review. Milestone Plan - Teamwork Connector https://docs.google.com/a/wso2.com/spreadsheets/d/1kCmrrzZ3GqKpURvuv2pskGC-j6v9Cq60WD4jFj8dRmw/edit?usp=drive_web Regards, Kesavan Yogarajah Associate Software Engineer WSO2 Inc. Mob: +94 779758021 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] YouTube Connector for WSO2 ESB
Hi All I have attached usecase for YouTube ESB connector here. Use Case for YouTub ESB connector https://docs.google.com/a/wso2.com/document/d/1W_IjNXwMQCXx8SbOIsiHYJRpGX7adQCv4xjLbjQT6m8/edit?usp=drive_web Regards, -- *Naasheer Ali* | Associate Software Engineer WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka Email: naashe...@wso2.com On Mon, Nov 24, 2014 at 10:12 PM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: What is the usecase here? Why anyone would want to use this connector in an ESB configuration? On Monday, November 24, 2014, Naasheer Ali naashe...@wso2.com wrote: Hi All, I've planed to develop $subject. *Introduction* YouTube is a video-sharing website. The site allows users to upload, view, and share videos. *YouTube API Methods**Activities* - *ChannelBanners* - *Channels* - *ChannelSections* - *GuideCategories* - *i18nLanguages* - *i18nRegions* - *PlaylistItems* - *Playlists* - *Search* - *Subscriptions* - *Thumbnails* - *VideoCategories* - *Videos* - *Watermarks* - *Channel Reports* Link to YouTube API : http://api-portal.anypoint.mulesoft.com/youtube/api/youtube-data-api-v30/docs/reference Regards, -- *Naasheer Ali* | Associate Software Engineer WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka Email: naashe...@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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Making BAM Activity Monitoring a generic feature
Hi Maninda, On Tue, Nov 25, 2014 at 2:48 PM, Maninda Edirisooriya mani...@wso2.com wrote: Current implementation of BAM Activity Monitoring is based on a the activity ID field and sorting the timestamps. It has some limitations. 1. Only one activity monitoring scenario is possible per tenant Can you elaborate more on this. Do you mean that one activity can have events from different tenants? 2. Activity ID the the hard coded parameter used for correlating among events 3. Ordering mechanism is based only on sorting operation of timestamp field 4. Tightly bound with Cassandra custom indexes Yes. We have above known limitations in the current architecture basically because indexing and searching is implemented based on Cassandra custom index CFs which doesn't support advance sorting/searching and grouping operations. With the introduction of custom data stores in BAM we should support activity monitoring for RDBMS indexes. There we can use SQL queries as tasks for updating indexes. This enables us to use multiple activity monitoring scenarios per each stream. For example all session ID, transaction ID and username can be considered as activities for different monitoring requirements at the same time. With the toolbox deployment we can define all the activity monitoring scenarios so that indexes are created for each field. And also we can make it possible to configure the sorting mechanism per each activity. The user can be able to select whatever field like timestamp or hop_number as the sorting field. This would enable user to introduce their own field to order the activity results. WDYT? Multiple activity monitoring scenarios per each stream is already supported in current implementation. Sorting and pagination are the missing pieces which we have design properly in our next major release. And we should also make the activity correlation field configurable via the toolbox. *Maninda Edirisooriya* Senior Software Engineer *WSO2, Inc.*lean.enterprise.middleware. *Blog* : http://maninda.blogspot.com/ *E-mail* : mani...@wso2.com *Skype* : @manindae *Twitter* : @maninda -- Regards, Inosh Goonewardena Associate Technical Lead- WSO2 Inc. Mobile: +94779966317 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Message Deletion For Topics - MB 3.0.0
Hi HasithaH, According to a little reading i did with the amqp spec regarding topic behavior (refer mail Behavior of non-durable AMQP topics in MB 3.0.0) ; - We have control over how to implement message queues (stored queues) for an exchange. So, the decision to have one storage queue for multiple subscribers on the same node for a single non-durable topic is ours to make. - Temporary exchanges last until the server shuts-down. Lifecycle of a non-durable topic ends only in a server shut-down. (Subscribers can come and go) - Temporary message queues last until the server shuts-down. Lifecycle of a temporary message queue (like the one we use here) should therefore clear when the server shuts down. Given above findings, spec-wise, it is okay for a new non-durable topic subscriber to receive past messages of the topic. (valid for the current server session). If consumers expect a subscriber to receive only new messages, I feel that they should use durable topics. Correct me if I'm wrong :) --- There is also a solution (one approach), as we discussed, to use the subscriber-subscribed-timestamp against message-arrival-time to block messages coming from the past for that subscriber. (This could be done in evaluateDeliveryRules method ? ) WDYT ? Btw theres a jira related to this : https://wso2.org/jira/browse/MB-863 :) Thanks On Tue, Nov 25, 2014 at 6:11 PM, Hasitha Hiranya hasit...@wso2.com wrote: Hi, There is an identified concern on the $Subject. We are saving topic messages to durable store to share the messages across the nodes and prevent OOM. Consider following scenario 1. Sub1 subscribes to topic1 on MB1 node 2. Sub2 subscribes to topic1 on MB1 node 3. Sub3 subscribes to topic1 on MB1 node Sub1 closes. We cannot delete messages as messages are shared by all subscribers for topic1 (Sub2 and Sub3 are still alive) Now Sub4 subscribes to topic1 on MB1 node It will get above mentioned messages which we did not delete (we just send message to all relevant subs on the node). But as per topic behavior this should not happen. What would be possible solutions for this? In MB 2.2.0, we did not get this problem as messages were fire-and-forget (without considering acks, but in MB 3.0.0 we consider acks for topic messages). What would be the possible solutions? 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 -- Cheers, Hasitha Amal De Silva Software Engineer Mobile : 0772037426 Blog: http://devnutshell.tumblr.com/ WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. ) ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Making BAM Activity Monitoring a generic feature
On Tue, Nov 25, 2014 at 7:03 PM, Inosh Goonewardena in...@wso2.com wrote: Hi Maninda, On Tue, Nov 25, 2014 at 2:48 PM, Maninda Edirisooriya mani...@wso2.com wrote: Current implementation of BAM Activity Monitoring is based on a the activity ID field and sorting the timestamps. It has some limitations. 1. Only one activity monitoring scenario is possible per tenant Can you elaborate more on this. Do you mean that one activity can have events from different tenants? No. I mean activity monitoring should be possible with different correlation fields other than hard coded activityID field per tenant. 2. Activity ID the the hard coded parameter used for correlating among events 3. Ordering mechanism is based only on sorting operation of timestamp field 4. Tightly bound with Cassandra custom indexes Yes. We have above known limitations in the current architecture basically because indexing and searching is implemented based on Cassandra custom index CFs which doesn't support advance sorting/searching and grouping operations. With the introduction of custom data stores in BAM we should support activity monitoring for RDBMS indexes. There we can use SQL queries as tasks for updating indexes. This enables us to use multiple activity monitoring scenarios per each stream. For example all session ID, transaction ID and username can be considered as activities for different monitoring requirements at the same time. With the toolbox deployment we can define all the activity monitoring scenarios so that indexes are created for each field. And also we can make it possible to configure the sorting mechanism per each activity. The user can be able to select whatever field like timestamp or hop_number as the sorting field. This would enable user to introduce their own field to order the activity results. WDYT? Multiple activity monitoring scenarios per each stream is already supported in current implementation. Sorting and pagination are the missing pieces which we have design properly in our next major release. And we should also make the activity correlation field configurable via the toolbox. We should have a way to specify different fields for monitoring different activities and see them in the Activity Monitoring dashboard. For example if you want to monitor the flow of session IDs among streams and suppose at the same time you want to see the transaction ID flow between ESB mediation flows. You need two correlation ID fields and two indexes and should be able to see each scenario separately in the activity dashboard. There the session ID may be sorted with the timestamp but transaction flow should be sorted based on a constant field set by the BAM mediator, mediator_number. The later one can be used in many situations where the message flow time difference between the two interception points is lesser than a 1 millisecond. (for e.g. in the same sequence where no significant operations are done to the message) *Maninda Edirisooriya* Senior Software Engineer *WSO2, Inc.*lean.enterprise.middleware. *Blog* : http://maninda.blogspot.com/ *E-mail* : mani...@wso2.com *Skype* : @manindae *Twitter* : @maninda -- Regards, Inosh Goonewardena Associate Technical Lead- WSO2 Inc. Mobile: +94779966317 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] [G-Reg-5.0.0] Service UI/Store
Hi Senaka, Thanks for the response. Yes. It makes sense to display it in one tab rather than in two, as those are dependant, and the consumer can look into the details of the service in one place. After further discussion with the team, if this fits good in a consumer point of view, I'll proceed with this way. Shazni Nazeer Senior Software Engineer Mob : +94 37331 LinkedIn : http://lk.linkedin.com/in/shazninazeer Blog : http://shazninazeer.blogspot.com On Tue, Nov 25, 2014 at 3:29 PM, Senaka Fernando sen...@wso2.com wrote: Hi Shazni, Has to be dependent. And also needs to sync with this new Metadata model that we are talking about. Thanks, Senaka. On Tue, Nov 25, 2014 at 4:36 AM, Shazni Nazeer sha...@wso2.com wrote: Hi All, In the extension that I was working I now have made the necessary changes to the publisher end so that we could add services and wsdl from the publisher and view those in a list. When clicked on the relevant service or wsdl it shows up an overview page with details. The wsdl we add through the publisher also creates the relevant service. The service support 'ServiceLifecycle' by default, which is not the case with the publisher end in ES feature, which attaches the store life cycle. We are yet to finalize the life-cycle to be associated and how to proceed with that. Going on to the the store end, how would it be best viewed? Should we be having two different tabs for service and wsdl? Or will it be concise showing the wsdl in the service view it self as both are dependant? I'm planning to work on the store end and your input on this will be appreciated. thanks Shazni Nazeer Senior Software Engineer Mob : +94 37331 LinkedIn : http://lk.linkedin.com/in/shazninazeer Blog : http://shazninazeer.blogspot.com On Wed, Aug 6, 2014 at 4:55 PM, Senaka Fernando sen...@wso2.com wrote: Hi Subash, Well I don't think that's just it. We had something running for the 2013 WSO2Con, and Chandana was looking into moving that into the Store as well. Not sure whether he did that. Apart from this, in terms of plans, what I had in mind is what we discussed offline. Thanks, Senaka. On Wed, Aug 6, 2014 at 1:03 AM, Subash Chaturanga sub...@wso2.com wrote: Hi Senaka et al, Had a quick look at what Shazni did compared to Chandana's one. In provider's view we seems in line with what was there initially with the reduced service RXT. @Senaka, anyway with the unified gov model, we probably end up a more reduced version for service and with some updates. Let's keep it till then. For Doc links, even in service store we have this same old 3 doc link field with type/url/comment. @Ruchira is it possible to have something for documentation like whats there in AM ? @Senaka Have we thought about the store front for services ? Currently (even with Chandana's impl) you can't do anything in store other than tag/rate/comment. What were the plans you had on service store ? On Tue, Aug 5, 2014 at 11:54 AM, Shazni Nazeer sha...@wso2.com wrote: Hi Chandana, Thanks for the information. Yes. That's what I'm trying to achieve at the moment. With the new ES, first we need to be able to add a service through a wsdl url. In the earlier work, was that happening in the same service UI? If so what would be the case for the other fields such as the name-space? Was it getting hidden dynamically or is it simply getting ignored when the wsdl url is provided? Regarding addition of wsdl addition by zip files, there can still be issues as you mentioned. Depending on that, we might not consider that and wsdl addition using url for the first milestone. Appreciate your feedback. regards Shazni Nazeer Senior Software Engineer Mob : +94 37331 LinkedIn : http://lk.linkedin.com/in/shazninazeer Blog : http://shazninazeer.blogspot.com On Sat, Aug 2, 2014 at 7:34 PM, Chandana Napagoda chand...@wso2.com wrote: Hi Shazni, Service creation using WSDL URLs was already implemented in an older version of ES. But there was a problem with service creation using a zip file of WSDLs [1]. Will send you a separate mail with exiting code blocks for service creation using a WSDL URL. [1]. [Architecture] Jaggery unzips all folders? Regards, Chandana On Sat, Aug 2, 2014 at 10:00 AM, Chandana Napagoda chand...@wso2.com wrote: Hi Shazni, Service creation using WSDL URLs was already implemented in an older version of ES. But there was a problem with service creation using a zip file of WSDLs [1]. Will send you a separate mail with exiting code blocks for service creation using a WSDL URL. [1]. [Architecture] Jaggery unzips all folders? Regards, Chandana On Fri, Aug 1, 2014 at 2:35 PM, Shazni Nazeer sha...@wso2.com wrote: Hi Senaka, First of all thanks for the information. I already had a call with Chandana together with SameeraM regarding this. It was understood that the work Chandana did (which was working
Re: [Architecture] RFC: Should we add inline extension to CEP?
Can we run Clojure from Java? How fast would that be? Can we give a example on how it will look like? I was chatting with Sanjiva, and he proposed java scripts. However, until we switch to Java 8, it is slow. Need to discuss that. --Srinath On Mon, Nov 24, 2014 at 1:20 PM, Lasantha Fernando lasan...@wso2.com wrote: Can we use Clojure for this? Clojure can be used as a dynamic language as well [1,2]. I think we should be able to use the load-file [3] function or load/load-script [4,5]. Since clojure has a strong affinity to Storm, someone coming in from Storm background will be more used to Clojure IMHO. Clojure also supports lambda expressions. (It is also mostly a functional programming language :-)) [1] http://nicholaskariniemi.github.io/2014/01/26/clojure-compilation.html [2] http://nicholaskariniemi.github.io/2014/02/06/clojure-compilation2.html [3] https://clojuredocs.org/clojure.core/load-file [4] https://clojuredocs.org/clojure.core/load [5] https://clojuredocs.org/clojure.main/load-script Thanks, Lasantha On 22 November 2014 at 09:15, Srinath Perera srin...@wso2.com wrote: Would that needs tools.jar in the classpath? One advantage of scala are lamba function (e.g. see Sameera's slides on java 8) .. but disadvantage is you need to learn scala a bit. --Srinath On Fri, Nov 21, 2014 at 4:43 PM, Rajeev Sampath raje...@wso2.com wrote: On Fri, Nov 21, 2014 at 10:40 AM, Srinath Perera srin...@wso2.com wrote: Useful to have in competition with Storm. Performance is the concern. One ida is to get extensions as scala function and running is using https://code.google.com/p/scalascriptengine/ This will be a very useful feature to have. Also another option is to let users embed plain java code inline, and then convert it to bytecode at the query initialization time with a bytecode generator like Javassist. http://www.csg.ci.i.u-tokyo.ac.jp/~chiba/javassist/ Thanks Rajeev WDYT? --Srinath -- Blog: http://srinathsview.blogspot.com twitter:@srinath_perera Site: http://people.apache.org/~hemapani/ Photos: http://www.flickr.com/photos/hemapani/ Phone: 0772360902 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Rajeev Sampath Senior Software Engineer WSO2, Inc.; http://www.wso2.com. Mobile: * +94716265766 %2B94716265766* -- Srinath Perera, Ph.D. http://people.apache.org/~hemapani/ http://srinathsview.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 -- Blog: http://srinathsview.blogspot.com twitter:@srinath_perera Site: http://people.apache.org/~hemapani/ Photos: http://www.flickr.com/photos/hemapani/ Phone: 0772360902 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
