HP XC System Software Administration Guide Version 3.1

• “The nconfigure Scripts” (page 66)
• “The cconfigure Scripts” (page 66)
Common Conventions
When a node list is passed as an argument to the configuration scripts, the node list is passed in reverse
numeric order, which means that the head node is first if it is present in the list.
The naming convention for script file names follows this syntax; all script names begin with a capital letter
C:
C[0-9][0-9]service_name
For example, the gconfig script name for the Console Management Facility (CMF) is C50cmf. The capital
letter C is required in all script names, and cmf is the service name. The number 50 represents the order
in which the script runs during cluster_config processing. This number also enables you to control
dependency issues. For example, if a second service depends on CMF being configured, the script name
for the second service uses a number greater than 50 to ensure it is configured after CMF.
Depending upon the configuration requirements of a service, it is possible to have a C50cmf script in the
gconfig.d directory and a C50cmf script in the nconfig.d directory or in any other combination of
configuration directories.
It is also permissible for the script names for one or more services to use the same numeral. For this example,
if a script named C50dbserver also exists in the gconfig.d directory, the scripts are executed in
alphabetical order, with C50cmf executed first.
If you are adding a service, look in the script-specific directories, in /opt/hptc/etc/*config.d, and
in the roles_services_ini file to ensure that a script name and service is not already in use.
4.6.5.1 The sconfigure Scripts
The sconfigure scripts in the /opt/hptc/etc/sconfig.d directory modify the golden image and
are intended to configure systemwide functions, policies, and behaviors. They are intended to configure
system parameters that are not related to specific services and servers. Security policies often fall into this
category.
An sconfigure script often modifies files that become part of the golden image for the entire system or
that modify the database in some way.
An sconfigure script is executed inside the cluster_config utility as follows:
script_path sconfigure golden_client
script_path sunconfigure golden_client
The head node is the golden client, and only one golden client is supported. Each script in this directory
is executed unconditionally during the sconfigure process. The sconfigure scripts return 0 (zero) on
success and return a nonzero value on failures. You can stop the configuration process on a nonrecoverable
sconfigure error, which is indicated by the sconfigure script exiting with a return code of 255.
Alternatively, you can use config_die( ) in ConfigUtils.pm to return 255. Any exit code other than
255 continues with the configuration process.
The sconfigure scripts can include a user interface to aid in configuration and to suggest more optimal
configuration choices to the user.
The sunconfigure action is not performed automatically.
4.6.5.2 The gconfigure Scripts
The gconfigure scripts in the /opt/hptc/etc/gconfig.d directory modify the golden image and
set up client-to-server assignments and other global service configuration. A gconfigure script often
modifies global configuration files and modifies the database to include client/server relationships for
services.
The gconfigure action occurs only if one or more servers have been assigned the service. Thus,
gconfigure scripts are executed conditionally.
Common Conventions 63