Scalable Vector Graphics problems
Consult this topic for problems and solutions for Scalable Vector Graphics.
Using Tivoli Performance Viewer without Scalable Vector Graphics (SVG)
In Version 8.x,
the Tivoli® Performance Viewer
graph uses Dojo Technology for plotting the performance activity rather
than the Scalable Vector Graphics (SVG) format. The Dojo format provides
a better user experience and is more processor and memory efficient
for the application server. The SVG format is still supported but
is deprecated in Version 8 of this product. To use the SVG format
and image format, set the JVM property to false
;
for example: com.ibm.websphere.tpv.DojoGraph=false
.
If the property is set to false
, Dojo is disabled
and Tivoli Performance Viewer
displays interactive graphics using the SVG format or non-interactive
graphics using the JPG format. When you specify to use the SVG format
by setting com.ibm.websphere.tpv.DojoGraph=false
,
if you do not have the Adobe SVG
browser plug-in installed, you are prompted to download and install
it. If you select not to install the plug-in (by selecting Cancel), Tivoli Performance Viewer displays
the static image. If your browser is Internet Explorer 7, the Adobe SVG installation prompt might
be inaccessible. To resolve the problem, reinstall Adobe SVG. By default, this property is set
to a value of true
to use the Dojo format.
When you specify to use the SVG format by setting com.ibm.websphere.tpv.DojoGraph=false
and
you are viewing performance data in Tivoli Performance
Viewer on a browser that does not support Scalable Vector Graphics
(SVG) graphics, either using the Adobe SVG plug-in or through native
support, complex graphs might take a long time to refresh. Eventually
an out of memory error may occur.
When Tivoli Performance Viewer detects a browser that does not support SVG, it uses Apache Batik to transcode the SVG into a binary image format. The transcoding process is highly memory intensive. The complexity of the graph is affected by two things: the Tivoli Performance Viewer buffer size, which dictates how many points are in each line that is drawn, and the number of selected data points, which dictates how many lines are drawn.
To avoid long refresh times or the out of memory errors, use a browser that supports SVG, either with a plug-in, like the Adobe SVG plug-in, or natively, which is included in some Mozilla builds. If this is not possible, keep the graph simple by limiting the size of the buffer and the number of selected data points.