OLT Client Controller
The OLT Client Controller runs on the workstation where your client application, or
servlet, is running. The Client Controller enables the setting of parameters that tell the
trace components where the client application and the 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 two purposes:
- Before you run your application, the Client Controller determines where the OLT Server
is running and where the debugger should be started. The Client Controller assumes, by
default, that you are running all OLT components on one machine. If you plan to deploy OLT
components across multiple machines, you must change the Client Controller settings.
- 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.
Note: If you are running applications on more than one machine, open a
copy of the Client Controller on each.
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 debugger opens each time your client application
calls a debuggable server method. You are then prompted to step into or over the code.
Alternatively, you can 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. 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
OLT Debugger Daemon.
- Click OK to apply the change.
- Start the OLT 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 OLT Debugger Daemon is listening (the default port is 8001). You
need only change this value if the port 8001 is already in use. This is more common in a
multi-user environment like AIX.
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.
HTML 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. This should be correct by default on
NT, but if you cannot access help then you may need to explicitly enter the browser
location. On AIX, 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.
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