OLT Client Controller
The OLT Client Controller runs on the workstation where your client
application, or servlet, is running. The Client Controller allows you to set the
parameters that tell the OLT runtime where the OLT Server and the IBM
Distributed Debugger are running. For additional help, refer to the HTML or PDF
documentation provided during the user interface install. These files are
installed to your x:\IBMDebug\doc directory.
The Client Controller serves several purposes:
- Before you run your application, the Client Controller displays settings
that define where the OLT Server is
expected to be running and where the Debugger is expected to be started.
- On startup, Client Controller displays the settings from your previous session. You may need to change those setting according to the configuration of your current session.
For the initial startup, Client Controller uses the default settings, which correspond to the scenario where
the OLT Server and Debugger are running on the same machine as the
application you are debugging.
- While your application runs, keep the Client Controller open so that you
can switch "on the fly" among the five monitoring modes. Any
change you make to the monitoring mode takes effect on the next call from
client to application server. If you plan to deploy OLT components across
multiple machines, you must change the Client Controller settings.
Note: If you intend to trace applications running on more than one machine,
you need to open a copy of the Client Controller on each of them.
Help is available for the following Client Controller setting nodes:
Monitoring mode settings
OLT offers five options for monitoring applications. While running an
application, you can switch monitoring modes by selecting a new mode from this page and clicking OK. The new mode takes effect on the next
call to the application server.
- No trace and debug
In this mode, your client application can finish running while you shut down
the trace and debug facilities.
- Trace only (default)
Select this mode to produce a trace, on which you can set method breakpoints
for debugging.
- Debug only
This mode enables you to debug your application without producing a trace.
In this mode, the Debugger stops on every debuggable server call.
- Trace and debug with prompt
This is the mode you will most often use for debugging. If your OLT viewer
is set to Step-by-step debug mode (the default), the execution of the application
being debugged is suspended each time your client application calls a debuggable server method.
You are then prompted to step into or over the server method. Alternatively, you can disable step-by-step debugging,
which will cause the execution of the application being
debugged to suspend only in debuggable server methods on which method breakpoints have been set. To
disable step-by-step debugging deselect Options > Step-by-step debug
from the Viewer menu, or deselect the Step-by-step debug option in the Breakpoints dialog box.
- Trace and debug without prompt
In this mode, a trace is created, and the Debugger steps into every
debuggable server object method without first prompting you.
OLT server settings
The settings on this page indicate the location of the OLT server. If you
change these values while the client application is running, the changes take
effect the next time you start the application.
- Host name
The host name of the machine where the OLT server is running (the default is
the host name of the current workstation). If your OLT server is not running
on the same machine as the client application, you must change this host
name value to point to the machine where the OLT server is running.
- TCP/IP port
The port where the OLT server is listening (the default port is 2102). You
need only change this value if port 2102 is already in use and the OLT server is listening to a different port. This is more
common in a multi-user environment like AIX.
- Collect real-time information
This option tells the OLT server to collect real-time information, which
gives you the option of switching later to a real-time display mode in the
viewer. If you are running multiple client applications, you should select
the same real-time option for each.
OLT Client Controller settings
This setting indicates the TCP/IP port from which all clients receive the
values that are set by the Client Controller. You would typically change this
port number only if there was a conflict.
Remote Debugger settings
The settings on this page indicate where the Debugger is to open.
- In the OLT viewer, select File > Preferences > OLT >
OLT Client Controller Settings > Remote Debugger
- Enter the host name and TCP/IP port for the workstation on which you
intend to run the Debugger daemon.
- Click OK to apply the change.
- If the machine where you intend to run the Debugger is different from the machine where the OLT Viewer is
running, start the Debugger daemon manually on the machine where you want the
Debugger to open.
If your application will be running on a different machine than OLT and
the Debugger daemon, you must start the OLT Client Controller on that
workstation prior to running your client application, and you
must modify the host name value in the Remote Debugger settings to point
to the workstation on which you manually started the Debugger daemon.
- TCP/IP port
The port where the Debugger daemon is listening (the default port is
8001). You need to change this value only if the port 8001 is already in use.
This is more common in a multiuser environment like AIX. Note that Port 8002 is reserved for use by the
Debugger user interface.
If you change the values on this page while the client application is
running, the changes take effect the next time you start the application.
Appearance settings
Use this page to define the overall appearance of the Client Controller. You
can select from three different texture and color schemes:
- Metal (default)
- CDE/Motif
- Windows
Help settings
Use this page to select the browser used to display online help files.
- Help browser
Select the Web browser you want to use.
- Browser location
Select the location of the browser executable file.
On NT, it should be
sufficient to specify the name of the executable, such as netscape.exe.
However, if you cannot access the help, you may need to
explicitly enter the browser location.

On
AIX and Solaris, you must select the browser
path before having access to online help.
- Open help in a separate browser window
Click this option to have a separate Web browser session dedicated to help
information. Otherwise, help will open in the current Web browser session,
if one is already running.