This chapter describes how to troubleshoot problems encountered while using Oracle Communications Delegated Administrator.
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.
The Delegated Administrator is a multi-client and server environment. A fully deployed environment has dependencies on LDAP, two web containers, a server, two clients, and possibly Access Manager.
Thus, a problem description contains three critical elements:
A basic description of the problem
Version information
The answer to the question, "Does the problem happen when you use commadmin, Delegated Administration Console (web client), or both?"
Collecting this information helps to minimize problem resolution time.
To debug the Delegated Administrator utility (commadmin), you can print debug messages in the client by using the -v option with the commadmin command.
This feature is interactive, you can enable it at any time, with any full (object + task) usage.
If you are unable to solve the problem by using the verbose output, consider expanding your analysis to include the Delegated Administration Server. Refer to the debugging features described later in this information.
If you are submitting a problem to Oracle Technical Support, save both normal and verbose output.
By default, Delegated Administrator Console logging is off.
The Delegated Administrator console creates a run-time log file:
Default log file name: da.log
Default location: DelegatedAdmin_home/log/
You can specify your own log file by editing a log properties file named logger.properties.
To specify your own Delegated Administrator Console log file:
Open the logger.properties file in a text editor.
The logger.properties file is located by default in the following directory:DelegatedAdmin_home/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.
See "Deploying a Customized Configuration File" for instructions on how to deploy a customized properties file to a particular Web container.
You can create a Delegated Administrator Server log that contains error messages generated by the Delegated Administrator Server's servlets installed on the web container.
To do so, you enable a Debug servlet to log debug messages from the Delegated Administrator Server's servlets execution.
You use the commadmin debug log command to enable Delegated Administrator Server to write messages to a debug log. See "commadmin debug log" for additional information.
For example, enter the following command:
commadmin debug log -D paul -n sesta.com -t on
In the preceding command, Paul is the Top Level Administrator. The command would log Debug servlet messages to the default path and file:
/tmp/commcli.log
Note:
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 troubleshoot Delegated Administrator by examining the server logs generated by your Web container.
Table 9-1 Web Container Server Logs
| Web Container | Container Description | File Path | File Path Variable Description |
|---|---|---|---|
|
Web Server 6.x |
Maintains access and error logs |
web_server6_base/https-host.domain/logs |
web_server6_base is the base where Web Server 6.x software is installed. For example: /opt/SUNWwebsvr. 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 |
web_server7_config_base/https-host.domain/logs |
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 |
/application_server7_base/domains/domain1/server1/logs |
application_server7_base is the path where Application Server 7.x software is installed. |
|
Application Server 8.x |
Maintains access and error logs |
Server log: /application_server8_base/domains/domain1/logs Access log: /application_server8_base/domains/domain1/logs/access/server_access_log |
application_server8_base is the path where Application Server 8.x software is installed. |
|
Application Server 9.0 |
Maintains access and error logs For more information, see About Logging. |
Server log: /application_server9_base/domains/domain1/logs Access log: /application_server9_base/domains/domain1/logs/acces/server_access_log |
application_server9_base is the path where Application Server 9.x software is installed. |
You can debug Delegated Administrator 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 hostname is the name of the machine where Directory Server is running.
For more information on Directory Server logs, see the documentation about Directory Server Enterprise Edition 6.3
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.