Chart errors

Consult this list of possible causes of charting errors and suggested solutions.

BIRT charts do not display if Java 2 security is enabled in WebSphere Application Server

Java 2 security in WebSphere Application Server prevents the BIRT charting component from running correctly. To view BIRT charts, ensure that Java 2 security is disabled. For more information on Java 2 security, see http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.express.doc/info/exp/ae/csec_rsecmgr2.html

BIRT report design format is not valid

The report designs that you create in the BIRT Designer should contain a single data set and a single chart or table and nothing else. Other items in the report might cause the error,

TIPCH0005E The design format for the chart or table is not valid

If you receive this error, modify your chart .rptdesign, upload it again, and open it in a chart widget.

Chart does not render or is very slow to render because the amount of data is too large

When you open a BIRT designed chart that has a large amount of data, it is possible to exceed the capacity of the Jazz™ for Service Management application server. If this happens, you will get an error message. Try pre-filtering the data so that only values of interest get retrieved.

Also, be sure to single-click dashboards that have chart widgets in them. The dashboard might not display correctly or render the chart when it is double-clicked from the navigation tree.

Chart widget might not display in widget list

While working in with a charting widget, you can change the type of chart by selecting another one from a list of available charts. Although it is unlikely, it is possible for the list to not populate with the available charts. If this happens, log out of the console, restart your browser, and log in again.

Cannot copy and add the charting widget to a new dashboard

When copying the Charting widget and adding it to a new dashboard, you might get this message:

CWLAA6003 Could not display the widget, 
the widget may not be started. Check the error logs

If this happens, ensure the charting role that your user ID is assigned to has the Editor access level assigned.

Error messages while using the Charting widget

While using the charting widget, you could get this error message:

TIPMSG1003E  An error occurred while making the server request.
Error: 'dojo.byId(...)' is null or not an object

Alternatively, it might be an EOF (End Of File) exception that appears. If either of these errors occurs, close the error message window and proceed. Most of the time the chart will load; if it does not, you can either click Refresh

Refresh in the widget or reload the chart from the selection.

Many users are loading to the same dashboard that has charting widgets

This error can be displayed if too many users attempt to open a chart in the same dashboard at the same time:

TIPCH0006E An error occurred while collecting data for the chart, 
check the web service data source. 
Cannot set the string value () to parameter 1 java.rmi.RemoteException: 
KFWITM220E Request failed during execution; 
nested exception is: KFWITM220E Request failed during execution.

This error can happen when the system is overloaded with requests. Close the error message window, then click Refresh

Refresh in the chart widget.

Closing many chart widget dashboards in quick succession gives an error

When running the console in the Firefox browser, you might get this error if you quickly close many dashboards that have chart widgets:

TIPMSG1003E  An error occurred while making the server request.
Error: dojo.byId(this.namespace + "chartNameH") has no properties

If this happens, close the error message window and proceed. The dashboards will eventually close without error.

Cannot get the result set metadata from the ITM Web Service

When you connect to the ITM Web Service from the BIRT Designer to create a custom chart, you might receive an error message, Cannot get the result set metadata while creating a chart. Here are some possible causes to review with your Tivoli Monitoring administrator:

The IBM Tivoli Monitoring agent (or agents) is stopped or has connectivity problems.
The query is not supported by the Charting widget or BIRT Designer. The Charting widget uses the view's definition, including any filters applied. The BIRT Designer enables you to modify the query. You can check the BIRT Designer log file at <BIRTDesigner>\workspace\.metadata\.log for exception details. If you see this exception, the query might not be supported in this release:
```
Caused by: org.apache.axis2.AxisFault: java.rmi.RemoteException: 
KFWITM220E Request failed during execution.
```
In the Tivoli Enterprise Portal, click Query editor and look for the query in the navigation tree. If the query is not listed, it will not be available to the BIRT Designer or Charting widget. Ask your administrator to check the log files.
If this is long-term historical data that is being retrieved, the Tivoli Data Warehouse Proxy agent is stopped or has connectivity problems. These are examples of errors that can occur when a view type is chosen that queries historical data, but no data exists to return.
```
TIPCH0006E An error occurred while collecting data for the chart: 
Cannot get the result set metadata.java.rmi. RemoteException: 
KFWITM220E Request failed during execution; nested exception is: 
KFWITM220E Request failed during execution.
```
Historical data queries require that historical data collection be configured and started for the attribute groups and that sufficient data bas been gathered to render a historical view. Furthermore, summarized historical data requires that the Summarization and Pruning agent also be configured and the process completed at least once before querying summarized and pruned data.

