Richard:
Here is the basic information you are looking for extracted from the
ADSM readme files:
Webshell:
Installation checklist
For multiuser systems the WebShell installation procedure should be
performed by the system administrator and run as a process under the
system administrator
(e.g., root for AIX), since he will have the correct permissions to
update/read secure directories (e.g., directory containing passwords).
1.Copy the WebShell package (winweb.exe, os2web.exe, or aixweb.tar)
to the directory containing (or to contain) the ADSM Command Line client
(dsmc.exe or dsmc).
2.Change to that directory.
3.Extract the WebShell files. For Windows execute winweb. For OS/2
execute os2web. For AIX execute tar -xvf aixweb.tar.
4.Inform WebShell of your ADSM password, by executing adsmpswd. (This
is only required when ADSM password = generate is not used.)
For Windows and OS/2 this password file, adsmpswd.ws should reside
in the wsstuff directory created during the extraction. For AIX,
adsmpswd.ws
should reside in /etc/security/adsm.
5.Inform WebShell of the userids on the system, their type (regular
user vs administrator), and the passwords to be used for Web
authentication, by
executing mkwspswd.
For Windows and OS/2 this password file, adsmweb.ws should reside
in the wsstuff directory created during the extraction. For AIX,
adsmweb.ws
should reside in /etc/security/adsm.
6.Execute WebShell by webshell OptionalPortNumber
OptionalLocationOfWebAuthenticationFile .
7.Access WebShell by URL: http://YourMachineName:PortNumber/webshell.
Note: Default port number is 2121.
Extracting WebShell files
The WebShell package is downloaded as one file, a self extracting zip
file for Windows (winweb.exe) and OS/2 (os2web.exe) or as a tar file for
AIX
(aixweb.tar).
WebShell package contents
The WebShell package contains the following files:
executables
webshell.exe (for Windows and OS/2) or webshell (for AIX)
The WebShell executable/binary
adsmpswd.exe (for OS/2 and Windows) or adsmpswd (for AIX)
Used to create/update adsmpswd.ws (ADSM password file)
mkwspswd.exe (for OS/2 and Windows) or mkwspswd (for AIX)
Used to create/update adsmweb.ws (WebShell Web
authentication file)
webstart (for AIX only )
Shell script used to invoke webshell via /etc/inittab
html files
wsreadme.html
Installation instructions
adsmhbs.html
Help for the backup selection form
adsmhrs.html
Help for the restore selection form
adsmhbk.html
Help for the backup operation form
adsmhrst.html
Help for the restore operation form
images
backgrou.gif
Graphic for the background
adsmhead.gif
Graphic for the ADSM WebShell banner
adsmhelp.gif
Graphic for the ADSM WebShell help banner
backup.gif
Graphic for the backup to safe image displayed on the
backup form
restore.gif
Graphic for the safe to restore image displayed on the
restore form
info.gif
Graphic for the ADSM WebShell help icon
blank.gif
Graphic for small space filler
rbspace.gif
Graphic for larger space filler
security
adsmpswd.ws
File containing scrambled version of ADSM password, to be
used by WebShell when communicating with the ADSM server. Note: this
file
will be created when executing adsmpswd.
adsmweb.ws
File containing userids, scrambled passwords, and type of
user (e.g., general user vs administrator), to be used by WebShell to
authenticate
Web users. Note: this file will be created when executing
mkwspswd.
miscellaneous
adsmresp.ws
File used by WebShell to end response prompting by the
ADSM server
To extract the files from the package, for Windows execute winweb, for
OS/2 execute os2web, or for AIX execute tar -xvf aixweb.tar from the
directory
containing the ADSM Command Line client (dsmc.exe for Windows and OS/2,
or dsmc for AIX). The other files (html, images, security, and response
files)
need to reside in an immediate subdirectory of the executable directory,
called wsstuff. The extraction process will create the wsstuff
subdirectory and place the
non executable files there.
Note for AIX:
The security files need to reside in /etc/security/adsm.
Note for NetDoor or other LAN server environments:
The WebShell executables/binaries and wsstuff directory should also
reside within the same directory as the ADSM command line client.
However, if security
(ADSM password and Web authentication password) is on a local machine
basis, the security files need to reside on each local machine. Specify
the location of
these security files when invoking webshell .
Security
In order for WebShell to communicate with the ADSM server, it requires
the ADSM password of the client. This password will be kept in the file
adsmpswd.ws, in scrambled format. If password = generate is not active,
execute the adsmpswd executable to create adsmpswd.ws with the valid
ADSM
password. (When invoked without arguments, adsmpswd will provide the
command syntax.)
Note:
If password = generate is active, the password file's contents are
ignored.
In order for a user to access WebShell, via a Web browser, his userid
and password must be validated. These userid(s) and password(s) are kept
in file
adsmweb.ws, in scrambled format. Execute mkwspswd to create the Web
authentication entries. (When invoked without arguments, mkwspswd will
provide
the command syntax.)
For AIX, there should be an entry for each user on the system including
root. The userid in the password entry must match the userid on the
system. Each user
has access to his own files, while root has access to all the files.
Since OS/2 is a single user system, only one entry for the machine owner
is required. However, if there is an administrator for the client
machines, an additional
entry should be created for him.
Execution
There can be two input arguments when executing WebShell: a port number,
and a different location for the adsmweb.ws password file.
WebShell includes an embedded Web server. As such it needs to know what
port to listen on for the requests from the Web browser. The default
port number
is 2121. If you desire a different port number, specify the new port
number as the first argument when executing webshell.
Note:
When WebShell is accessed, via a Web browser, the port number specified
must match the input or default port number. For example, if the
following command
is executed on the ADSM client machine peaches, webshell 3019, the URL
to access WebShell would be http://peaches:3019/webshell. Or if the port
number wasn't changed and just webshell was invoked, the URL to access
WebShell would be http://peaches:2121/webshell.
As mentioned above, the ADSM Web authenticated password file is expected
to reside in the wsstuff subdirectory of the webshell executable
directory for
Windows and OS/2, or /etc/security/adsm for AIX. To override this
location, specify the new location, as a fully qualified path name, as
the second argument
when executing webshell.
For example, if you are an AIX user that would like to try WebShell
before root has installed it on your system, you would need to specify
the location of the
adsmweb.ws password file, since you would not have access to update/read
from /etc/security/adsm. So, for example, if adsmweb.ws file existed in
/u/plums/webshell/wsstuff and the chosen port is 3019, the following
command should be executed, webshell 3019 /u/plums/webshell/wsstuff.
WebShell can be executed in a number of ways. It can be executed
directly from the command line, on an as needed basis. Or via a program
folder, again on an
as needed basis. Or via your system startup process (e.g., startup
folder for OS/2, inittab for AIX).
Note:
For multiuser systems, it should be installed and executed under an
administrator/root process who has the appropriate permissions to update
directories and
access the password files.
Note:
For AIX, an additional shell script webstart is provided to start
webshell via /etc/inittab. /etc/inittab can be updated manually or by
using the mkitab utility.
For either, the fully qualified path name of webstart must be specified.
Known Problems
Windows NT
For mixed case drive labels (i.e., not all upper case), the View
Restore Menu is unable to display the directories and files that have
been backed up for
that file space, since ADSM does not recognize the file space name.
For example, if the label on your c drive is called System-Drive (note
the mixed
case), you will not be able to view the directories/files that have
been backed up within that file space and consequently you will not be
able to restore any
directories/files from that file space. However, if the drive label
is SYSTEM-DRIVE, there is no problem since ADSM recognizes that file
space name.
This is an ADSM Windows NT command line client bug, not a
WebShell bug, so look for a fix from the ADSM Windows NT command line
client.
Web Browsers
Screen not being refreshed when Backup Selection is pressed
The browser doesn't realize the request is for a form, so if
caching is on, the browser displays the same page from his cache, rather
than sending the
request to WebShell. As an interim solution, turn your
browser's cache off.
|
