IBM RELEASE 7.3 Management Manual Download Page 33

Page: 33 / 388

port

hpssgui

and

hpssadm

clients must access to reach the System Manager.

This task can be made a bit easier if the System Manager RPC program number is labeled in the
portmapper. To do this, add a line for the System Manager in the /etc/rpc file specifying the program
number and a convenient rpc service name such as “hpss_ssm” (note that names may not contain
embedded spaces). Then this service name will show up in the

rpcinfo

output.

The format of the /etc/rpc file differs slightly across platforms. See the platform specific man pages for
the rpc file for details. The

rpcinfo

utility is typically found in either /usr/bin (AIX) or /usr/sbin (Linux).

3.2. Quick Startup of hpssgui

We recommend that

hpssgui

sessions be invoked from the user's desktop computer instead of on the

HPSS server machine.

hpssgui

is an application designed to run in the Java environment on the user's

desktop computer and to communicate with the remote SSM System Manager. If

hpssgui

is executed on

the remote System Manager host, it must run through an X windows session and it may run very slowly
in that environment. This is a limitation of Java and networks.

We recognize the value of using the remote X functionality as a quick way to get SSM running, but once
your system is up, it is highly recommended that you configure local desktop SSM

hpssgui

clients for all

HPSS administrators and operators. Local desktop

hpssgui

configuration is detailed in Section 3.3:

Configuration and Startup of hpssgui and hpssadm

below.

Following are steps for quickly configuring and starting an SSM GUI client:

1. Use the

hpssuser

utility to create an SSM user with admin authority. See Section 3.3.2.1:

The

hpssuser Utility

on page 35 and the

hpssuser

man page for more information.

2. On Linux systems, set the JAVA_BIN environment variable to point to the Java runtime binary

directory. Set the variable in the environment override file, usually /var/hpss/etc/env.conf. It is
usually set to something like /usr/java5/bin. The default setting of $JAVA_BIN is /usr/java5/bin
which is the usual location of the java binary directory.

3. The

mkhpss

utility generates the ssm.conf SSM configuration text file when configuring the SM.

See the

HPSS Installation Guide,

Section 5.3:

Install HPSS/DB2 and Configure HPSS

Infrastructure

for more details. Verify the existence of the $HPSS_PATH_SSM/ssm.conf file.

4. Start the

hpssgui

script:

% /opt/hpss/bin/hpssgui.pl

Note that the -m option can be used to specify the desired SSM configuration file to be used.
When this option is not specified, hpssgui.pl looks for the ssm.conf configuration file in the
current directory, then in the directory defined by the HPSS_PATH_SSM environment
variable (usually /var/hpss/ssm). If the script doesn't find a configuration file in either
directory, it will use default values to start the client

Note that the -d (debug) and -S (log file name) options can be used to capture all levels of

hpssgui

logging in a text file. Bear in mind, however, that this can generate significant

amounts of log data. (See the

hpssgui

man page.)

HPSS Management Guide

November 2009

Release 7.3 (Revision 1.0)