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.

–<br />

When<br />

the<br />

Web<br />

document<br />

root<br />

is<br />

not<br />

specified<br />

on<br />

the<br />

command<br />

line<br />

or<br />

in<br />

the<br />

response<br />

file,<br />

amwebcfg<br />

automatically<br />

creates<br />

a<br />

new<br />

directory<br />

and<br />

adds<br />

the<br />

entry<br />

to<br />

the<br />

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

instance<br />

configuration<br />

file.<br />

The<br />

document<br />

root<br />

is<br />

built<br />

according<br />

to<br />

the<br />

following<br />

syntax:<br />

UNIX:<br />

installation_directory/pdweb/www-instance_name/docs<br />

Windows:<br />

installation_directory\pdweb\www-instance_name\docs<br />

–<br />

When<br />

the<br />

Web<br />

document<br />

root<br />

is<br />

specified<br />

on<br />

the<br />

command<br />

line<br />

or<br />

in<br />

the<br />

response<br />

file,<br />

amwebcfg<br />

adds<br />

the<br />

entry<br />

to<br />

the<br />

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

instance<br />

configuration<br />

file.<br />

Note:<br />

The<br />

directory<br />

must<br />

already<br />

exist.<br />

The<br />

amwebcfg<br />

utility<br />

will<br />

not<br />

create<br />

a<br />

new<br />

directory<br />

Sharing<br />

one<br />

Web<br />

document<br />

root<br />

directory<br />

across<br />

multiple<br />

instances<br />

Multiple<br />

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

server<br />

instances<br />

can<br />

use<br />

the<br />

same<br />

Web<br />

document<br />

root<br />

directory.<br />

When<br />

you<br />

want<br />

to<br />

use<br />

this<br />

scenario,<br />

the<br />

best<br />

way<br />

to<br />

configure<br />

the<br />

document<br />

root<br />

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

each<br />

new<br />

server<br />

instance<br />

is<br />

as<br />

follows:<br />

1.<br />

Allow<br />

amwebcfg<br />

to<br />

create<br />

a<br />

new<br />

Web<br />

document<br />

root<br />

directory.<br />

2.<br />

When<br />

amwebcfg<br />

configuration<br />

completes,<br />

manually<br />

edit<br />

the<br />

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

configuration<br />

file<br />

and<br />

reassign<br />

the<br />

document<br />

root<br />

value<br />

to<br />

the<br />

preferred<br />

directory.<br />

[content]<br />

doc-root<br />

=<br />

full_path_to_directory<br />

This<br />

procedure<br />

is<br />

recommended<br />

because<br />

each<br />

time<br />

a<br />

Web<br />

document<br />

root<br />

hierarchy<br />

is<br />

created,<br />

amwebcfg<br />

copies<br />

the<br />

contents<br />

of<br />

the<br />

html.tivoli<br />

directory<br />

hierarchy<br />

into<br />

the<br />

new<br />

Web<br />

document<br />

root.<br />

The<br />

contents<br />

of<br />

html.tivoli<br />

include<br />

an<br />

index.html<br />

file.<br />

This<br />

means<br />

that<br />

an<br />

existing<br />

index.html<br />

could<br />

get<br />

overwritten<br />

by<br />

the<br />

default<br />

(template)<br />

file<br />

from<br />

the<br />

html.tivoli<br />

directory.<br />

Manual<br />

editing<br />

of<br />

the<br />

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

configuration<br />

file<br />

avoids<br />

this<br />

problem.<br />

After<br />

editing<br />

the<br />

configuration<br />

file,<br />

you<br />

can<br />

remove<br />

the<br />

unneeded<br />

Web<br />

document<br />

root<br />

(the<br />

one<br />

created<br />

automatically<br />

by<br />

amwebcfg).<br />

Example<br />

server<br />

instance<br />

configuration<br />

values<br />

The<br />

following<br />

table<br />

contains<br />

a<br />

set<br />

of<br />

example<br />

settings<br />

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

a<br />

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

server<br />

instance.<br />

These<br />

example<br />

settings<br />

will<br />

be<br />

used<br />

in<br />

the<br />

sample<br />

configuration<br />

commands<br />

used<br />

in<br />

the<br />

remainder<br />

of<br />

the<br />

configuration<br />

sections<br />

of<br />

this<br />

chapter.<br />

Setting<br />

Value<br />

Administrative<br />

user<br />

ID<br />

sec_master<br />

Administrative<br />

user<br />

password<br />

mypassw0rd<br />

Host<br />

name<br />

diamond.subnet2.ibm.com<br />

Instance<br />

name<br />

web1<br />

Listening<br />

port<br />

7235<br />

Enable<br />

HTTP<br />

usage<br />

yes<br />

HTTP<br />

port<br />

81<br />

Enable<br />

HTTPS<br />

usage<br />

yes<br />

HTTPS<br />

port<br />

444<br />

Use<br />

logical<br />

network<br />

interface?<br />

yes<br />

20<br />

<strong>IBM</strong><br />

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

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

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

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

e-<strong>business</strong>:<br />

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

<strong>Administration</strong><br />

Guide

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

Saved successfully!

Ooh no, something went wrong!