Hi Sinthuja, Looks good. We may also need to think how to a get data from Cassandra in an generic way in the longer term. (To get things started I think we can use the service present in BAM). I guess this would be largely solved when Cassandra data source impl (this is already there as I got to know from Dinusha) and Cassandra CQL support(Cassandra 1.0) is out.
Regards Buddhika On Thu, Jan 19, 2012 at 11:56 AM, Tharindu Mathew <[email protected]> wrote: > The requirements look good.. > > I believe we should pick some use cases (like the samples) and implement > this... then we can start identifying and filling in the gaps in the > current impl... > > > On Thu, Jan 19, 2012 at 10:12 AM, Sinthuja Ragendran <[email protected]>wrote: > >> Hi, >> >> User need not to write the query. The query for BAM data will be done via >> GUI tool such that the user could select what are the data he wants to have >> in the report. >> Further more according to the inputs given by the user, the jrxml file >> will be edited on the fly and the BAM reporting backend component will >> gather the data from cassendra database and send it to the reporting >> component to fill the data in the report. >> >> Thanks. >> >> Regards, >> Sinthuja. >> >> >> On Thu, Jan 19, 2012 at 5:54 AM, Srinath Perera <[email protected]> wrote: >> >>> Are we going to let user define some query? since it is on BAM data >>> how will it work? >>> >>> Other than that requirements look good to me >>> >>> --Srinath >>> >>> On Wed, Jan 18, 2012 at 6:00 PM, Sinthuja Ragendran <[email protected]> >>> wrote: >>> > Hi, >>> > >>> > I'm currently involved with report generation for BAM2.0. First of all >>> I >>> > would like to finalize the requirements for the report generation. >>> > >>> > After the discussion with BAM team, we have come up with following >>> > requirements, that might be useful in the user point of view. >>> > >>> > Facility to select the type of report (Chart type, Table type, etc) >>> > Facility to select the format of the report (pdf, excel sheet, etc) >>> > Customizing the data which is supposed to be in the report (Eg: In the >>> case >>> > of chart type report, he need to give what are the data in the x-axis, >>> > y-axis. In the case tabular format which data(request count, response >>> count, >>> > etc) should be reported, etc) >>> > Facility to customize the time line of the report (ie, whether one >>> > summarized report for whole year or separate reports for all 12 months) >>> > Custom formating of report >>> > >>> > - Changing Logo >>> > - Changing font style/colour, background color >>> > >>> > Automatic periodic report generation (ie, setting the date and time, >>> so that >>> > the report generation occurs automatically) >>> > Facility to send the automatically generated reports to the given >>> e-mail >>> > addresses. >>> > Interaction between the dashboard and the reports. For example a user >>> would >>> > want to create a report out of what he sees in his dashboard. (Not >>> sure how >>> > far this is feasible) >>> > >>> > Our plan is to make use of our WSO2 reporting component which uses >>> > JasperReports[1]. To use this we should first create a generic report >>> > template (.jrxml file) and save as default templates for defined report >>> > types ( for creating report templates we can use iReport [2]), and then >>> > according to the user preference changing the xml tags and attributes >>> of the >>> > .jrxml on the fly. Then the reporting component which uses jasperreport >>> > library, will create the needful final report. Furthermore the data >>> from the >>> > cassendra database which is used by BAM2.0, can be sent by beans >>> format, >>> > java collection maps, or xml for the data filling of report. >>> > >>> > Please share your thoughts on above. >>> > >>> > [1] >>> > >>> http://jasperforge.org/uploads/publish/jasperreportswebsite/trunk/tutorial.html >>> > >>> > [2] >>> > >>> http://jasperforge.org/website/ireportwebsite/IR%20Website/ir_getting_started.html?header=project&target=ireport >>> > >>> > >>> > >>> > Thanks. >>> > >>> > Regards, >>> > Sinthuja. >>> > >>> > _______________________________________________ >>> > Carbon-dev mailing list >>> > [email protected] >>> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> > >>> >>> >>> >>> -- >>> ============================ >>> Srinath Perera, Ph.D. >>> http://www.cs.indiana.edu/~hperera/ >>> http://srinathsview.blogspot.com/ >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >> >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Regards, > > Tharindu > > blog: http://mackiemathew.com/ > M: +94777759908 > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
