Sun Gathering Debug Data for Sun Java System Directory Editor 1

Procedure1.5.5 To Collect Required Debug Data for Directory Editor Graphical User Interface Problems

This section describes what data to collect when part of the Directory Editor user interface fails to comply with what you expect.

  1. Collect screen shots of the affected screen or screens.

    The screen shots should show the problem you are experiencing.

  2. Provide step by step instructions for reproducing the problem.

    If needed, also provide test case data.

  3. Provide the browser name, version number, and operating system where you run the browser to access Directory Editor.

  4. Provide information about the user who was logged in when the problem occurred.

  5. Collect trace logging information showing view and web activity.

    To collect this information, perform the following steps.

    1. Open the app-server-root/WEB-INF/classes/ file in a text editor.

    2. Add the following lines.,view,web
      log4j.appender.view.layout.ConversionPattern=%d{ISO8601} [%t] %-5p %c - %m%n
      log4j.appender.web.layout.ConversionPattern=%d{ISO8601} [%t] %-5p %c - %m%n
    3. Restart Directory Editor.

    4. Reproduce the login problem immediately.

    5. Collect the log files named de-view.log and de-web.log.

  6. Collect screen shots of Directory Editor debugging screens.

    Access the following Directory Editor URL, http://hostname:port/de/

    Take screen shots of the following five tab pages:

    • HTTP Session

    • Directory Properties

    • Java System Properties

    • Memory

    • Call Timer