Timeout or message about not connecting to the server

If the system times out or an error message is displayed while importing an Tivoli Monitoring chart, it is typically because the Tivoli Enterprise Portal Server is unavailable for some reason. Check that the portal server is online and start it if it is not. Then try importing the chart again. If the error is

TIPMSG1000E Detail: AxisFault

open DASH_HOME/properties/charts.properties in a text editor and increase the value of this parameter (180000 is 3 minutes): AXIS_TIMEOUT=180000.

Unable to view Tivoli Monitoring charts after installing the Web GUI followed by Tivoli Business Service Manager

This error can be displayed when you attempt to load a chart from the ITM Web Service:

Axis Fault: Error initializing ITM Import Manager

The ITM Web Service needs to be configured with the login ID for the Tivoli Enterprise Portal Server. Use the ITMLogin command as described in the Additional commands.

Loading a chart from an ITM Web Service continues indefinitely

This error can happen in a saved chart dashboard when the administrative console is running in the Firefox browser and the Page persistence setting in the General properties is set to None. You can click Refresh in the browser toolbar. You can also change Page persistence to Client, and then Save the dashboard with this setting.

Avoid double-clicking dashboards in the navigation bar. If you double-click a dashboard that contains a charting widget, the dashboard might not display correctly or render the chart. A single click is all you need to do.

Problems loading a dashboard after changing to another ITM Web Service

After adding the ITM Web Service and populating charts with data from Tivoli Enterprise Monitoring Agents and OMEGAMON XE agents, do not switch to a different ITM Web Service because there is no guarantee that the same charts and queries will be available and there might be problems loading the dashboard.

Use the chart selector from the chart toolbar to load a different chart. In addition, the ITM Web Service must be installed in the same instance as the Jazz for Service Management application server.

Cannot connect to an ITM Web Service from a remote Jazz for Service Management application server

Connection to an ITM Web Service from a remote Jazz for Service Management application server will not be successful and is not supported in this release. The remote server must define its own Web service connection to be able to import charts from that Web service.

Imported charts are inconsistent with their Tivoli Monitoring counterpart

Many of the Tivoli Enterprise Portal workspaces are designed for showing data from all the managed systems within the enterprise. When these charts are imported into the console, users might notice that some of the charts show data for all managed systems, without grouping data under each managed system name.

To view a subset of the data for the chart, right-click the chart widget and click Preferences. Specify the managed system name in the Parameters tab. The result will be a chart showing data for only the managed system name that was specified. Ensure that the text entered matches the managed system name as it appears in the Tivoli Enterprise Portal client, such as myhostname:NT.

Tivoli Business Service Manager users can import Tivoli Monitoring resources into the Service Component Registry using the Xmltoolkit. Whenever the service is clicked in the service tree, the charting widget automatically receives the managed system name as context (no need to specify the name in Preferences > Parameters).

Too many active report queries

When importing charts from a Tivoli Enterprise Portal Server that is at Version 6.2 (not Version 6.2 Fix Pack 1 or later), the portal server might get a message about too many active report queries. If this happens, add the following environment variable to the portal server environment file:

KFW_REPORT_REQUEST_LIMIT=100

where 100 is the maximum number of outstanding requests that the portal server will allow from each agent. The default value for IBM Tivoli Monitoring V.6.2 is 15. The environment file is opened in a text editor through Manage Tivoli® Monitoring Services or the command line:

itm_install_dir\cnps\kfwenv
itm_install_dir/config/cq.ini
itm_install_dir/config/cq.ini

After editing the environment file, and recycling the Tivoli Enterprise Portal Server, try importing charts again. Adjust the report request limit if you continue to get the same error.

Save to text option for a chart does not work in Internet Explorer 7

By default Internet Explorer is not configured to automatically prompt you to download a file. To configure Internet Explorer 7 to prompt you to download a file:

Click Tools > Internet Options.
In the Internet Options dialog, click the Security tab and click Custom Level.
In the Settings panel scroll to the Downloads section and enable the Automatic prompting for file downloads option and click OK.
Click OK in the Internet Options dialog to return the browser window.

IBM Tivoli Monitoring charts display differently in theDashboard Application Services Hub environment

Some colors from Tivoli Monitoring charts may display differently in the Dashboard Application Services Hub due to differences in their respective color palettes.