WebSphere brand IBM WebSphere Premises Server, Version 6.1.x

Troubleshooting the Spatial Management Client

This topic describes problems that might occur with the Spatial Management Client and provides possible solutions.

The Spatial Management Client does not completely start

If you cannot see the map of the current area, and you cannot see Zones in the Zones list (the Zones list basically is empty), then make sure that the Adobe® Scalable Vector Graphics (SVG) Viewer plug-in for your browser is installed.

Search results are not saved

If you are using the Spatial Management Client on a Windows® operating system and your search results are not properly saving as HTML, enable ActiveX in Internet Explorer:

  1. In the browser, navigate to Tools > Internet Options.
  2. Select the Security tab.
  3. Click Custom Level.
  4. Scroll down to ActiveX controls and plug-ins > Initialize and script ActiveX controls not marked as safe, and click Enable or click Prompt if you would like to be prompted with a confirmation window in order to save the search results.
  5. Click Ok, and then click Ok again.

There are also two workarounds you can use if you do not choose to enable ActiveX:

Personal preferences are not saved

There are limitations in saving your personal preferences for the Spatial Management Client:

Tags are still visible when they have already left the area, but the tag counts seem to be correct

If you have this issue, you need to add or modify the value of the <DisplayRefreshCounter> parameter in the prefsV3.xml file. The <DisplayRefreshCounter> parameter forces a repainting of all the tags in the Spatial Management Client every nth poll interval (<pollInterval ms="">).

For example, a setting of <DisplayRefreshCounter>50</DisplayRefreshCounter> means that the Spatial Management Client repaints every 50th poll. If you have a poll interval of 3000 (<pollInterval ms="3000">), then the Spatial Management Client repaints every 150th second.

If you have a lot of tags on the Spatial Management Client, repainting too often increases the load on your system. To avoid overloading, set the parameters to update every 120 seconds, or less often than that.


Library | Support | Terms of use

(c) Copyright IBM Corporation 2004, 2008. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.