Enabling OLT for Component Broker
Before running Object Level Trace in the Component Broker environment, use
the Component Broker System Manager user interface to configure OLT server
properties, enable remote tracing and debugging, and to change the request
timeout value on both your server and client images.
Before using OLT
on AIX, be sure to modify your .profile, as described in the topic
"Preparing for an OLT session"
If you want the OLT server to listens for connecting OLT clients on a port
number other than the default port (2102), change the port setting on the OLT
server's host:
- If you are running the OLT server and viewer on the same machine, change
the OLT server port as follows:
- In the OLT viewer, select File > Preferences
- Select OLT from the tree in the Browser Preferences
window.
- In the OLT server TCP/IP port field, enter the new
port number.
- Click OK.
- If you are running the OLT server and viewer on separate machines, you
will need to change the OLT_TRC_SRVAPP_PORT entry in the OLT environment
file (dertrenv.dat) on the machine where you are running the OLT server. The
dertrenv.dat file is located in %userprofile%\DbgProf on
Windows NT, and in $HOME/.DbgProf on AIX or Solaris.
If the OLT server is running on a different machine than your client
application or the OLT server uses a port other than 2102, use the System
Manager user interface to change the OLT server properties of the client style:
- In the navigation pane, expand the configuration for the client
application. For example, expand Management Zones > application_zone
> Configurations > application_configuration.
- Expand the Client Styles folder
- From the client style's pop-up menu, select Properties.
- Enter the fully-qualified name or TCP/IP address of the machine running
your OLT server in the OLT hostname field. By default, this
is the name of the host on which the client style is configured.
- Enter the port where the OLT server listens for connecting OLT clients in
the OLT port field. By default, this is 2102.
- Click OK to close the properties editor.
- Activate the configuration that contains the client style to apply your
changes.
To enable remote tracing and debugging:
- In the System Manager user interface, select View > View Level
> Control.
- Expand Host Images > your_host > Server Images.
- Select the server image where your application resides. If the application
server is already running, select Stop > Stop from the
server image's pop-up menu before proceeding to the next step.
- From the pop-up menu, select Properties. A notebook
opens.
- Select the Main tab.
- Check the Enable debug box.
For AIX servers
only, do the following:
- Open the Host images folder and expand the host image
that corresponds to the name of your server. From the pop-up menu,
select Properties. A notebook opens.
- Select the Main tab
- Change the Health monitor polling interval value to 0
(or a value that cannot be easily reached when using the debugger, such
as 300 seconds).
- Click OK to close the host image notebook.
- Select the ORB tab.
- Change the Request timeout value to 0
(or a value that cannot easily be reached when using the debugger, such as
300 seconds).
- Click OK to close the server image notebook.
- If your C++ client application resides on the same host as the
application server, or on a different host with no System Manager user
interface installed, follow these steps:
- Expand Client style images and select the host name
that corresponds to the machine where your client application resides.
- From the client style image's pop-up menu, select Properties.
A notebook opens.
- On the Main tab, check the Enable debug
box.
- Select the ORB tab.
- Change the request timeout value to 0 (or a value
that cannot be easily reached when using the debugger, such as 300
seconds).
- Click OK to close the client image notebook.
If your client application resides on a different host and you
have the System Manager user interface installed on that host, complete
steps a-f on the client machine.
Restart the application server by selecting Run or Run
immediate from the pop-up menu of the server image for your application
server. Monitor the Action Console window for completion status.
Note: If your client-side code includes transaction timeout
values, you must set these values to 0 and recompile before continuing.
You are now ready to trace your application using OLT.
Important: If you
are using Component Broker applications with a different codepage than
workstation OLT will run on, you will need to see the following environment
variable on the workstation where the CB applications is running:
OLT_TRC_SRV_CODEPAGE=codepage of the machine running OLT

Preparing for an OLT session
Tracing a distributed application