Debugging from a remote workstation

You may want to interact with the debugger on a workstation that is remote from the client application, the OLT viewer, or both.

The following steps assume that you intend to run your client application on one workstation, OLT on a second workstation, and the debugger interface on a third workstation. Your application server can be running on any of these machines or on a fourth machine.

To create a trace, then debug in step-by-step mode from a remote workstation, follow these steps:

  1. From a command line on the workstation where you want to view the trace, enter olt. OLT starts.

    ngwin.gif (1069 bytes)Do not close the OLT command prompt window until you have finished your trace session.

  2. From a command line on the workstation where you want the debugger to open, enter the following string:

    idebug -qquiet -qdaemon -quiport=8001

    where:
    8001 = port number entered in step 2b, if not 8001

    The debugger daemon starts.

  3. Start your client application.

    C++ client application:
    Start your C++ application from a command prompt.

    Java client application:
    At a command prompt, enter this command:

    for Java 1.1.x:

    java_g -debug -nojit
    -Dcom.ibm.CORBA.requestTimeout=0
    -Dcom.ibm.CORBA.BootstrapHost=<BootstrapHostname>
    -Dcom.ibm.CORBA.EnableApplicationOLT=true
    -Dcom.ibm.CORBA.OLTApplicationHost=<OLT_Server_Host>
    -Dcom.ibm.CORBA.OLTApplicationPort=<OLT_Server_Port>
    -DOLTClient=true
    -classpath <path\YourAppJarFile>; <path\somojor.zip>; <path\dertrjrt.jar>; %CLASSPATH%
    yourapp

    for the Java 2 platform:

    java -Xdebug -Djava.compiler=NONE
    -Dcom.ibm.CORBA.requestTimeout=0
    -Dcom.ibm.CORBA.BootstrapHost=<BootstrapHostname>
    -Dcom.ibm.CORBA.EnableApplicationOLT=true
    -Dcom.ibm.CORBA.OLTApplicationHost=<OLT_Server_Host>
    -Dcom.ibm.CORBA.OLTApplicationPort=<OLT_Server_Port>
    -DOLTClient=true
    -Xbootclasspath: <path\YourAppJarFile>;<path\somojor.zip>;<path\dertrjrt.jar>; %JAVA_HOME%\lib\tools.jar;%JAVA_HOME%\jre\lib\rt.jar;%CLASSPATH%
    yourapp

    where:
    <BootstrapHostname> = your fully-qualified server application host name (only needed if System Manager is running on a different host)
    <OLT_Server_Host> = the fully-qualified name or TCP/IP address of the machine running your OLT server
    <OLT_Server_Port> = the port where the OLT server listens for connecting OLT clients
    <path\somojor.zip> = x:\CBroker\lib\somojor.zip on Windows NT; /usr/lpp/CBConnector/lib/somojor.zip on AIX; /opt/IBMdebug/lib/dertrjrt.jar on Solaris.
    <path\dertrjrt.jar>
    = x:\IBMDebug\lib\dertrjrt.jar on Windows NT; /usr/idebug/lib/dertrjrt.jar on AIX; /opt/IBMdebug/lib/dertrjrt.jar on Solaris.

  4. A dialog box opens. To run your client application with the default debugger and execution mode settings, click Run. To change the debugger and execution mode settings, click Change settings and do the following on the Client Controller page:
    1. Select the client id that corresponds to the client application you started.
    2. In the Debugger hostname field, enter the host name for the workstation on which you started the debugger daemon. If you changed the default port number for the Debugger Daemon (8001), enter the new port number in the Debugger TCP/IP port field.
    3. Select Trace and debug from the execution mode list. 
    4. Click Apply to apply the monitoring mode change.
    The client application is registered with OLT after you click Run in the dialog box or Apply on the Client Controller page.
  5.  Switch to the OLT View page to start viewing your trace.

In Step-by-step debug mode, OLT stops each time a debuggable method is encountered. OLT then asks whether you want to step into, or over, the method.


Running the debugger from OLT
Starting the OLT server and viewer on separate workstations
Navigating the trace

ngrelc.gif (533 bytes)
How to read the trace


OLT troubleshooting