You can customize the format of the default HTTP access log.
By default, WebLogic Server keeps a log of all HTTP transactions in a text file. The file is named access.log and is located in the $DOMAIN_HOME/servers/AdminServer/logs directory.
The log provides true timing information from WebLogic, in terms of how long each individual Endeca Server request takes. This timing information can be important in troubleshooting a slow system.
Note that this setup needs to be done on a per-server basis. That is, in a clustered environment, this has to be done for the Admin Server and for every Managed Server. This is because the clone operation (done when installing a clustered environment) carries over SSL configuration, but does not carry over access log configuration.
To customize the HTTP access log:
date time time-taken cs-method cs-uri sc-status
#Version: 1.0 #Fields: date time time-taken cs-method cs-uri sc-status #Software: WebLogic #Start-Date: 2013-10-22 15:23:40 2013-10-22 15:27:07 0.967 POST /endeca-server/ws/manage 200 2013-10-22 15:27:32 7.301 POST /endeca-server/es/control 200 2013-10-22 15:27:32 7.567 POST /endeca-server/ws/manage 200 2013-10-22 16:23:35 0.219 GET /endeca-server/ws/conversation/sh?wsdl 200 2013-10-22 16:23:35 0.0 GET /favicon.ico 404 2013-10-22 16:24:14 0.031 GET /endeca-server/ws/conversation/sh?wsdl 200 2013-10-22 16:24:14 0.031 GET /endeca-server/ws/conversation/sh?XSD=lql_parser_types.xsd 200 2013-10-22 16:27:15 5.692 POST /endeca-server/ws/conversation/sh 200 2013-10-22 16:27:50 0.624 POST /endeca-server/ws/conversation/sh 200
Note that all the queries were successful (status code of 200), except for the one with the 404 status code.