Unexpected Map Content or Display Problems

To analyze client side problems like missing map contents, missing buttons in the GUI or client side errors a log-monitor and a debug mode support you.


Log Monitor


With the log monitor it is possible to log the communication (requests and responses) between client and server.

The log monitor can be opened by pressing CTRL+ALT+M after project start. A new window will appear containing several divided parts.

The top window contains client requests

The middle window contains server responses, allocation of request/response is done via request_id and RES@id_res"

The bottom window contains client-side debug information during runtime with error and warning information etc

The button get client initial info shows the GET_INIT Response on which the client initializes

The button get client state info shows the JavaScript Components and the actual attribute states

The Button get server state info shows some details of the server-side states, e.g. build time

The Button save as textfile allows to save all log entries in one single file


Log monitor

Log monitor


Debug Settings


With the debug settings it is possible to further analyze problems by e.g. displaying cache and extent information. Open the debug settings by pressing CTRL+ALT+D after project start. A small iFrame will appear showing several checkboxes.

Display cache and extent information:
Blue raster lines are shown under the map so transparency can be checked. Cache tile information for cached map services will be displayed as red lines, after the map has been refreshed once. The cache information is shown for every active cached data frame. Besides, information is shown in the tiles: Cache ID/ R: Row/ C: Column/ ct: order in which tiles are requested. Border of the cache that is restricted through the full extent property is shown by pictures named TOP, RIGHT, BOTTOM and LEFT. With dynamic maps the full extent is displayed by an outline.

Cluster Debugging:
This option is only active if a client-side cluster display is used. It shows the dependency between single objects and their cluster. Be aware that activating this option will slow down the performance of the cluster display significantly.

Show external call frame:
A check will show the hidden iFrame (default to_weboffice) above the overview map with a red border. This way you can check correctness of calls.

Show hidden GUI elements:
GUI hidden by the user will be displayed.

Use map fading:
This will enable/disable the map fading which is helpful for slow remote connections

Execute Javascript - eval ():
Javascript commands for use in WebOffice context.


Debug settings

Debug settings


Additional Call Parameters


By adding the following parameters to the URL call it is possible to force WebOffice 10.9 SP1 to start with activated log monitor/debug consoles:

clientlog=true (e.g. http://myserver:8080/WebOffice/synserver?project=myproject&clientlog=true)
This will start WebOffice 10.9 SP1 with an opened client-side log monitor. All logging information from startup of the client will be logged.

consolelog=true (z.B. http://myserver:8080/WebOffice/synserver?project=myproject&consolelog=true)
This will start WebOffice 10.9 SP1 with activated logging in the debug console of the browser.

clientmode=tab|phone (z.B. http://myserver:8080/WebOffice/synserver?project=myproject&clientmode=tab)
This will start WebOffice 10.9 SP1 in either the tab or the phone mode of WebOffice mobile client.