Hi Nuwan, So when are you planning to complete/partially complete to the make use of the new dashborad? This requirement is for BAM toolboxes and planned to be in M6 of BAM2 according to the roadmap [1].
So what you would suggest whether to proceed with old dashboard or wait until newly implementing one? [1] https://wso2.org/jira/browse/BAM#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel Thanks, Sinthuja. On Thu, May 24, 2012 at 12:40 PM, Nuwan Bandara <[email protected]> wrote: > Hi, > > Honestly right now, the dashboard is not that flexible. It was made up > initially with a limited set of requirements. You might be able to > accommodate these with some hacks, but I cannot think of a clean solution. > > We will be start doing a jaggery based dashboard solution within next few > weeks, and will make sure to capture all these requirements and expose a > clean api. > > With what we got right now, > > 1. You can directly use the admin service and push data in > 2. Create a dashboard xml, (which is a registry dump) withing the code > and pump it in to the registry (Refer to the dahboard populater code.) > > Regards, > /Nuwan > > > On Thu, May 24, 2012 at 12:29 PM, Tharindu Mathew <[email protected]>wrote: > >> Sinthuja, >> >> Maybe we should expand on the requirement here. I believe it is not just >> adding a gadget but adding a whole dashboard, i.e. tabs + tab configuration >> of gadgets + gadgets. >> >> Nuwan, this is similar to what we had with dashboard.xml. We need this to >> deploy different dashboards for different scenarios. Ex: A dashboard for >> service monitoring, a dashboard for message tracing, a dashboard for ESB >> monitoring >> >> Can you suggest the best approach for this? This should probably be there >> in the gadget deployment phase already, >> >> On Thu, May 24, 2012 at 12:07 PM, Nuwan Bandara <[email protected]> wrote: >> >>> Hi Sinthuja, >>> >>> We havent done this programatically before, so you mite face road >>> blocks. Please read through DashboardService. I belive addGadgetToUser >>> method, does what you need. >>> >>> addGadgetToUser(String userId, String tabId, String url, String >>> dashboardName, String gadgetGroup) >>> >>> Simply ignore the last parameter and pass null for that. >>> >>> Regards, >>> /Nuwan >>> >>> On Thu, May 24, 2012 at 11:14 AM, Sinthuja Ragendran >>> <[email protected]>wrote: >>> >>>> Hi, >>>> >>>> I have requirement to add a gadget in BAM2 programmatically. I have a >>>> gadget artifact in the file system, and I need this gadget artifact to be >>>> added to the bam gadgets and see that in the bam main dash board >>>> programmatically, rather going through the UI by clicking on add gadgets >>>> and point to the URL. >>>> >>>> What are the possible ways of doing this? Is there any services exposed >>>> to add the gadgets so that I can make use of? >>>> >>>> Currently bam2 has the following features installed: >>>> >>>> org.wso2.carbon.dashboard.dashboardpopulator.server.feature >>>> org.wso2.carbon.dashboard.feature >>>> org.wso2.carbon.gadget.editor.ui.feature >>>> org.wso2.carbon.gadget.editor.feature >>>> >>>> Thanks, >>>> Sinthuja. >>>> >>> >>> >>> >>> -- >>> *Thanks & Regards, >>> >>> Nuwan Bandara >>> Associate Technical Lead & Member, MC, Development Technologies >>> WSO2 Inc. - lean . enterprise . middleware | http://wso2.com >>> blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 >>> 9629 >>> * >>> <http://www.nuwanbando.com/> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Regards, >> >> Tharindu >> >> blog: http://mackiemathew.com/ >> M: +94777759908 >> >> > > > -- > *Thanks & Regards, > > Nuwan Bandara > Associate Technical Lead & Member, MC, Development Technologies > WSO2 Inc. - lean . enterprise . middleware | http://wso2.com > blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 > 9629 > * > <http://www.nuwanbando.com/> >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
