Database Reference
In-Depth Information
Administering policy exceptions
In this section, you will learn how to manage and administer policy exceptions.
Monitoring policy exceptions
Critical statistics such as total number of failed requests and number of failures
due to authentication, authorization, or integrity violations for OWSM-based
policies are, fortunately, available. To view a count of these violations to policies
attached to composite artifacts, click on the
Policies
tab from the composite
dashboard. For JAX-RPC or JAX-WS type services bundled inside a Java de-
ployment archive, security violations are available in the
Web Service
dash-
board under
Farm_[Domain_Name]
|
Application Deployments
|
[App]
|
Web
Services
. While there is no additional error log available for the violations, these
statistics are important and should be looked at in the first place, as they give
you an idea that something is wrong with either your security configurations or
with the way the secured services are being invoked. In the next few sections,
you will learn about the various options that allow you to configure OWSM log-
ging coarsely at the infrastructure level, to the most granular level of an individu-
al policy.
Configuring logging for OWSM policies
By default, OWSM policies do not generate any logs in the servers. Though this
should be optimal for a production environment, it is certain that additional log-
ging is needed to debug and troubleshoot security related issues in the infra-
structure. There are several ways to capture this information.
Changing OWSM log configuration
In
Chapter 3
,
Monitoring Oracle SOA Suite 11g
, you learned how overriding the
default log configuration from Oracle Enterprise Manager Fusion Middleware
Control instructs the infrastructure to capture and dump additional logs in the
server log files. The easiest way to enforce logging at the entire infrastructure
