Filter
Top Products
3.3.5.1. Automatic SSM Client Packaging and Installation
The hpssuser utility provides a mechanism for packaging all the necessary client files required to
execute the hpssgui program on the user's desktop host. Refer to the hpssuser man page for more
information on generating an SSM Client Package. These files may also be copied manually; see Section
3.3.5.2: Manual SSM Client Packaging and Installation, for a list of the required files.
This example creates an SSM Client Package named “ssmclient.tar”:
%/opt/hpss/bin/hpssuser -ssmclientpkg ssmclient.tar
[ packaging ssm client ]
[ creating ssmclient.tar ]
hpssgui.pl
hpssgui.vbs
hpss.jar
krb5.conf
ssm.conf
[ packaged ssm client in ssmclient.tar ]
Once the SSM Client Package has been generated simply FTP the tar file over to the client node and then
extract the member files to the desired location.
3.3.5.2. Manual SSM Client Packaging and Installation
This section describes the manual installation of the necessary client files required to execute the hpssgui
or hpssadm program on the user's desktop host. The hpssuser utility also provides a mechanism for
packaging these files automatically; see Section 3.3.5.1: Automatic SSM Client Packaging and
Installation.
The desktop machine requires the proper version of Java and the following HPSS files, which should be
copied from the host on which the SSM System Manager executes:
• scripts: hpssgui.pl, hpssgui.vbs, hpssadm.pl, or hpssadm.vbs
• hpss.jar
• ssm.conf
• krb5.conf [if using Kerberos authentication]
• user keytab [if using hpssadm]
• help files [optional]
These are the default locations of these files on the SSM System Manager host, from which they may be
copied:
startup scripts /opt/hpss/bin
hpss.jar /opt/hpss/bin
ssm.conf /var/hpss/ssm
krb5.conf /etc/krb5.conf
keytab file /var/hpss/ssm/keytab.USERNAME
help files /var/hpss/doc
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 43