1.5.1 To Collect Required Debug Data for Any Directory Editor Problem

All problems described in this technical note need basic information collected about when the problem occurred and about the system having the problem. Use this task to collect that basic information.

1. Note the time or times the problem occurred.

2. Note the name of the application server in which you run Directory Editor.

3. Note the exact version of the application server in which you run Directory Editor.

4. Note the exact version of the Java Virtual Machine which you use to run Directory Editor.

5. Note the operating system version.

   Solaris OS

   uname -a

   HP-UX

   uname -r

   Red Hat

   cat /etc/redhat-release

   Windows

   C:\Program Files\Common files\Microsoft Shared\MSInfo\msinfo32.exe /report C:\report.txt

6. Note the patch level.

   Solaris OS

   showrev -p

   HP-UX

   swlist

   Red Hat

   rpm -qa

   Windows

   Already provided in C:\report.txt.

7. Note the Directory Editor version and build number.

   The build number is available only for Directory Editor 1.

   To determine the build number, hover your mouse cursor over the Version string at the top of the Directory Editor page. Either a tooltip appears showing the build number, or the browser displays the build number as a message in the status bar at the bottom of the browser window.

   Alternatively, you can view the source of the Directory Editor web page and search for Build number.

8. Collect Directory Editor configuration files.

   application-root/WEB-INF/classes/init.xml

   application-root/WEB-INF/classes/log4j.properties

   application-root/WEB-INF/startup.properties