Filter
Top Products
Changes since 5.1 Server GUI ADM
Options to the hpssgui and hpssadm startup scripts have 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 read
the ssm configuration file in the current working directory unless
the pathname to this file is specified by the -m option.
n n
The SSM client scripts now use an internal polling mechanism for
getting window updates (as opposed to being notified of the update
by the server). This means that:
• the SSM client application no longer requires a second
port for two-way communication,
• using SSM across an ssh tunnel is simpler since you
now need to set up the tunnel only in one direction,
• the rate of polling can be fine-tuned by the user (see the
-A, -G, -L -M, -W options).
n n
The scripts are dependent upon a login.conf file and, if using
Kerberos authentication, a krb5.conf file. The hpssuser program
creates both of these files. The scripts will look in the current
working directory for these files unless they are specified on the
command line (-C and -k options).
n n
It is no longer necessary to add a security provider entry to the java
system java.security file.
n n
The pathname to the java executable can be specified by using the
-j option. If this option isn't specified, then the script will use the
java executable in $JAVA_BIN if it is valid. If $JAVA_BIN/java
is not defined, then the script will use 'java' which will use the
client's $PATH.
n n
Effective with HPSS 5.1.1, the hpssgui script supports customizing
the user's background color or Look & Feel using the -b, -F and -T
options. Sites which did not apply the 5.1 patch would not have
had this functionality.
n
The SSM user can specify the number of alarms to display on the
alarm list using the -N option.
n n
The SSM user can specify the pathname to the hpss.jar using the -
P option.
n n
The SSM user can specify the path to search for application
preferences using the -i option. This path is now local to the SSM
client machine; preferences are no longer stored on the SSM server
machine.
n n
Sites which are converting from a previous release of HPSS should be
certain to replace all their hpssgui and hpssadm startup scripts on all client
platforms with the new versions.
n n
HPSS Installation Guide July 2008
Release 6.2 (Revision 2.0) 28