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
- Tuning for performance
Applications created using IBM® WebSphere Portlet Factory need to be architected for performance.
- The log4j debug property
To have debug tracing output written to the log file, the log4j.category.bowstreet.system.debugTracing property must be set to a value of INFO (default).
- Starting builder call timing tracing
To analyze the time that builder calls take during regeneration, you can start builder call timing tracing.
- About using system tracing
Use the system tracing feature to store the WebApp execution path and the execution time for each action (Page or Method).
- Debug Tracing builder
Use the Debug Tracing builder to trace a variable or a specific action in a model.
- Interpreting a debug log file
After you run your application, open the debugTracing.txt log. It should look similar to the following:
- Print the value of a variable
You can use a tool available from the Action List builder to generate a System.out.println statement.
- Debug with Eclipse/RAD using Factory Model Execution Debugging
The Factory Model Execution Debugger support enables model developers to easily leverage the Eclipse/RAD integrated debugger.
- Enabling debug tracing
Before you use the Debug Tracing builder, set the bowstreet.system.debugTracing property to DEBUG.
- IBM WebSphere Portlet Factory Designer Task view error messages
Errors and warnings that result from a builder's generation code are sent to the IDE's Tasks view.
Library | Support |