Configuring tracing for the local management interface

Edit online

Use the LMI Tracing page to configure the tracing specifications for different components of the local management interface.

About this task

You can now set the tracing specifications of the local management interface for debugging purposes.
Note:
  • Changing these tracing specifications might have an adverse effect on the performance of the local management interface.
  • Setting trace for Oracle components “oracle.*” results in the underlying Oracle JDBC jar file being changed to a debugging jar file. This might have adverse effects on performance and as such Oracle tracing should only be enabled for debugging purposes and disabled once complete.
Warning: Enabling trace for Oracle components “oracle.*” might result in the Oracle database administrator password being logged in clear text.

Procedure

  1. Select System > System Settings > Administrator Settings.
  2. Click LMI Tracing.
    The LMI tracing components and trace levels are displayed.
    Table 1. LMI tracing components
    Component Description
    com.ibm.isam.* This option enables tracing for the components of all offerings, which include the Security Verify Identity Access Base, Advanced Access Control, and Federation offerings.
    com.ibm.isam.core.* This option enables tracing for the common components of all offerings. These common components are shared by the various offerings. For example, the Verify Identity Access runtime and SSL certificates management.
    com.ibm.isam.wga.* This option enables tracing for the components of the Verify Identity Access Base offering. For example, the management of reverse proxy instances.
    com.ibm.isam.mga.* This option enables tracing for the components of the Verify Identity Access Advanced Access Control and Federation offerings. For example, the risk based analysis (RBA) configuration, the management of federations, partners, and module chains.
    com.ibm.mesa.* This option enables tracing for the underlying components that compose the LMI framework. These components are used both as a base for all of the offerings and to provide the management of most system settings. For example, updates and network configuration.
    HTTP This option enables tracing for the components of the web application server that are involved in HTTP communication.
    SSL This option enables tracing for the components of the web application server that are involved in SSL communication.
    JSP This option enables tracing for the JavaServer pages components of the web application server.
    Servlet Engine This option enables tracing for the servlet engine and web container components of the web application server.
    Session Management This option enables tracing for the components of the web application server that make up the session and session management functionality.
    Configuration This option enables tracing for the configuration of the web application server.
    Native Security This option enables tracing for the native security components of the web application server.
    Table 2. LMI trace levels
    Level Description
    all All events are logged. If you create custom levels, all includes those levels, and can provide a more detailed trace than finest.
    finest A more detailed trace that includes all the detail that is needed to debug problems.
    finer Detailed trace information.
    fine Trace information that includes general trace, method entry, exit, and return values.
    detail General information that details the subtask progress.
    config Configuration change or status.
    info General information that outlines the overall task progress.
    audit Significant event that affects the server state or resources.
    warning Potential error or impending error. This level can also indicate a progressive failure, for example, the potential leaking of resources.
    severe Task cannot continue. But component, application, and server can still function. This level can also indicate an impending unrecoverable error.
    fatal Task cannot continue. Component, application, and server cannot function.
    off Logging is turned off.
  3. Define the trace specifications in either of the following methods.
    • Select a component and trace level from the table, and then click the Add. Repeat this procedure until all trace specifications are added.
    • Manually enter the trace specifications in the Trace Specification text area.
  4. Click Save.
  5. Deploy the changes.
    Note: The local management interface is automatically restarted so that the changes can take effect.