Debug Tracing Builder

In this topic ... How do I... Specifying Inputs Enabling Debug Tracing Related Topics ... Overview: Debugging Web Applications How do I... Debug an Application

The Debug Tracing builder sets a debug tracing property on the WebApp, so that when you run the model , the it displays information from one or more of the following categories in the application server's console window. This information is also written to the debugTracing.txt file in Factory's WEB-INF/logs directory.

Log files for a portlet are found in the deployed portlet WAR's directory. Log files for a standalone application can be found in the deployed enterprise application's directory.

• Profile selection

• Builder Call inputs

• Model Generation

• Model actions

• Service Call requests

• Incoming SOAP requests

• HTTP Parameters in the request

Properties in the log4j.properties file (in Factory's WEB-INF/config directory) determine what information gets displayed during the debug tracing operation.

 

How do I...

Set log4j Properties

Trace the Value of a Variable

Trace a Specific Action

Interpret a Debug Log File

Print Out Value of a Variable

 

Specifying Inputs

The Debug Tracing builder takes the inputs described in the table below. For help on inputs common to many or all builders such as those in the Properties and HTML Attributes input groups, see "Using the Builder Call Editor."

Input Name	Description
Name	Enter a name for this builder call. The Designer displays this name in the Builder Call List.
Trace all actions	Enable this checkbox to trace all action executed as part of the specified action.
Action to trace	Select a method or action list on which to trace execution information. This field is ignored if the Trace all actions field is selected.
(Optional) Log Parameters	Enable this option if you want the HTTP parameters (if any) for the request to be displayed as part of the debug tracing output.
(Optional) Additional debug output	If you want additional information to be debugged, enter the information here. For example, assume you entered a method to be traced in the Action to trace field and you also want a variable to be traced, you would enter an indirect reference to the variable in the Additional debug output field... ${Variables/strVar} We can also trace a Java expression by entering the following in the Additional debug output field: ${Java/<expression_you_want_to_trace>}

 

Enabling Debug Tracing

Before you use the Debug Tracing builder, set the bowstreet.system.debugTracing property in the WEB-INF/config/log4j.properties file to DEBUG. When this property is set to DEBUG, it provides more details, such as the session ID and profile information.

To change the property to DEBUG, do the following:

1. Open the WEB-INF/config/log4j.properties file in your favorite text editor.

2. Change the property from log4j.category.bowstreet.system.debugTracing=INFO,Console,DebugTracing to the following

log4j.category.bowstreet.system.debugTracing=DEBUG,Console,DebugTracing

3. Change priority value from WARN (the default value) to DEBUG for one or more of the following properties:

# These categories are for system level logging, please set the priority

# of category to INFO, WARN or DEBUG to enable that category

log4j.category.bowstreet.system.request=WARN,Console,Request

log4j.category.bowstreet.system.profileSelection=WARN,Console,ProfileSelection

log4j.category.bowstreet.system.regen=WARN,Console,Regen

log4j.category.bowstreet.system.builderCalls=WARN,Console,BuilderCalls

log4j.category.bowstreet.system.modelActions=WARN,Console,ModelActions

log4j.category.bowstreet.system.webservice.serviceCall=WARN,Console,ServiceCalls

log4j.category.bowstreet.system.webservice.incomingSOAPRequest=WARN,Console,IncomingSOAPRequests