3. User Interface
- Q: How can I ignore an auto-discovered resource?
- Q: I selected a search suggestion from the resource search box, but I didn't get any results. Why?
- Q: Errors and stack traces in the GWT Message Center are sometimes not helpful. How can I find out what the real problem is?
- Q: Why are the graphs and charts on the MONITOR tab in the GUI not displayed?
Q:
How can I ignore an auto-discovered resource?
A:
If your agent discovers a new platform and finds a few resources that you do not want to take into inventory, you have to tell the server to ignore those resources.
First, you can select the resources to import in the auto-discovery portlet and deselect the unwanted resources. As long as they are displayed in the portlet, they are not imported.
The other option is to select the resource you do not want to import and click on Ignore, so it no longer appears in the portlet. However, if you try this on a resource on a freshly discovered platform, it will fail. The reason for this is that the inventory is organized in a tree-like manner with the platform as a tree-root. When a server or service is taken into the system, regardless of whether it is imported or ignored, it is attached below that root. When the platform is not yet imported into the inventory, there is no root that the ignored resource can be attached to.
You can ignore a server on a platform by performing the following steps:
- Import the platform and leave that server unchecked.
- When the platform is successfully imported, select the server and click Ignore.
It is not possible to just ignore a platform. If you want to ignore a platform, do not run an agent on it.
Q:
I selected a search suggestion from the resource search box, but I didn't get any results. Why?
A:
The suggestions in the search drop-down are not filtered by category — but the search results are. For example, if you are in the Server tab, the dynamic search suggestions will prompt for
type==CPU, even though CPU is in the service category. If you select type==CPU, then nothing is returned in the search, because the search results are filtered by the category, and the search is implicitly set to the server category.
Q:
Errors and stack traces in the GWT Message Center are sometimes not helpful. How can I find out what the real problem is?
A:
If there are errors in the UI, an error ID is displayed, enclosed in square brackets. That can be used to track down the error and stack trace in the JBoss ON server's log file. For example:
java.lang.RuntimeException:[1312480384219] ...
The server-side log information is more useful because these exceptions are occur on the server-side and are forwarded to the GWT client.
Q:
Why are the graphs and charts on the MONITOR tab in the GUI not displayed?
A:
Errors like the following can appear in the JBoss ON server log:
java.lang.NoClassDefFoundError: Could not initialize class org..enterprise.gui.image.chart.ColumnChart
To generate the text in graphs and charts, Java requires specific system fonts to be installed. Error messages will appear if the required font package is not installed. On Red Hat Enterprise Linux, make sure the urw-fonts package is installed:
yum install urw-fonts
