Hi Chamara, Yes, for now the only way doing this is by manually editing dashboard.xml configuration file. I accept this is a hacky method of doing this. To overcome this we have planned to get the installed toolboxes via admin service call and I'm currently working on it.
Thanks, Chamath. On Wed, Oct 17, 2012 at 3:12 PM, Chamara Ariyarathne <[email protected]>wrote: > There is a configuration as > > {BAM_HOME}/repository/deployment/server/jaggeryapps/bamdashboards/dashboard.xml > > <bamdashboards> > <dashboard isPrimary="true"> > <name>mediation_stats_monitoring</name> > </dashboard> > <!-- uncomment below node to activate service stats monitoring > dashboard --> > <dashboard isPrimary="false"> > <name>service_stats_monitoring</name> > </dashboard> > <!-- uncomment below node to activate activity monitoring > dashboard--> > <dashboard isPrimary="false"> > <name>activity_monitoring</name> > </dashboard> > </bamdashboards> > > This needs to be edited all the time a toolbox is deployed. > > Assume already Service Statistics toolbox is running. Then if Medation > Stat toolbox is uploaded this file gets changed as the > service_stats_monitoring part gets commented out, and the service > statistics link in the dashboard disappear. If it is needed back the file > should be edited, and restart the server. > > Isn't there a better way of deploying toolboxes without disappearing > current dashboard pages? > > -- > *Chamara Ariyarathne* > Senior Software Engineer - QA; > WSO2 Inc; http://www.wso2.com/. > Mobile; *+94772786766* > > -- _-_-_-_-_-_-_-_-_-_ Thanks & Regards, Chamath. *+94 71 532 0009*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
