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.

This<br />

parameter<br />

determines<br />

the<br />

cut-off<br />

point<br />

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

servicing<br />

requests<br />

across<br />

a<br />

junction.<br />

When<br />

the<br />

worker-thread-hard-limit<br />

is<br />

exceeded,<br />

error<br />

messages<br />

are<br />

sent<br />

(every<br />

30<br />

seconds)<br />

to<br />

the<br />

<strong>WebSEAL</strong><br />

error<br />

log<br />

file.<br />

In<br />

addition,<br />

the<br />

user<br />

is<br />

sent<br />

a<br />

503<br />

″Service<br />

Unavailable″<br />

message.<br />

For<br />

example,<br />

when<br />

worker-threads<br />

=<br />

50,<br />

a<br />

setting<br />

of<br />

80<br />

(%)<br />

causes<br />

error<br />

messages<br />

to<br />

be<br />

issued<br />

when<br />

the<br />

junction<br />

tries<br />

to<br />

consume<br />

more<br />

than<br />

40<br />

worker<br />

threads.<br />

All<br />

requests<br />

representing<br />

greater<br />

than<br />

40<br />

worker<br />

threads<br />

on<br />

the<br />

junction<br />

are<br />

returned<br />

with<br />

a<br />

503<br />

″Service<br />

Unavailable″<br />

message.<br />

The<br />

default<br />

value<br />

of<br />

100<br />

(%)<br />

indicates<br />

there<br />

is<br />

no<br />

limit.<br />

These<br />

global<br />

settings<br />

apply<br />

equally<br />

to<br />

all<br />

configured<br />

junctions.<br />

When<br />

configuring<br />

these<br />

two<br />

parameters,<br />

it<br />

is<br />

logical<br />

to<br />

set<br />

the<br />

″soft″<br />

limit<br />

to<br />

a<br />

lower<br />

value<br />

than<br />

the<br />

″hard″<br />

limit.<br />

Per-junction<br />

allocation<br />

of<br />

worker<br />

threads<br />

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

junctions<br />

Alternatively,<br />

you<br />

can<br />

limit<br />

worker<br />

thread<br />

consumption<br />

on<br />

a<br />

per-junction<br />

basis.<br />

The<br />

following<br />

options<br />

to<br />

the<br />

pdadmin<br />

server<br />

task<br />

create<br />

command<br />

allow<br />

you<br />

to<br />

specify<br />

hard<br />

and<br />

soft<br />

worker<br />

thread<br />

limits<br />

on<br />

a<br />

specific<br />

junction:<br />

v<br />

–l<br />

percent_value<br />

This<br />

option<br />

sets<br />

a<br />

value<br />

(percent)<br />

on<br />

the<br />

junction<br />

that<br />

defines<br />

the<br />

soft<br />

limit<br />

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

consumption<br />

of<br />

worker<br />

threads.<br />

As<br />

in<br />

the<br />

global<br />

soft<br />

limit<br />

setting,<br />

this<br />

option<br />

causes<br />

warning<br />

messages<br />

to<br />

be<br />

issued<br />

when<br />

the<br />

junction<br />

consumes<br />

more<br />

worker<br />

threads<br />

than<br />

allowed<br />

by<br />

the<br />

setting.<br />

v<br />

–L<br />

percent_value<br />

This<br />

option<br />

sets<br />

a<br />

value<br />

(percent)<br />

on<br />

the<br />

junction<br />

that<br />

defines<br />

the<br />

hard<br />

limit<br />

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

consumption<br />

of<br />

worker<br />

threads.<br />

As<br />

in<br />

the<br />

global<br />

hard<br />

limit<br />

setting,<br />

this<br />

option<br />

causes<br />

warning<br />

messages<br />

to<br />

be<br />

issued<br />

when<br />

the<br />

junction<br />

tries<br />

to<br />

consume<br />

more<br />

worker<br />

threads<br />

than<br />

allowed<br />

by<br />

the<br />

setting.<br />

In<br />

addition,<br />

the<br />

user<br />

is<br />

sent<br />

a<br />

503<br />

″Service<br />

Unavailable″<br />

message.<br />

For<br />

example:<br />

pdadmin><br />

server<br />

task<br />

webseald-<br />

create<br />

-t<br />

tcp<br />

-h<br />

<br />

\<br />

-l<br />

60<br />

-L<br />

80<br />

<br />

Per-junction<br />

settings<br />

always<br />

override<br />

the<br />

global<br />

settings<br />

in<br />

the<br />

<strong>WebSEAL</strong><br />

configuration<br />

file.<br />

Ensure<br />

that<br />

the<br />

settings<br />

on<br />

a<br />

specific<br />

junction<br />

do<br />

not<br />

adversely<br />

affect<br />

the<br />

policy<br />

established<br />

by<br />

the<br />

global<br />

settings.<br />

Troubleshooting<br />

notes<br />

v<br />

You<br />

can<br />

use<br />

the<br />

pdadmin<br />

server<br />

task<br />

show<br />

command<br />

to<br />

view<br />

the<br />

number<br />

of<br />

active<br />

worker<br />

threads<br />

on<br />

a<br />

specific<br />

junction:<br />

pdadmin><br />

server<br />

task<br />

webseald-<br />

show<br />

/<br />

This<br />

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

might<br />

be<br />

useful<br />

when<br />

you<br />

want<br />

to<br />

determine<br />

the<br />

location<br />

of<br />

a<br />

junction<br />

that<br />

is<br />

absorbing<br />

more<br />

than<br />

its<br />

share<br />

of<br />

worker<br />

thread<br />

resources.<br />

v<br />

If<br />

you<br />

specify<br />

a<br />

soft<br />

limit<br />

value<br />

that<br />

is<br />

greater<br />

than<br />

the<br />

hard<br />

limit<br />

value<br />

on<br />

a<br />

specific<br />

junction,<br />

the<br />

junction<br />

will<br />

not<br />

be<br />

created.<br />

v<br />

You<br />

must<br />

specify<br />

both<br />

soft<br />

and<br />

hard<br />

limit<br />

values<br />

(both<br />

–l<br />

and<br />

–L<br />

options)<br />

on<br />

a<br />

specific<br />

junction.<br />

Chapter<br />

2.<br />

<strong>WebSEAL</strong><br />

server<br />

configuration<br />

43

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

Saved successfully!

Ooh no, something went wrong!