Configuring Logging For A Proxy Service; Section 4.3, "Configuring Logging For A Proxy Service - Novell ACCESS MANAGER 3.1 SP2 - ACCESS GATEWAY GUIDE 2010 Manual

2 On the Log Profiles page, click New, specify a name for the profile such as
click OK.
3 Specify a name for the log file, such as
4 In the Filter List section, click Manage Filters.
5 Click New, specify a name for the filter such as
6 Expand the Advanced Log Level Options section.
7 Select Form Fill Processing, then click the expand/collapse icon on the left.
8 To view the events you have selected, expand the Error, Info, and Debug options.
Notice that the selected events allow you to determine if the Access Gateway found a page that
matches the Form Fill policy and whether the policy was evaluated without errors.
9 Select Web Server Communication, then click the expand/collapse icon on the left.
10 Expand the info level of events, then make sure that the Web Server Request with Form Fill
Parameters event is select and that the Web Server Request With Identity Injection Parameters
event is deselected.
11 Click OK.
12 Select the profile, click Enable, then click OK.
13 Click the Access Gateways link, then update the Access Gateway.
14 Log in as a user and access a resource that has been assigned a Form Fill policy.
15 View the entries in log file.
Linux:
/var/opt/novell/amlogging/logs
Windows:
\Program Files\Novell\amlogging\logs
16 (Optional) To view how the Embedded Service Provider evaluates the Form Fill policy, see
"Form Fill Traces" in the
17 (Optional) To add more information about Form Fill policies to the Apache
enable the DebugFormFill option. For more information, see
Gateway Service Options," on page

4.3 Configuring Logging for a Proxy Service

Logging HTTP transactions has associated costs. The Access Gateway is capable of handling
thousands of transactions per second. If transaction volume is high and each log entry consumes a
few hundred bytes, the Access Gateway can fill up the available disk space in a matter of minutes.
HTTP logging also increases system overhead, which causes some degradation in performance. By
default, the logging of HTTP transactions is turned off. Before enabling logging, you need to
determine what needs to be logged and then plan a logging strategy.
Section 4.3.1, "Determining Logging Requirements," on page 132
Section 4.3.2, "Calculating Rollover Requirements," on page 132
Section 4.3.3, "Enabling Logging," on page 135
Section 4.3.4, "Configuring Common Log Options," on page 135
Section 4.3.5, "Configuring Extended Log Options," on page 137
Section 4.3.6, "Configuring the Size of the Log Partition," on page 140
.
formfill
Form Fill Filter
Novell Access Manager 3.1 SP2 Policy
180.
Form Fill
, then click OK.
Guide.
error_log
Section 5.7, "Advanced Access
Access Gateway Maintenance 131
, then
file,