Filter
Top Products
1.4.4. SSM Changes
Significant changes were made in SSM between Releases 4.5 and 5.1 and again between 5.1 and 6.2.
For the reader's convenience, all changes between 4.5 and 6.2 are summarized in Section 3.3.4.1:
Changes Affecting Sites Upgrading Directly from 4.5. Changes between 5.1 and 6.2 are summarized
in Section 3.3.4.2: Changes Affecting Sites Upgrading from 5.1. The tables indicate whether each
change affects the SSM Server (the System Manager), the SSM GUI hpssgui, and/or the HPSS
command line utility hpssadm. Sites need consult only the table which pertains to them.
1.4.4.1. Changes Affecting Sites Upgrading Directly from 4.5
Changes since 4.5 Server GUI ADM
The SSM System Manager and Data Server were consolidated in release
6.2 into a single server, the SSM System Manager.
n
Java is now required for the SSM Graphical User Interface (hpssgui). Java
is no longer required by the SSM server (the new consolidated SSM
System Manager).
n n
SSL is no longer supported with SSM. This means it is no longer
necessary to create an SSL certificate (the /var/hpss/ssm/ds.cer file) or
import it into the certificate authority file ($JAVA_ROOT/jre/lib/cacerts)
on each SSM client machine.
n n n
The Java Security Manager is no longer used with SSM. This means the
Java Policy files are no longer required. In 4.5, these files were the
java.policy.ds and the java.policy.hpssadm.
n n n
The hpssadm.jar and mobjects.jar files are no longer used. All classes are
now in a single jar file hpss.jar.
n n
The start_ssm script is no longer available. The SSM System Manager is
started with the rc.hpss script. The rc.hpss script has been moved from a
default location of /etc to /opt/hpss/bin.
n
The start_ssm_session script is no longer available. In HPSS 6.2, the SSM
GUI is started with the hpssgui startup script. There are perl and vbs
versions of this script, named with an extension to indicate the type of
script: hpssgui.pl and hpssgui.vbs.
n
There are new versions of the hpssadm startup scripts in perl and vbs.
These are named with an extension to indicate the type of script:
hpssadm.pl and hpssadm.vbs. The ksh and bat scripts are no longer
supported.
n
Options to the new hpssgui startup scripts differ considerably from the
options to the old start_ssm_session script. Options to the hpssadm startup
scripts have also changed significantly. See the man pages for details.
Following are some highlights:
n n
The scripts are dependent upon an SSM configuration file
(ssm.conf), created by mkhpss, which contains some site-specific
configuration values. The SSM client script will attempt to ready
the SSM configuration file in the current working directory unless
the pathname to this file is specified by the -m option.
n n
HPSS Installation Guide July 2008
Release 6.2 (Revision 2.0) 21