You can obtain log information for Delegated Administrator by examining log files generated by the Delegated Administrator components, by the Web container to which Delegated Administrator has been deployed, and by Directory Server and Access Manager.
This appendix includes the following topics:
To debug the Delegated Administrator utility (commadmin), you can print debug messages in the client by using the -v option with the commadmin command.
The Delegated Administrator console creates a runtime log file:
Default log file name: da.log
Default location: /opt/SUNWcomm/log
You can specify your own log file by editing a log properties file named logger.properties.
Open the logger.properties file in a text editor.
The logger.properties file is located by default in the following directory:
da-base/data/da/WEB-INF/classes/com/sun/comm/da/resources
You can change the following properties in the logger.properties file:
da.logging.enable=yes or no
where yes enables logging and no disables logging.
By default, logging is disabled. To turn on logging, you must set this value to yes.
da.log.file=full pathname
specifies the directory and file to which logging statements are written. This property changes da.log to a file name and location you specify.
Redeploy the edited logger.properties file to the Web container used by the Delegated Administrator console.
Before the change can take effect, you must run the script that deploys the customized logger.properties file to your Web container.
For instructions on how to deploy a customized properties file to a particular Web container, see To Deploy a Customized Configuration File.
You can create a Delegated Administrator server log that contains debug statements generated by the Delegated Administrator servlets installed on the Web container.
To do so, you enable a Debug servlet to log debug messages from the Delegated Administrator servlet execution.
You use the commadmin debug log command to write Delegated Administrator server messages to a debug log.
The -f option specifies the full path and file name of the log.
The -t option allows you to toggle between writing debug messages to the log and turning off the debug logging.
For example, enter the following command:
commadmin debug log -D paul -n sesta.com -w bolton \ -t on -f /tmp/debug.log |
The preceding command would log Debug servlet messages to the following path and file:
/tmp/debug.log
The log can only be created in the /tmp/ or /var/tmp/ directory.
Whenever you restart the Web container, you must run the commadmin debug log command again.
You can debug Delegated Administrator further by examining the server logs generated by your Web container.
Web Server 6.x maintains access and error logs, located in the following path:
web_server6_base/https-host.domain/logs
where
web_server6_base is the path where Web Server 6.x software is installed. For example: /opt/SUNWwbsvr.
host.domain is the host and domain name of the machine where Web Server 6.x is running.
Web Server 7.x maintains access and error logs, located in the following path:
web_server7_config_base/https-host.domain/logs
where
web_server7_config_base is the path where Web Server 7.x configuration and log files are installed. For example: /var/opt/SUNWwbsvr7.
host.domain is the host and domain name of the machine where Web Server 7.x is running.
Application Server 7.x maintains access and error logs, located in the following path:
/application_server7_base/domains/domain1/server1/logs
where
application_server7_base is the path where Application Server 7.x software is installed.
Application Server 8.x maintains access and error logs, located in the following paths.
Server log:
/application_server8_base/domains/domain1/logs
Access log:
/application_server8_base/domains/domain1/logs/access/server_access_log
where
application_server8_base is the path where Application Server 8.x software is installed.
You can debug Delegated Administrator further by examining the logs generated by Directory Server and Access Manager.
Directory Server maintains access and error logs, located in the following path:
/var/opt/mps/serverroot/slapd-hostname/logs
where
hostnameis the name of the machine where Directory Server is running.
Access Manager maintains log files in the following paths:
/var/opt/SUNWam/debug
The preceding path contains the amProfile and amAuth logs.
/var/opt/SUNWam/logs
The preceding path contains the amAdmin.access and amAdmin.error logs.