Chat now with support
Chat with Support

Identity Manager 8.0 - Web Designer Reference Guide

Web Designer Editor Web Designer Structures and Functions The Web Designer Object Model Working with the Web Designer Web Project Configuration Options Customizing the Web Portal Basics of Web Designer Programming Compiling and Debugging Monitoring Frequent Tasks in the Web Portal

Debugging

If error messages are shown in the preview while the web application is running, Web Designer provides different forms of help.

Note: A WCF connection must be created for this function.

You can set breakpoints in the definition tree view for debugging. For more information, see Setting Breakpoints.

You can use the following buttons in the preview to manage Web Designer debugging.

Table 64: Buttons for managing debugging in the preview
Icon Function
Enable debugger.
Single step mode.
Resume execution

For more information, see Working with the Preview.

An external program can also be used to debug the web application (for example: Visual Studio). Debugging steps are created in the debug compilation to help you with subsequent debugging. Debugging with external programs is dependent on the environment used. This approach is therefore not referred to again here.

For internal debugging, called up methods can be displayed in the Call Stack view. This gives you important information on the source of the error.

For more information, see Call stack.

Setting Breakpoints

To set a breakpoint

  1. Perform one of the following tasks.
    1. Open the relevant module or component in the navigation view.
    2. Select a corresponding object in the properties view and click .

    For more information, see Properties.

  2. Mark the node on which the breakpoint is to be set and select Set breakpoint from the context menu.

    Note: Not all nodes in the definition tree view can support a breakpoint. However, as a general rule, a breakpoint can be set on all nodes that can be suspended in single step mode. A breakpoint can also be set for Container, Label- or Button-type nodes. In these cases, a breakpoint is activated as soon as the control is rendered.

    The marked node is highlighted in red.

To remove a breakpoint

  • Mark the node with a breakpoint and select Remove breakpoint from the context menu.

    The marked node is no longer highlighted.

Call Stack

The Call stack view contains a list of internal action calls when the debugger is enabled and a breakpoint activated. For more information, see Setting Breakpoints. All actions executed during the breakpoint are listed. This information can be used to identify the C# methods and related DLLs causing the error.

 NOTE: The description of the Call Stack given here only helps you to pinpoint the error source For debugging itself, use external development tools such as Visual Studio.

The Call Stack view provides the following information:

  • Method

    Name of the method called up

  • DLL

    DLL name. The DLL provides you with the origin of the method.

Monitoring

A installed web application can be monitored from your own web site.

The user groups authorized to call up the monitor page are specified in the Monitor.config configuration file. By default, these are all the users that are members of the role Builtin\Administrators.

The monitor page currently has five tabs. The information shown on the monitor page or the available functions are described below. This page is currently available in the languages configured in your web browser.

To open the monitor page

  1. Perform one of the following tasks.
    1. Click on the start page.
    2. Select Debug views | Monitor page from the menu bar.

    The monitor page is opened in the standard browser.

Detailed information about this topic
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating