Hi Tharindu, On Wed, Oct 24, 2012 at 12:25 AM, Tharindu Mathew <[email protected]> wrote:
> OK, trying to decode what you are expecting here... For example, lets say we want to build a sample where someone could do use runtime data from BAM to do lifecycle management in G-Reg. Like, before moving from staging into production, we need to validate whether the necessary SLAs are met in the staging environment. > > Will having a REST-based API running over HTTP that allows you to access > your summarized data, make what you are trying to do easier? > Yes, it would. We can define a somewhat-standard and easy to understand connector to BAM from G-Reg or any other WSO2 or non-WSO2 product if we had some API. Thanks, Senaka. > > > On Tue, Oct 23, 2012 at 11:35 AM, Senaka Fernando <[email protected]> wrote: > >> Hi Tharindu, >> >> I understand what you mean, you store stuff in a DB, and anyone can use >> JDBC to talk to the DB, that's nothing new. Of course it'll become an >> answer to someone trying to do this. But, the usability of this is not the >> best. >> >> For example, if we say you need to use JDBC to access the user store or >> registry remotely, will that work? IMHO, the answer is no. So, even in BAM >> we should have a better answer than "you can simply use JDBC to talk to the >> DB and get what you want" or people are going to find it really hard to >> integrate BAM into their solutions. >> >> The level of usability that you find in some products of the platform, is >> not the level of usability you get with BAM today. If you want to talk to >> BAM and get summarized data, the effort you need to put in is similar to >> writing your own data harvesting application. Now, that's the concern I'm >> having. >> >> Thanks, >> Senaka. >> >> >> On Tue, Oct 23, 2012 at 11:55 PM, Tharindu Mathew <[email protected]>wrote: >> >>> I think what you are asking for customized solutions on top of BAM. We >>> achieve this to an extent with toolboxes. >>> >>> But, you are trying to get another feature in Carbon integrated. For >>> this, we can build a specific solution for whatever you are trying to >>> achieve. Knowing the use case would be helpful. >>> >>> But, for a usual case JDBC is good enough. You have a standard way of >>> accessing your data through a well known API. This is how any reporting >>> engine can be used to access data in BAM as well. Everyone has their JDBC >>> connectors. This is the from-BAM API. >>> >>> >>> On Tue, Oct 23, 2012 at 11:18 AM, Senaka Fernando <[email protected]>wrote: >>> >>>> Hi Chintana, >>>> >>>> Of course this can be done in many ways including having DSS in front >>>> of BAM. The question I have is around what BAM supports as "first-class". >>>> Right now, if someone wants to integrate tool/product/component X with BAM, >>>> it is only in the "to-BAM" direction. There is no "from-BAM" support, >>>> unless you do some coding/configuring on your own. That's what I am trying >>>> to find a solution for. >>>> >>>> For example, say I have a check-list, and I need to validate that the >>>> service has been performing at a certain level in staging before it goes >>>> into production. I can do that right now with BAM, but the approach is not >>>> that easy. >>>> >>>> Thanks, >>>> Senaka. >>>> >>>> >>>> On Tue, Oct 23, 2012 at 11:19 PM, Chintana Wilamuna >>>> <[email protected]>wrote: >>>> >>>>> Since it's an RDBMS thing, you can slap a DSS in front of it if you >>>>> need to access through services. Mobile clients? No problem, DSS can do >>>>> JSON. Are you talking about a Java API? >>>>> >>>>> -Chintana >>>>> >>>>> On Sat, Oct 20, 2012 at 10:14 AM, Senaka Fernando <[email protected]>wrote: >>>>> >>>>>> Hi Tharindu, >>>>>> >>>>>> No, that is too abstract. "You can write Java-code and build your >>>>>> integration around BAM" is not an acceptable answer for a user or an >>>>>> integrator working with the BAM product. If we have standardized a way to >>>>>> build gadgets to display the data, the same should be repeatable to >>>>>> produce >>>>>> some APIs to access this data. I see a lot of usefulness in doing this. >>>>>> For >>>>>> example, >>>>>> >>>>>> 1. If I want to correlate statistics reported on BAM with services or >>>>>> other assets in the repository I can do that if I had some access to the >>>>>> runtime data. >>>>>> 2. If I wanted to build some mobile applications that consumes these >>>>>> data, I need not build my own data harvesting layer. >>>>>> >>>>>> We might not need an immediate solution to address this problem, but >>>>>> IMHO we should not consider that everything in BAM boils down to >>>>>> mechanisms >>>>>> to build some gadgets that end up on a portal. As per the current trends, >>>>>> most organizations would be interested in building and publicizing APIs >>>>>> compared to building dashboards. Mobile and/or other application >>>>>> developers >>>>>> will think about how to create UIs out of them. >>>>>> >>>>>> Thanks, >>>>>> Senaka. >>>>>> >>>>>> On Sat, Oct 20, 2012 at 3:44 PM, Tharindu Mathew >>>>>> <[email protected]>wrote: >>>>>> >>>>>>> We've found a great new API for this. I think it's called jdbc. ;-) >>>>>>> On Oct 20, 2012 3:02 AM, "Senaka Fernando" <[email protected]> wrote: >>>>>>> >>>>>>>> Hi Kasun, >>>>>>>> >>>>>>>> Well in that case, we seem to have a gap there. You can access the >>>>>>>> database means we don't have an API for it. While we can develop >>>>>>>> extensions >>>>>>>> to get the job done on a case-by-case basis, I don't think this is a >>>>>>>> compelling answer. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Senaka. >>>>>>>> >>>>>>>> On Sat, Oct 20, 2012 at 3:21 PM, Kasun Weranga <[email protected]>wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> On Sat, Oct 20, 2012 at 2:59 PM, Senaka Fernando >>>>>>>>> <[email protected]>wrote: >>>>>>>>> >>>>>>>>>> Hi all, >>>>>>>>>> >>>>>>>>>> Say I've write a BAM toolbox which does everything from >>>>>>>>>> collecting, summarizing and displaying on dashboard. Now, is there >>>>>>>>>> an API I >>>>>>>>>> can use to access this data (what gets displayed in the gadgets) so >>>>>>>>>> that I >>>>>>>>>> can use it outside of BAM? For example, in small Java Client or a >>>>>>>>>> Validation in a G-Reg lifecycle. >>>>>>>>>> >>>>>>>>> >>>>>>>>> We store summarized data in RDBMS, then the gadgets will collect >>>>>>>>> those data from the database. So If you want, you can directly access >>>>>>>>> the >>>>>>>>> database to get the summarized data. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> KasunW. >>>>>>>>> >>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> Senaka. >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> *Senaka Fernando* >>>>>>>>>> Member - Integration Technologies Management Committee; >>>>>>>>>> Technical Lead; WSO2 Inc.; http://wso2.com* >>>>>>>>>> Member; Apache Software Foundation; http://apache.org >>>>>>>>>> >>>>>>>>>> E-mail: senaka AT wso2.com >>>>>>>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>>>>>>>> Linked-In: http://linkedin.com/in/senakafernando >>>>>>>>>> >>>>>>>>>> *Lean . Enterprise . Middleware >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> *Kasun Weranga* >>>>>>>>> Software Engineer >>>>>>>>> ** >>>>>>>>> *WSO2, Inc. >>>>>>>>> *lean.enterprise.middleware. >>>>>>>>> mobile : +94 772314602 >>>>>>>>> <http://sanjeewamalalgoda.blogspot.com/>blog >>>>>>>>> :<http://sanjeewamalalgoda.blogspot.com/> >>>>>>>>> http://kasunweranga.blogspot.com/ >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> *Senaka Fernando* >>>>>>>> Member - Integration Technologies Management Committee; >>>>>>>> Technical Lead; WSO2 Inc.; http://wso2.com* >>>>>>>> Member; Apache Software Foundation; http://apache.org >>>>>>>> >>>>>>>> E-mail: senaka AT wso2.com >>>>>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>>>>>> Linked-In: http://linkedin.com/in/senakafernando >>>>>>>> >>>>>>>> *Lean . Enterprise . Middleware >>>>>>>> >>>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Senaka Fernando* >>>>>> Member - Integration Technologies Management Committee; >>>>>> Technical Lead; WSO2 Inc.; http://wso2.com* >>>>>> Member; Apache Software Foundation; http://apache.org >>>>>> >>>>>> E-mail: senaka AT wso2.com >>>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>>>> Linked-In: http://linkedin.com/in/senakafernando >>>>>> >>>>>> *Lean . Enterprise . Middleware >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> [email protected] >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Chintana Wilamuna >>>>> Senior Technical Lead >>>>> WSO2, Inc.; http://wso2.com >>>>> lean.enterprise.middleware >>>>> >>>>> phone: +94 72 145 4545 >>>>> blog: http://engwar.com/ >>>>> photos: http://flickr.com/photos/chintana >>>>> linkedin: http://www.linkedin.com/in/engwar >>>>> twitter: twitter.com/std_err >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Senaka Fernando* >>>> Member - Integration Technologies Management Committee; >>>> Technical Lead; WSO2 Inc.; http://wso2.com* >>>> Member; Apache Software Foundation; http://apache.org >>>> >>>> E-mail: senaka AT wso2.com >>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>> Linked-In: http://linkedin.com/in/senakafernando >>>> >>>> *Lean . Enterprise . Middleware >>>> >>>> >>> >>> >>> -- >>> Regards, >>> >>> Tharindu >>> >>> blog: http://mackiemathew.com/ >>> M: +94777759908 >>> >>> >> >> >> -- >> *Senaka Fernando* >> Member - Integration Technologies Management Committee; >> Technical Lead; WSO2 Inc.; http://wso2.com* >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> > > > -- > Regards, > > Tharindu > > blog: http://mackiemathew.com/ > M: +94777759908 > > -- *Senaka Fernando* Member - Integration Technologies Management Committee; Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
