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

A
″state″
established
between
a
client
and
back-end
server
2,
via
WebSEAL
server
1
will
fail
if
a
subsequent
request
from
the
client
is
routed
through
WebSEAL
server
2.
Apply
the
following
process
for
specifying
a
UUID
during
the
creation
of
a
junction:
1.
Create
a
junction
from
WebSEAL
server
1
to
each
back-end
server.
Use
create
–s
and
add.
2.
List
the
UUID
generated
for
each
back-end
server
during
Step
1.
Use
show.
3.
Create
a
junction
from
WebSEAL
server
2
to
each
back-end
server
and
specify
the
UUIDs
identified
in
Step
2.
Use
create
–s
–u
and
add
–u.
In
the
following
figure,
back-end
server
1
is
known
by
both
WebSEAL-1
and
WebSEAL-2
as
UUID
1.
Back-end
server
2
is
known
by
both
WebSEAL-1
and
WebSEAL-2
as
UUID
2.
Example:
In
the
following
example,
v
WebSEAL-1
instance
is
called
WS1.
Host
name
is
cruz.
v
WebSEAL-2
instance
is
called
WS2.
Host
name
is
meow.
v
Back-end
server
1
is
called
APP1
WebSEAL-1
Application
Server 2
Stateful
Junctions
WebSEAL-2
UUID B
Application
Server 1
UUID A
Figure
16.
Dissimilar
UUIDs
WebSEAL-1
Application
Server 2
(UUID 2)
Stateful
Junctions
Load
Balancing
Mechanism
WebSEAL-2
Client
Cookie
with
UUID 2
Application
Server 1
(UUID 1)
Figure
17.
Specifying
back-end
server
UUIDs
for
stateful
junctions
Chapter
10.
WebSEAL
junctions
303