Performing GCM server setup tasks to establish a
basic configuration, including authorizing initial user with administrator
privilege (see
Setting Up the GCM Server).
Running the GCM client (with administrator privilege)
to finish configuring the association (see
Setting Up the GCM Server).
Kits You can always find the latest versions of the POLYCENTER
Software Installation utility kits for the OpenVMS GCM server and
client on the OpenVMS web site, which is located at:
http://www.openvms.hp.com
Click on "Products" to find the location
of downloadable kits for the OpenVMS client and server, and the
zip file for the Windows client.
GCM is also available on the OpenVMS Alpha Version 7.3-2
Layered Product CD-ROM, which is shipped along with the operating
system.
Installing the GCM
Server The GCM server is preinstalled on OpenVMS Version 7.3-1
and higher versions. On previous versions of OpenVMS (Version 7.2-1H1
or higher), you can install the GCM server with the POLYCENTER Software Installation
utility kit (see
Kits ).
Installing the GCM server does the following:
Installs (or updates) the SYS$COMMON:[SYSEXE]GCM_SERVER.EXE
image.
Installs the SYS$COMMON:[SYS$STARTUP]GCMSRV$STARTUP.COM
file.
Defines the SYS$COMMON:[SYS$CONFIG] directory with
the logical name GCMSRV$DIR.
Installs the following files in directory GCMSRV$DIR:
$ PRODUCT INSTALL GCM_SERVER
The following product has been selected:
CPQ AXPVMS GCM_SERVER V1.0 Layered Product
Do you want to continue? [YES]
Configuration phase starting . . .
You will be asked to choose options, if any, for each selected product
and for any selected products that may be installed to satisfy software
dependency requirements.
CPQ AXPVMS GCM_SERVER V1.0: Graphical Configuration Manager V1.0
COPYRIGHT (C) 2002 -- All rights reserved
Compaq Computer Corporation
License and Product Authorization Key (PAK) Information
* This product does not have any configuration options.
Copying GCM Release Notes to SYS$HELP
Will install the GCM Server V1.0.
GCM Startup File
Execution phase starting . . .
The following product will be installed to destination:
CPQ AXPVMS GCM_SERVER V1.0 DISK$WFGLX5_X931:[VMS$COMMON.]
Portion done: 0%...10%...20%...30%...90%...100%
The following product has been installed:
CPQ AXPVMS GCM_SERVER V1.0 Layered Product
$
Installing the GCM
Client OpenVMS GCM Client describes
how to install the OpenVMS GCM client.
PC GCM Client describes how to install the PC GCM client.
$ PRODUCT INSTALL GCM_CLIENT
The following product has been selected:
CPQ AXPVMS GCM_CLIENT V1.0 Layered Product
Do you want to continue? [YES]
Configuration phase starting . . .
You will be asked to choose options, if any, for each selected product
and for any selected products that may be installed to satisfy software
dependency requirements.
CPQ AXPVMS GCM_CLIENT V1.0: Graphical Configuration Manager V1.0 Client
COPYRIGHT (C) 2002 --- All rights reserved
Compaq Computer Corporation
License and Product Authorization Key (PAK) Information
* This product does not have any configuration options.
Copying GCM Release Notes to SYS$HELP
Will install the GCM Java Client V1.0.
Will install a private copy of the Java JRE V1.2.2-3.
Will install a private copy of the Java Fast VM V1.2.2-1
Execution phase starting . . .
The following product will be installed to destination:
CPQ AXPVMS GCM_CLIENT V1.0 DISK$WFGLX5_X931:[VMS$COMMON.]
Portion done: 0%...10%...20%...30%...90%...100%
The following product has been installed:
CPQ AXPVMS GCM_CLIENT V1.0 Layered Product
$
Directory of GCM Client Files lists
the files in the current directory the OpenVMS GCM client is installed
in. Note that the OpenVMS GCM client installation installs the Java
Run-Time Environment in the JRE.DIR directory.
PC GCM Client To install the PC GCM client, first copy the GCM Client zip
file, which can be found on the OpenVMS Software web site at
http://www.openvms.hp.com/openvms
and then use a zip utility to install the GCM client.
You can also find GCM on the OpenVMS Alpha Version 7.3-2
Layered Product CD-ROM.
The installation process allows you to select the Windows
directory that will contain the GCM client. Note that to retain
any preferences between GCM client sessions, you must start the
GCM client from the directory you select during installation. You
can accomplish this by clicking the GCM Client icon.
Setting Up the GCM
Server To set up the GCM server, first set default to the SYS$COMMON:[SYS$CONFIG]
directory, and then run GCM$SETUP.EXE to perform the following tasks:
Define the initial configuration of
the association.
Authorize the initial user (username, password,
and privileges).
Choose whether or not to start the GCM server immediately.
Determine whether or not to automatically start
the GCM server when the system boots.
During GCM server setup, you can also choose to authorize
additional GCM users.
Running GCM$SETUP.EXE generates and encrypts the GCM administration
database file SYS$COMMON:[SYS$CONFIG]GCM_ADMIN.EDB. Choosing to
start the GCM server executes the SYS$STARTUP:GCMSRV$STARTUP.COM
procedure, which results in the following:
Creation and execution of GCMSRV$DIR:GCM_STARTUP.COM,
which starts the GCM server as a detached process with the log file
GCMSRV$DIR:GCM_SERVER.LOG.
Starting the GCM server with process name GCM_SERVER.
The GCM server automatically restarts after a server
fault. If the GCM server hangs, it will time out and restart. You
can also enter a RESTART command from a suitably privileged GCM
client.
The first time a GCM server restarts, its process name is
GCM_SERVER01. Thereafter, each time the GCM server restarts, its
process name is incremented by one, up to GCM_SERVER99; at that
point, subsequent restarts are disabled to prevent the GCM server
from entering a restart loop.
You can prevent attempts at automatic restart by defining
the system logical name GCMSRV$ABORT. After you eliminate the cause
of the restart attempts, you must deassign this logical name to
enable automatic restart of the GCM server.
Sample GCM Server Setup is an
example of how to set up the initial GCM server configuration.
Example 5 Sample GCM Server Setup
$ SET DEFAULT SYS$CONFIG
$ DIRECTORY
Directory SYS$COMMON:[SYS$CONFIG]
GCM$SETUP.EXE;1 GCM_BANNER.JPG;1 GCM_CERT.PEM;1 GCM_CUSTOM.XML;1
GCM_NOTICE.HTML;1 GCM_PRIVKEY.PEM;1 GCM_RULESET.XML;1
Total of 7 files.
$ RUN GCM$SETUP
OpenVMS GCM-Server Setup Utility
Copyright 2002, Hewlett Packard Corporation
This utility initializes the GCM Administrative Database:
SYS$COMMON:[SYS$CONFIG]GCM_ADMIN.EDB
If you are performing an initial GCM-Server installation that will
create an Association of more than a single server instance, you must
perform the following tasks to assure proper server synchronization:
1) Create the new local database using this utility.
2) Copy the database to all other GCM-Server instances in your
Association.
3) Start each GCM-Server.
You can start servers via $@SYS$STARTUP:GCMSRV$STARTUP.COM or by
invoking this utility on each system. When an existing database is
found, this utility will offer additional server startup options.
Continue (Y/N) {Y}?
Do you prefer full text assistance (Y/N) {N}? y
SERVER DISCOVERY TCP/IP PORT NUMBER:
Use the default Port Number 4100 (Y/N) {Y}? y
CONNECTION BOUNDS:
Use the default concurrent CLIENT limit of 4 (Y/N) {Y}? y
Use the default concurrent SERVER limit of 8 (Y/N) {Y}? y
CONNECTION SECURITY:
WARNING - DISABLING SECURITY COULD POTENTIALLY COMPROMISE THE
INTEGRITY OF YOUR SYSTEM AND IS NOT RECOMMENDED BY HEWLETT PACKARD.
Use SSL Client-Server Security (Y/N) {Y}? y
%SECURITY - WILL BE ENABLED.
SERVER ASSOCIATION RECORD:
Enter the Association Name (use no quotes): GCM Test Association
SYSTEM RECORDS:
Enter a SYSTEM Name (ex: star.zko.hp.com) (RETURN when done):
wfglx4.zko.hp.com
Enter a System IP Address (0 to use DNS): 16.32.112.16
Enter a System Number (range 0-7): 0
Enter a HARD PARTITION Number (range 0-7): 0
Enter a SOFT PARTITION Number (range 0-7): 0
%Define additional system records as needed...
Enter a SYSTEM Name (ex: star.zko.hp.com) (RETURN when done):
wfglx5.zko.hp.com
Enter a System IP Address (0 to use DNS): 16.32.112.17
Enter a System Number (range 0-7): 0
Enter a HARD PARTITION Number (range 0-7): 0
Enter a SOFT PARTITION Number (range 0-7): 1
%Define additional system records as needed...
Enter a SYSTEM Name (ex: star.zko.hp.com) (RETURN when done):
CLIENT AUTHORIZATION RECORDS:
Enter Client's Full Name or Title (RETURN when done): First Last
Enter Client's Username: First
Enter initial Password for First: Last
Enter EMAIL Address for First: First.Last@hp.com
Give First CONFIG Privilege (Y/N) {Y}? y
COMMAND privilege allows a user to issue DCL commands.
Give First COMMAND Privilege (Y/N) {Y}? y
Give First USER-COMMAND Privilege (Y/N) {Y}? y
Give First POWER Privilege (Y/N) {Y}? y
Give First ADMIN Privilege (Y/N) {Y}? y
Enable First account now (Y/N) {Y}? y
%Define additional client records as needed...
Enter Client's Full Name or Title (RETURN when done):
SERVER STARTUP OPTIONS:
Do you want the local GCM-SERVER to start on System Boot (Y/N) {Y}? y
Do you want to start the local GCM-SERVER now (Y/N) {Y}? y
************************ POST SETUP TASKS **************************
This completes the GCM Admin Database initialization.
IMPORTANT:
If you are using multiple GCM-Servers, copy the newly created GCM
Admin Database file: SYS$COMMON:[SYS$CONFIG]GCM_ADMIN.EDB, to the
same location on each system you defined in the Association, then
start or restart each server via $ @SYS$STARTUP:GCMSRV$STARTUP.COM
If the database has been properly defined, each server will detect
the presence of the other servers and form the specified Association.
If the GCM_SERVER process fails to start, examine the server logfile
SYS$COMMON:[SYS$CONFIG]GCM_SERVER.LOG.
When the server has started, you may use the GCM-Client to establish
a connection and further tune the installation.
For maximum security, you may wish to protect or remove this utility.
$
For an example of GCM server setup with complete prompting
text that explains each entry, see
Sample Verbose GCM Server Setup.
GCM Administration Database
The GCM$SETUP utility prompts you for details regarding system
configuration, user identification, and startup methods.
To enhance security, you can rename, delete, or otherwise
protect the GCM setup utility after you have run it. The setup utility
is required again only if you need to rebuild the initial database.
During the initial setup, you must define at least one system
to run the GCM server (typically, the system you are logged in to)
and authorize one user with administrator privilege. This user can
then run the GCM client and connect to the GCM server for further
configuration and tuning. During GCM server setup, you can define
additional instances in the association, and you can authorize additional
GCM users with individual access privileges. You can also perform
these tasks from a GCM client at any time.
The GCM setup utility creates the SYS$COMMON:[SYS$CONFIG]GCM_ADMIN.EDB
file, which is the initial GCM administration database. This is
an encrypted database that contains information about the association
and its users. In normal operation, this database can be interpreted
only by the GCM server. (See
Troubleshooting the GCM Server.)
If you have configured the association with more than one instance,
you must manually copy the GCM administration database file to the
GCM server directory of each additional instance before you start
GCM servers on those instances. Failure to copy the database file
can prevent the association from being properly created, or can
cause the initial GCM administration database to be overwritten.
Note that changing the configuration of the association, such
as by adding a new instance or by removing an instance, is a major
modification. Whenever you make a major modification to the association,
you must manually copy the GCM administration database file to the
GCM server directory on that instance before starting the GCM server.
Minor modifications to the database in an active association
automatically propagate to all GCM servers; you do not have to restart
the GCM servers. Minor modifications include actions such as adding
and removing GCM client records or adjusting GCM server parameters.