Consultor Eletrônico

Running Debugger Tool WebSpeed (2.x/3.x) Transaction Server

Running Debugger Tool with WebSpeed (2.x or 3.x) Transaction Server
-------------------------------------------------------------------

IMPORTANT INFORMATION: The PROGRESS Debugger Tool is NOT included
with the WebSpeed product Version 2.x or 3.x. The debug product must
be purchased separately. This debug method is known to work on UNIX
for version 2.x, (unknown if it works on NT) and is known to work
for both NT and UNIX in version 3.x.

NOTE: The -debug command line option does NOT work, you will instead
have to use the steps listed below to run the debugger.

These are the steps required to start the debugger:

1> for WebSpeed 2.x, remove -weblogerror startup option from the
AgentParams entry in the broker configuration file (webspeed.cnf).

for WebSpeed 3.x remove -weblogerror startup option from the
srvrStartupParam= entry in the broker configuration file
(ubroker.properties).

2> you should run with StartInstances = 1, BeginNewInstances = 0,
and MaxInstances = 1. This ensures only one WebSpeed agent will
be running during the debug session.

3> set your DISPLAY variable to the machine you want to run the
debugger on. (Remember the debugger is a GUI window, you will
need Xwindows support - Necessary only on UNIX)

4> modify your web-disp.p (source code) to initialize the debugger
by adding DEBUGGER:INITIATE().

5> modify the broker startup script to add the directory containing
web-disp.p (source code) to the beginning of your PROPATH.

6> modify the code you want to debug with break points by adding
DEBUGGER:SET-BREAK().

Now when you start the Transaction Broker, the agent will
automatically bring up the Debugger in web-disp.p.

You can step through your source code at this point.

RVE (3/5/99)