Tracing and Diagnostics 12-11
These sections on the servlet logging tools contain the following:
■
Section 12.6.1, Enabling Oracle Diagnostics and Logging
■
Section 12.6.4, Location of Log Files
■
Section 12.6.5, Example Output for Each Level of Servlet Logging
12.6.1 Enabling Oracle Diagnostics and Logging
When you turn on logging, the Listener Servlet writes log messages to the servlet log file. Examples of output for the various levels of logging are in
Section 12.6.5, Example Output for Each Level of Servlet Logging
. Table 12–8
describes the supported logging capabilities. If no string is appended to serverURL, then default logging is supported. To start other loggers, they must be
specified in serverURL as described in the next section.
12.6.1.1 Specifying Logging
To specify logging for all users, change the serverURL entry in the default section in the Web Configuration page to the following:
serverURL=formslservletstring where string specifies the logging capability as defined in
Table 12–8 . If no string is
provided, the default logging For example, if you want to start session-level logging, modify the serverURL as follows:
serverURL=formslservletsession
12.6.1.2 Specifying Logging Levels Using Fusion Middleware Control
To set the log levels for Forms servlet logging using Fusion Middleware Control, perform the following:
1.
From the Fusion Middleware Control, select the managed server for example WLS_FORMS.
Table 12–8 Supported logging capabilities
String appended to serverURL
client parameter
Description of logging
none During Forms servlet initialization, a message is written to the log file
stating the name and path of the configuration file being used. Messages of levels higher and equal to the log level set for the default
logger in logging.xml are logged. Default Value is set to NOTIFICATION:1 and levels NOTIFICATION:1, WARNING:1,
ERROR:1 and INTERNAL_ERROR are logged.
session Log messages are written whenever a Forms session starts or ends.
These give the host name and IP address of the client the computer on which the users Web browser is running, the runtime process id, and
a unique internal session id number.
sessionperf Performance summary statistics are included with the session end
message. perf
A performance message is written for every request from the client. debug
Full debug messages. Other debug messages are written in addition to the messages mentioned above. This logging level is verbose and is
intended mainly for debugging and support purposes.
12-12 Forms Services Deployment Guide
2.
From the WebLogic Server menu, select Logs, then Log Configuration.
3.
In the Logger Name field, expand Root Logger. Expand each of the following: oracle, oracle.forms. The Logger name defined in serverURL as described in
Section 12.6.1.1, Specifying Logging is displayed, for example
oracle.forms.servlet.debug.
4.
Choose the Log level as required from the list in the Oracle Diagnostic Logging Level field. Refer to
Table 12–9 for the mapping of the internal Forms log level to
the Java levels.
This configuration modifies the logging.xml file for the managed server.
12.6.1.3 Specifying Full Diagnostics in the URL that Invokes the Forms Servlet
