第14章 Graphical Configuration Manager

$ 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:

 By default, the GCM-Servers listen for client connections on
 TCP/IP Port 4100.  This can be changed, but each server will need
 to be restarted, and each client will need to specify the new
 port number in their "Server Connection Preferences" settings.

 Use the default Port Number 4100 (Y/N) {Y}? y

 CONNECTION BOUNDS:

 By default, the GCM-Servers support up to 4 concurrent clients
 and 8 concurrent servers.  This can be changed, but each server
 will need to be restarted. Be advised that GCM performance may
 suffer as these values are increased.

 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:

 By default, the GCM-Servers expect that their clients will be
 using secure connections (SSL).  This can be disabled, but the
 servers will need to be restarted, and each client will need
 to change their "Server Connection Preferences" settings.

 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:

 Multiple GCM-Servers can form an "Association" of systems, providing
 a wide management scope.  This Association may include one server per
 soft-partition on one or more hard-partition on one or more physical
 system. Regardless of how many servers are in the Association, you
 need to define an Association Name that describes the involved systems.
 Choose a simple descriptive string such as "Engineering Lab Systems".

 Enter the Association Name (use no quotes): GCM Test Association

 SYSTEM RECORDS:

 Each system in the Association must be uniquely identified by its
 IP Address, System Number, Hard-Partition Number, and Soft Partition
 Number.  At least one system must be defined.  You may define multiple
 systems now, or define additional systems after establishing your
 first client connection.

 Enter a fully qualified name for the system running a GCM-Server.
 For example: star.zko.hp.com. When you are done entering system
 records, enter 0 at the following prompt.

 Enter a SYSTEM Name (ex: star.zko.hp.com) (RETURN when done): wfglx4.zko.hp.com

 Enter a fully qualified IP Address for the system running a
 GCM-Server.  For example: 16.32.112.16
 If you prefer to use DNS to lookup the address, enter 0

 Enter a System IP Address (0 to use DNS): 16.32.112.16

 The SYSTEM NUMBER is a simple numeric value that uniquely identifies
 soft and hard partitions that reside in a common partitionable
 computer.  For example, if you have two separate partitionable
 computers in your Association, each having its own hard and soft
 partitioned instances, enter a SYSTEM NUMBER of 0 for all hard and
 soft partitions in the first computer, and enter 1 for those in the
 second computer.

 Enter a System Number (range 0-7): 0

 The HARD PARTITION NUMBER is a numeric value that uniquely identifies
 which HARD Partition a GCM-Server resides within.  If a system has
 only a single HARD Partition, enter 0.  If a system has multiple
 HARD Partitions, use the appropriate Hard Partition ID.  These are
 sequential numeric values which were used when creating the system
 partitions.  You can also obtain these values by running the Galaxy
 Configuration Utility via $ CONFIG GALAXY command.

 Enter a HARD PARTITION Number (range 0-7): 0

 The SOFT PARTITION NUMBER is a numeric value that uniquely identifies
 which SOFT Partition a GCM-Server resides within.  If a system has
 only a single SOFT Partition, enter 0.  If a system has multiple
 SOFT Partitions, use the appropriate Soft Partition ID.  These are
 sequential numeric values which were used when creating the system
 partitions.  You can also obtain these values by running the Galaxy
 Configuration Utility via $ CONFIG GALAXY command.

 Enter a SOFT PARTITION Number (range 0-7): 0

 %Define additional system records as needed...

 Enter a fully qualified name for the system running a GCM-Server.
 For example: star.zko.hp.com. When you are done entering system
 records, enter 0 at the following prompt.

 Enter a SYSTEM Name (ex: star.zko.hp.com) (RETURN when done): wfglx5.zko.hp.com

 Enter a fully qualified IP Address for the system running a
 GCM-Server.  For example: 16.32.112.16
 If you prefer to use DNS to lookup the address, enter 0

 Enter a System IP Address (0 to use DNS): 16.32.112.17

 The SYSTEM NUMBER is a simple numeric value that uniquely identifies
 soft and hard partitions that reside in a common partitionable
 computer.  For example, if you have two separate partitionable
 computers in your Association, each having its own hard and soft
 partitioned instances, enter a SYSTEM NUMBER of 0 for all hard and
 soft partitions in the first computer, and enter 1 for those in the
 second computer.

 Enter a System Number (range 0-7): 0

 The HARD PARTITION NUMBER is a numeric value that uniquely identifies
 which HARD Partition a GCM-Server resides within.  If a system has
 only a single HARD Partition, enter 0.  If a system has multiple
 HARD Partitions, use the appropriate Hard Partition ID.  These are
 sequential numeric values which were used when creating the system
 partitions.  You can also obtain these values by running the Galaxy
 Configuration Utility via $ CONFIG GALAXY command.

 Enter a HARD PARTITION Number (range 0-7): 0

 The SOFT PARTITION NUMBER is a numeric value that uniquely identifies
 which SOFT Partition a GCM-Server resides within.  If a system has
 only a single SOFT Partition, enter 0.  If a system has multiple
 SOFT Partitions, use the appropriate Soft Partition ID.  These are
 sequential numeric values which were used when creating the system
 partitions.  You can also obtain these values by running the Galaxy
 Configuration Utility via $ CONFIG GALAXY command.

 Enter a SOFT PARTITION Number (range 0-7): 1

 %Define additional system records as needed...

 Enter a fully qualified name for the system running a GCM-Server.
 For example: star.zko.hp.com. When you are done entering system
 records, enter 0 at the following prompt.

 Enter a SYSTEM Name (ex: star.zko.hp.com) (RETURN when done): 

 CLIENT AUTHORIZATION RECORDS:

 At least one client must be defined in order to allow an initial
 client-server connection to be established. Additional clients may
 be defined now, or at any point using the client application and the
 GCM Subscription Procedure.  This initial client record must provide
 fully privileged access for the specified user so that subsequent
 GCM administration functions can be performed.

 Enter a string which describes this client.
 The string can be the users full name, or job title, etc.

 Enter Client's Full Name or Title (RETURN when done): First Last

 Enter the clients USER name.  This is a single word that identifies
 the user, such as their last name.

 Enter Client's Username: First

 Enter the clients PASSWORD.  This is a unique GCM password,
 unrelated to any system authorization function.
 Note: Passwords can be changed by any GCM-Client with Admin privilege.

 Enter initial Password for First: Last

 Enter the clients EMAIL Address.  This is particularly important
 for the client that is serving the role of GCM Administrator as
 they will receive email subscription requests.

 Enter EMAIL Address for First: First.Last@hp.com

 CONFIG privilege allows a user to issue commands that alter a system
 configuration (if they also have the COMMAND privilege) and to load
 and save configuration models.

 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

 USER-COMMAND privilege allows a user to create their own command
 menu entries. Commands are executed in a privileged context so
 use discretion when authorizing this privilege.

 Give First USER-COMMAND Privilege (Y/N) {Y}? y

 POWER privilege allows a user to issue commands that power on or off
 system components for systems that support such operations.

 Give First POWER Privilege (Y/N) {Y}? y

 ADMIN privilege allows a user to modify the GCM-Server Administration
 Database.  Use discretion when authorizing this privilege.

 Give First ADMIN Privilege (Y/N) {Y}? y

 You may choose to ENABLE this client immediately, or enable the
 client later once the GCM is fully configured.
 IMPORTANT: Be sure to enable the initial administrator client!

 Enable First account now (Y/N) {Y}? y

 %Define additional client records as needed...

 Enter a string which describes this client.
 The string can be the users full name, or job title, etc.

 Enter Client's Full Name or Title (RETURN when done): 

 SERVER STARTUP OPTIONS:

 You may choose to have the local GCM-Server started automatically upon 
 system boot.  If you choose this option, the server will be started 
 during the next system boot. To accomplish this, the startup file 
 SYS$STARTUP:GCMSRV$STARTUP.COM will be added to the Layered Product 
 startup database.

 Do you want the local GCM-SERVER to start on System Boot (Y/N) {Y}? y

 You may choose to start the local GCM-Server now, or you can start 
 it later via $@SYS$STARTUP:GCMSRV$STARTUP.COM 

 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.

$