You can access the Log Level and Message configuration screen
by clicking the Next button on the main screen of all filters.
This screen includes the following fields:
Log Level:
Configure one of the following options:
Use Service Level Settings
|
This option is selected by default. Logging is configured for
the Web Service with logging level of Failure.
|
Override Logging Level for this Filter
|
Alternatively, select this option to configure log messages for this
filter when it succeeds, fails, and/or aborts. Select Success,
Failure, and/or Fatal to configure this
filter to log at the respective levels.
|
Log Messages:
Default log message values are provided at each level for all filters. When
you select the checkbox for a particular level, the default log message for
that level is used. You can specify an alternative log message by entering
the message in the text field provided.
All filters require and generate
message attributes, while some consume attributes.
In some cases, it may be useful to log the value of these attributes.
For example, instead of an authentication filter logging a generic
Authentication Failed message, you can use the value of the
authentication.subject.id attribute to log the ID
of the user that could not be authenticated.
Use the following format to enter a message attribute as a property in a
log message:
At runtime, the Enterprise Gateway expands these properties to the value of the
message attribute. For example, to make sure the ID of a non-authenticated
user is logged in the message, enter something like the following in the
text field for the Failure case:
| | |
|
The user '${authentication.subject.id}' could not be authenticated.
| |
| | |
|
Then if a user with ID oracle can not be authenticated
by the Enterprise Gateway (a failure case), the following message is logged:
| | |
|
The user 'oracle' could not be authenticated.
| |
| | |
|
Audit Logging Behavior:
This setting is relevant only in cases where you have configured the
Enterprise Gateway to log audit trail messages to a database. For more details,
see the instructions in the
Logging Configuration topic.
You can select the Abort circuit processing on database log error
checkbox if you have configured the Enterprise Gateway to write log messages to a database,
but that database is not available at runtime. If you have selected this checkbox,
and the database is not available, the filter aborts, which in turn causes the
circuit to abort. In this case, the Fault Handler for the circuit is invoked.
Filter Category:
The category selected here identifies the category of filters to which this filter
belongs. The default selection should be appropriate in most cases.
|