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.

ngaix.gif (991 bytes)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:

  1. Select Host Images > yourhostname, and right-click it.
  2. Select Properties from the pop-up menu.
  3. Select the Main tab, and change the Health monitor polling interval to zero.

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:

  1. In the navigation pane, expand the configuration for the client application. For example, expand Management Zones > application_zone > Configurations > application_configuration.
  2. Expand the Client Styles folder
  3. From the client style's pop-up menu, select Properties.
  4. 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.
  5. Enter the port where the OLT server listens for connecting OLT clients in the OLT port field. By default, this is 2102.
  6. Click OK to close the properties editor.
  7. Activate the configuration that contains the client style to apply your changes.

To enable remote tracing and debugging:

  1. In the System Manager user interface, select View > View Level > Control.
  2. Expand Host Images > your_host > Server Images.
  3. 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.
  4. From the pop-up menu, select Properties. A notebook opens.
  5. Select the Main tab.
  6. Check the Enable debug box.
  7. ngaix.gif (991 bytes)For AIX servers only, do the following:
    1. 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.
    2. Select the Main tab
    3. 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).
    4. Click OK to close the host image notebook.
  8. Select the ORB tab.
  9. Change the Request timeout value to 0 (or a value that cannot easily be reached when using the debugger, such as 300 seconds).
  10. Click OK to close the server image notebook.
  11. If your managed 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:
    1. Expand Client style images and select the host name that corresponds to the machine where your client application resides.
    2. From the client style image's pop-up menu, select Properties. A notebook opens.
    3. On the Main tab, check the Enable debug box.
    4. Select the ORB tab.
    5. Change the request timeout value to 0 (or a value that cannot be easily reached when using the debugger, such as 300 seconds).
    6. 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: 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.

ngrelt.gif (466 bytes)
Preparing for an OLT and IBM Distributed Debugger session
Tracing a distributed application