Portlet Factory, Version 6.1.2


 

Overview: debugging an application

There are multiple ways to determine the cause of problems occurring in a web application.

You can use:

Debug tracing

To track down bugs in a model or application. The Debug Tracing builder allows you to trace variables and actions. This builder writes trace information to a log file allowing you review the logged trace output after you have run a model.By default this log file is given the following name:
web_app_dir\project_name\WEB-INF\logs\debugTracing.txt

Builder call timing tracing

You can analyze the time that builder calls take during regeneration. Use the builderCallTiming property in the log4j.properties file.

Designer Task view

To review errors and warnings that result from the builder generation code.

Application Server console

To view various execution errors and messages.

Parent topic: Working with WebSphere Portlet Factory


Library | Support |