1.5.2 To Collect Required Debug Data for Directory Editor Installation Problems

This procedure describes what data to collect when you cannot complete Directory Editor installation.

1. Collect the security policy file for your application server.

   For Sun Java System Application Server

   app-server-root/domains/domain-name/config/server.policy

   For Apache Tomcat with Security Manager turned on

   tomcat-root/conf/catalina.policy

2. Collect error logs for your application server.

   For example, if you run Directory Editor in the first domain and instance of Sun Java System Application Server, collect app-server-root/domains/domain1/server1/logs/server.log.

3. Collect Directory Server access, errors, and audit logs.

   Collect logs from both the Directory Editor Configuration Directory Server and also Managed Directory Servers. By default, you find these logs in the following locations:

   server-root/slapd-serverID/logs/access

   server-root/slapd-serverID/logs/errors

   server-root/slapd-serverID/logs/audit (if enabled)

   If these log files are not in the default locations, examine the Directory Server configuration file, server-root/slapd-/serverID/config/dse.ldif, to find the paths to the logs. The paths are specified as the values of attributes nsslapd-accesslog, nsslapd-errorlog, and nsslapd-auditlog.

4. When using Sun Java System Application Server 7 or 8, collect the server description file.

   For example, app-server-root/domains/domain1/server1/config/server.xml.