 |
 |
 |
 |
|
|
 |
Following is the list of xmls that determine the configuration of the dashboard. You can modify these xmls to change the look of your dashboard to suit your own purposes:
dashboard-components.xml: The main dashboard configuration xml (BOM) defining the static hierarchy of the services/components and the info about what all plots are to be shown for a given service/component.
dashboard-ui-defaults.xml: The global default ui values for the display components. These will be over-ridden in case they are speficied in the dashboard-components.xml.
dashboard-allnodes.xml: Defines the list of stats that are to be shown for a server in the enterprise view.
dashboard-user-dashboard.xml: Contains the details about the configured dashboards.
history-collector.xml: Defines the source of obtaining the statistic data for all the stat-ids. (object-name, method-name of the target MBean that provides the corresponding stat data). The stats are identified by their stat-ids. Dashboard will refer to these stat-ids to get the data. The history-collector.xml is located at <install_dir>/server/nodes/<node_name>/config, while the other xml files are located at <install_dir>/server/nodes/<node_name>/archives/public_html/admin/config.
dashboard-ui-defaults.xml to accomplish this. For example, to change the background color of the dial, you can change the value of the bgcolor attribute of the <dial-display> element to the new value.
<dial-display bgcolor="eeeeee" textcolor="666666" safe-color="66cc66" caution-color="ffcc66" danger-color="ff6666" divisions="5" type="relative"/>
Similarly, you can change the text color, the number of y divisions on the graph the kind of plot (whether line, area, or bar) that are shown initially, etc.
dashboard-allnodes.xml and add or remove the statistics that you want to see there. But you have to keep in mind that there is a limited real-estate available.
For example, to change the vertical bar that shows up along-side the Server node, you can make the following change:
<index>
<nodes>
<bargraph display-name="CPU Usage">
<max-stat stat-id="trend-008"/>
<current-stat stat-id="trend-009"/>
</bargraph>
<nodes>
<index>
The bargraph element provides the statistic ID for the maximum possible value and the current value.
Similarly, to have the JVM CPU Usage displayed in the property table along-side the Server node, instead of Web Sessions, replace the property element:
<index>
<nodes>
<properties>
<property id="3" display-name="Web Sessions">
<stat id="trend-006" context-based="false"/>
</property>
<nodes>
<index>
with:
<index>
<nodes>
<properties>
<property id="1" display-name="JVM CPU Usage">
<stat id="trend-025" context-based="false"/>
</property>
<nodes>
<index>
dashboard-components.xml. For example, if you want to remove the marker Applications node in the tree and just display all the applications, ears, wars, and jars directly beneath the root, just remove the <component id="Applications" opcode="" type="marker"> element and add all it's children directly to the component-hiearchy element.dashboard-components.xml will look like this:
<node>
<component-hiearchy>
<component id="Applications" opcode="" type="marker">
<component id="ear" opcode="0107" type="many">
<component id="war" opcode="0211" type="many"/> ... </component>
<component id="ear" opcode="0112" type="many"/> ... </component>
<component-hiearchy>
</node>
If there is a need to add a new component to the hierarchy, say list the JMS Destinations under the JMS Container, then add the following element as a child to the <component id="JMS" opcode="0104" type="one"/> element.
The value of the opcode should be the operation ID corresponding to the operation element in dashboard-components.xml, that defines the operation to get a list of JMS destinations. You will have to look up the MBean repository on the Server for the object name and the method name that provide this list.
component element under <index>/<components> element in the dashboard-components.xml. This element specifies the list of graphs/dials/properties that need to be displayed for each component in the component-hierarchy tree.
The id attribute of component element forms the link. The /graphs/graph element corresponds to the graphs (both small and big), /properties/property element to the tabular properties, and /dials/dial for the dials.
On the panel, only two dials and two small graphs can be seen. So if there are more than two dials or graphs, then only the first (in the order in which they appear) two are picked and others are not considered.
For example, if Web Container Sessions is to be shown as the first dial for the server component, that is, when the Server node is clicked in the tree, move the following under the /dials/dial element (of the component element which has the id attribute set to server) as the first element child:
<dial id="5" name="Web Container Sessions" unit="Count" caution-value="60" danger-value="90"> <stat id="trend-006" context-based="false"/> </dial>
Here itself you can modify the other UI features of the dial like the name for the unit to be used, the caution-value and the danger-value.
Related Topics:
 |
|
| © Pramati Technologies 2007 | Runs on Pramati Server | Feedback | Legal |