Hello There,
Most of us are aware that Access Logs Prints Application Access logs Information as below.
192.168.238.1 - - [01/Mar/2012:15:52:45 +0530] "GET /HelloWorld/welcome.jsp HTTP/1.1" 200 895
192.168.238.1 - - [01/Mar/2012:15:52:46 +0530] "GET /HelloWorld/GoodMorning.jsp HTTP/1.1" 200 2963
Which Specifically uses common logging format, syntax/format of the common logging format is as below.
The Above information is very limited in case if you need to know lot from it, each parameter above are specific to below information.
- host
- RFC931
- Any information returned by IDENTD for the remote client; WebLogic Server does not support user identification
- auth_user
- day/month/year:hour:minute:second UTC_offset
- Day, calendar month, year and time of day (24-hour format) with the hours difference between local time and GMT, enclosed in square brackets
- "request"
- status
- bytes
with the above information the access log is only used for to check whether application is being accessed or not over the server and the time and date of access, finally it will provide the status of the access.
Whereas the Extended Logging Format in WebLogic Server uses the W3C Specifications for the log format, for more information, please refer to http://www.w3.org/TR/WD-logfile.html
According to this logging format we can specify the customized fields for the HTTP Log file as in below link :
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/676400bc-8969-4aa7-851a-9319490a9bbb.mspx?mfr=true
And : http://docs.oracle.com/cd/E13222_01/wls/docs91/config_wls/web_server.html#elf
Follow the below steps to configure the Extended Logging format for HTTP Logs.
Step 1 : Install the WebLogic Server Software, Create a Domain, Start the Admin Server and Deploy a Sample Application to keep everything ready to test the Extended Logging format.
Step 2 : Click on Admin Server and Go to Logging Tab in the console
Step 3 : Click on HTTP to modify the HTTP logging format for the Application Access.
Step 4 : Scroll down and click on Advanced
Step 5 : Change the Format to Extended
Step 6 : And Specify the fields for Extended Logging in "Extended Logging Format Fields" as you would like to see the information from : http://docs.oracle.com/cd/E13222_01/wls/docs91/config_wls/web_server.html#elf
In my example domain I have specified the following fields.
date time cs-method cs-uri sc-status cs-username cs(User-Agent) s-sitename s-ip s-port time-taken cs(Cookie) sc-substatus cs-host cs-version
So as per the above link it will provide us the information for :
s-port: The Port number of the server.
Whereas the Extended Logging Format in WebLogic Server uses the W3C Specifications for the log format, for more information, please refer to http://www.w3.org/TR/WD-logfile.html
According to this logging format we can specify the customized fields for the HTTP Log file as in below link :
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/676400bc-8969-4aa7-851a-9319490a9bbb.mspx?mfr=true
And : http://docs.oracle.com/cd/E13222_01/wls/docs91/config_wls/web_server.html#elf
Follow the below steps to configure the Extended Logging format for HTTP Logs.
Step 1 : Install the WebLogic Server Software, Create a Domain, Start the Admin Server and Deploy a Sample Application to keep everything ready to test the Extended Logging format.
Step 2 : Click on Admin Server and Go to Logging Tab in the console
Step 3 : Click on HTTP to modify the HTTP logging format for the Application Access.
Step 4 : Scroll down and click on Advanced
Step 5 : Change the Format to Extended
Step 6 : And Specify the fields for Extended Logging in "Extended Logging Format Fields" as you would like to see the information from : http://docs.oracle.com/cd/E13222_01/wls/docs91/config_wls/web_server.html#elf
In my example domain I have specified the following fields.
date time cs-method cs-uri sc-status cs-username cs(User-Agent) s-sitename s-ip s-port time-taken cs(Cookie) sc-substatus cs-host cs-version
So as per the above link it will provide us the information for :
date :
Date at which transaction completed, field has type <date>, as defined in the W3C specification.
time
: Time at which transaction completed, field has type <time>, as defined in the W3C specification.
cs-method
:
The request method, for example GET or POST. This field has type <name>, as defined in the W3C specification. cs-uri
:
The full requested URI. This field has type <uri>, as defined in the W3C specification. sc-status
:
Status code of the
response, for example (404) indicating a "File not found" status. This
field has type <integer>, as defined in the W3C specification.
cs-username: The name of the authenticated user who accessed your server. Anonymous users are indicated by a hyphen.
cs(User-Agent) : The browser type that the client used.
s-sitename: The Internet service name and instance number that was running on the client.
s-ip
:
The IP address of the server. time-taken
:
Time taken for transaction to complete in seconds, field has type <fixed>, as defined in the W3C specification.
cs(Cookie)
|
The content of the cookie sent or received, if any.
|
sc-substatus: The substatus error code.
cs-host: The host header name, if any.
cs-version: The protocol version —HTTP or FTP —that the client used.
After this has been specified, save the same and activate the changes.
Step 7: Restart the server to activate the changes.
Step 8 : Access the Application deployed over the server.
Step 9: View the Access logs created
You will find following information sample in your access logs :
#Version: 1.0
#Fields: date time cs-method cs-uri sc-status cs-username cs(User-Agent) s-sitename s-ip s-port time-taken cs(Cookie) sc-substatus cs-host cs-version
#Software: WebLogic
#Start-Date: 2012-03-01 16:02:41
2012-03-01 10:33:22 GET /helloworld/welcome.jsp 200 - "Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2" - 192.168.238.1:7001 - 0.047 "JSESSIONID=QHclPPNTdXyGRJ5QRQFjC97t2PTnVKQTd2tB1hDVSFbf2pJNsw9t!-500938956" - - -
2012-03-01 10:33:24 GET /helloworld/hellothere 200 - "Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2" - 192.168.238.1:7001 - 0.015 "JSESSIONID=wZDZPPQSqFY6n25mgNcZGsF2MmVxT05XQZ0vLnxqCltrJcYjt7nw!-1723970954" - - -
2012-03-01 10:33:25 GET /helloworld/hello.jsp 200 - "Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2" - 192.168.238.1:7001 - 0.031 "JSESSIONID=wZDZPPQSqFY6n25mgNcZGsF2MmVxT05XQZ0vLnxqCltrJcYjt7nw!-1723970954" - - -
#Fields: date time cs-method cs-uri sc-status cs-username cs(User-Agent) s-sitename s-ip s-port time-taken cs(Cookie) sc-substatus cs-host cs-version
#Software: WebLogic
#Start-Date: 2012-03-01 16:02:41
2012-03-01 10:33:22 GET /helloworld/welcome.jsp 200 - "Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2" - 192.168.238.1:7001 - 0.047 "JSESSIONID=QHclPPNTdXyGRJ5QRQFjC97t2PTnVKQTd2tB1hDVSFbf2pJNsw9t!-500938956" - - -
2012-03-01 10:33:24 GET /helloworld/hellothere 200 - "Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2" - 192.168.238.1:7001 - 0.015 "JSESSIONID=wZDZPPQSqFY6n25mgNcZGsF2MmVxT05XQZ0vLnxqCltrJcYjt7nw!-1723970954" - - -
2012-03-01 10:33:25 GET /helloworld/hello.jsp 200 - "Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2" - 192.168.238.1:7001 - 0.031 "JSESSIONID=wZDZPPQSqFY6n25mgNcZGsF2MmVxT05XQZ0vLnxqCltrJcYjt7nw!-1723970954" - - -
Hope this posting was helpful for you.
Please share your feedback.
Regards
Shailesh Dyade