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

–f
Force
the
replacement
of
an
existing
junction.
Junction
Point
Location
in
the
WebSEAL
namespace
to
create
the
junction.
Add
a
server
to
an
existing
junction
Operation:
Adds
a
server
to
an
existing
junction
point.
Syntax:
add
-h
host-name
[options]
junction-point
Host
Name
–h
host-name
**Required**
The
DNS
host
name
or
IP
address
of
the
target
back-end
server.
Options
Mutual
Authentication
Over
SSL
–D
″DN″
Specify
Distinguished
Name
of
back-end
server
certificate.
This
value,
matched
with
actual
certificate
DN
enhances
authentication.
Proxy
junction
options
(required
with
–t
tcpproxy
and
–t
sslproxy)
–H
host-name
DNS
host
name
or
IP
address
of
the
proxy
server.
–P
port
The
TCP
port
of
the
proxy
server.
General
TCP
and
SSL
junction
options
–i
WebSEAL
server
treats
URLs
as
case
insensitive.
–p
port
TCP
port
of
back-end
third-party
server.
Default
is
80
for
TCP
junctions;
443
for
SSL
junctions.
–q
url
Relative
URL
for
query_contents
script.
Access
Manager
looks
for
query_contents
in
/cgi_bin/.
If
this
directory
is
different
or
the
query_contents
file
renamed,
use
this
option
to
indicate
to
WebSEAL
the
new
URL
to
the
file.
–u
UUID
Specifies
the
UUID
of
a
back-end
server
connected
to
WebSEAL
via
a
stateful
junction
(–s).
–v
virt-host-name
Virtual
host
name
represented
on
the
back-end
server.
This
option
supports
a
virtual
host
setup
on
the
back-end
server.
You
use
–v
when
the
back-end
junction
server
expects
a
host
name
header
because
you
are
junctioning
to
one
virtual
instance
of
that
server.
The
default
HTTP
header
request
from
the
browser
does
not
know
that
the
back-end
server
has
multiple
names
and
multiple
virtual
servers.
You
must
configure
WebSEAL
to
supply
that
extra
header
information
in
requests
destined
for
a
back-end
server
set
up
as
a
virtual
host.
–w
Win32
filesystem
support.
Junction
Point
Add
server
to
this
existing
junction
point.
Appendix
B.
WebSEAL
junction
reference
495