As well as tinkering with the sawserver (Presentation Services) logging level and format, we can specific which bits of the log we’re interested in. This is useful for two reasons:
- We can enable detailed logging for a specific area, without impacting performance as much as detailed logging throughout would cause
- By only logging in detail the area of interest we can more easily read the log output and not have to wade through pages of irrelevant information
Chapter 9 (“Using the Oracle BI Presentation Services Logging Facility”) of the Presentation Services Administration Guide details the log configuration.
To capture, for example, only inbound and outbound HTTP logs, you would amend your logconfig.xml to include this in the
If you want to write the information to a separate file, define a new Writer:
[...]
[...]
(use an unused writerClassId) and WriterClassGroup:
[...]
7
[...]
and use the newly defined WriterClassGroup in the Filter:
All of the odbc logging will now be written to a file in /tmp called sawodbc0.log.
To get a list of all possible path values, run sawserver with the -logsources commandline option
$ . ./common.sh
$ . ./sa-init.sh
$ sawserver -logsources
saw
saw.SOAP
saw.SOAP.JobManagementService
saw.answers
saw.answers.search
saw.authconfigmanager
saw.authconfigmanager.initialize
saw.cacheseeding
saw.catalog
saw.catalog.archive
saw.catalog.archive.merge
saw.catalog.archive.read
saw.catalog.archive.write
saw.catalog.archive.write.singleobject
saw.catalog.file
saw.catalog.filelock
saw.catalog.impl
saw.catalog.impl.cleanup
saw.catalog.impl.explainPermissions
[...etc etc...]