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 Preparing for an OLT
session.
For
Component Broker, AIX, or Solaris servers only. In the System Manager, change the Health
monitor polling interval value to 0 on the host image that corresponds to the name of your
server. You must start the System Manager user interface with the -repair option, then do
the following:
If you want the OLT server to listens for connecting OLT Runtimes on a port number other than the default port (2102), change the port setting on the OLT server's host:
If the OLT server is running on a different machine than your managed C++ client application or the OLT server uses a port other than 2102, use the Component Broker System Manager user interface to change the OLT server properties of the client style:
To enable remote tracing and debugging:
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: For Component Broker C++ clients, 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 set the following environment variable on the workstation where the CB
applications is running:
OLT_TRC_SRV_CODEPAGE=codepage of the machine running OLT
Component Broker Non-managed VisualAge C++ and ActiveX
clients
To run a VisualAge C++ or ActiveX client using Object Level Trace and the Distributed
Debugger on a host that does not have access to Component Broker's System Management user
interface, you can optionally use a client style properties file to provide the necessary
properties and arguments. At run time, the client application would get the arguments from
this properties file instead of getting them from the System Manager user interface. To
use the client style properties file, ensure that the environment variable SOMCBPROPS is
set to the name of this file. To run non-managed C++ clients against OLT, the following
values in the client style properties file must be set as follows:
com.ibm.CORBA.debugEnabled=yes com.ibm.CORBA.oltHostname=manji.torolab.ibm.com com.ibm.CORBA.oltPort=2102 com.ibm.CORBA.requestTimeout=0
To get more information on other properties that can be found and used in a client style properties file, please consult the Component Broker's client style documentation.
Preparing for an OLT and IBM Distributed Debugger session
Tracing a distributed application