10.02.2013 Views

IBM Tivoli Access Manager for e-business: WebSEAL Administration ...

IBM Tivoli Access Manager for e-business: WebSEAL Administration ...

IBM Tivoli Access Manager for e-business: WebSEAL Administration ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Specifying<br />

the<br />

frequency<br />

<strong>for</strong><br />

flushing<br />

log<br />

file<br />

buffers<br />

Log<br />

files<br />

are<br />

written<br />

to<br />

buffered<br />

data<br />

streams.<br />

If<br />

you<br />

are<br />

monitoring<br />

the<br />

log<br />

files<br />

in<br />

real<br />

time,<br />

you<br />

might<br />

want<br />

to<br />

alter<br />

the<br />

frequency<br />

with<br />

which<br />

the<br />

server<br />

<strong>for</strong>ces<br />

a<br />

flush<br />

of<br />

the<br />

log<br />

file<br />

buffers.<br />

By<br />

default,<br />

log<br />

files<br />

are<br />

flushed<br />

every<br />

20<br />

seconds:<br />

[logging]<br />

flush-time<br />

=<br />

20<br />

If<br />

you<br />

specify<br />

a<br />

negative<br />

value,<br />

a<br />

flush<br />

will<br />

be<br />

<strong>for</strong>ced<br />

after<br />

every<br />

record<br />

is<br />

written.<br />

HTTP<br />

common<br />

log<br />

<strong>for</strong>mat<br />

(<strong>for</strong><br />

request.log)<br />

Every<br />

response<br />

(success<br />

or<br />

failure)<br />

sent<br />

back<br />

by<br />

the<br />

<strong>Tivoli</strong><br />

<strong>Access</strong><br />

<strong>Manager</strong><br />

server<br />

is<br />

recorded<br />

with<br />

a<br />

one-line<br />

entry<br />

in<br />

the<br />

request.log<br />

file<br />

using<br />

following<br />

HTTP<br />

Common<br />

Log<br />

Format:<br />

host<br />

-<br />

authuser<br />

[date]<br />

request<br />

status<br />

bytes<br />

where:<br />

host<br />

Specifies<br />

the<br />

IP<br />

address<br />

of<br />

the<br />

requesting<br />

machine.<br />

authuser<br />

This<br />

field<br />

contains<br />

the<br />

identity<br />

in<strong>for</strong>mation<br />

of<br />

the<br />

user.<br />

The<br />

value<br />

″unauth″<br />

is<br />

used<br />

<strong>for</strong><br />

an<br />

unauthenticated<br />

user.<br />

date<br />

Specifies<br />

the<br />

date<br />

and<br />

time<br />

of<br />

the<br />

request.<br />

request<br />

Specifies<br />

the<br />

first<br />

line<br />

of<br />

the<br />

request<br />

as<br />

it<br />

came<br />

from<br />

the<br />

client.<br />

status<br />

Specifies<br />

the<br />

HTTP<br />

status<br />

code<br />

sent<br />

back<br />

to<br />

the<br />

requesting<br />

machine.<br />

bytes<br />

Specifies<br />

the<br />

number<br />

of<br />

bytes<br />

sent<br />

back<br />

to<br />

the<br />

requesting<br />

machine.<br />

This<br />

value—either<br />

the<br />

unfiltered<br />

content<br />

size<br />

or<br />

a<br />

zero<br />

size—is<br />

configured<br />

with<br />

the<br />

log-filtered-pages<br />

parameter.<br />

Displaying<br />

the<br />

request.log<br />

file<br />

The<br />

request.log<br />

records<br />

standard<br />

logging<br />

of<br />

HTTP<br />

requests,<br />

such<br />

as<br />

in<strong>for</strong>mation<br />

on<br />

URLs<br />

that<br />

have<br />

been<br />

requested<br />

and<br />

in<strong>for</strong>mation<br />

on<br />

the<br />

client<br />

(<strong>for</strong><br />

example,<br />

IP<br />

address)<br />

that<br />

made<br />

the<br />

request.<br />

The<br />

following<br />

example<br />

shows<br />

a<br />

sample<br />

version<br />

of<br />

a<br />

request.log<br />

file:<br />

130.15.1.90<br />

-<br />

Unauth<br />

[09/Oct/2003:<br />

10:12:06<br />

-0700]<br />

"GET<br />

/<br />

HTTP/1.1"<br />

200<br />

1979<br />

130.15.1.90<br />

-<br />

Unauth<br />

[09/Oct/2003:<br />

10:24:11<br />

-0700]<br />

"GET<br />

]jct/cgi-bin/printenv.exe<br />

HTTP/1.1"<br />

200<br />

1979<br />

130.15.1.90<br />

-<br />

Unauth<br />

[09/Oct/2003:<br />

11:07:13<br />

-0700]<br />

"GET<br />

/<br />

HTTP/1.1"<br />

200<br />

1979<br />

130.15.1.90<br />

-<br />

Unauth<br />

[09/Oct/2003:<br />

11:07:18<br />

-0700]<br />

"GET<br />

/pkmslogin.<strong>for</strong>m<br />

HTTP/1.1"<br />

1140<br />

130.15.1.90<br />

-<br />

Unauth<br />

[09/Oct/2003:<br />

11:07:18<br />

-0700]<br />

"GET<br />

/<br />

HTTP/1.1"<br />

200<br />

1052<br />

Displaying<br />

the<br />

agent.log<br />

file<br />

The<br />

agent.log<br />

file<br />

records<br />

the<br />

contents<br />

of<br />

the<br />

User_Agent:<br />

header<br />

in<br />

the<br />

HTTP<br />

request.<br />

This<br />

log<br />

reveals<br />

in<strong>for</strong>mation<br />

about<br />

the<br />

client<br />

browser,<br />

such<br />

as<br />

architecture<br />

or<br />

version<br />

number,<br />

<strong>for</strong><br />

each<br />

request.<br />

The<br />

following<br />

example<br />

shows<br />

a<br />

sample<br />

version<br />

of<br />

a<br />

agent.log<br />

file:<br />

Mozilla/4.01<br />

[en]<br />

(WinNT;<br />

U)<br />

Mozilla/4.01<br />

[en]<br />

(WinNT;<br />

U)<br />

Mozilla/4.01<br />

[en]<br />

(WinNT;<br />

U)<br />

Mozilla/4.01<br />

[en]<br />

(WinNT;<br />

U)<br />

Chapter<br />

4.<br />

Serviceability<br />

and<br />

logging<br />

107

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!