Do not use the SMCT tool with the current patch level of the Foundation Services
product.
An SMCT configuration file for user applications is required for each
cluster node group that is to be installed with user applications during SMCT
configuration stage two. This file is used as a parameter of the slconfig command. For more information on slconfig,
see the slconfig(1m) man page.
This configuration file contains a structured list of user-defined configuration
data to be installed at specific stages of cluster startup, together with
the user applications. User-defined configuration data can be the following:
-
User application data files that contain data to be added
to the user application.
For example, if the user application is a database package, the user
application data file could be data to populate the database.
-
Application installation scripts that add the user application
data to the user applications.
For example, you can specify a script or scripts to populate the database
with the application data to create new records and entries.
The configuration file for user applications uses the terms config and file to describe the running order
of the application installation scripts and the user application data that
are to be installed.
The configuration file contains a chain for three stages of the cluster
installation and startup. The stages are the following:
-
At the final stage of the Solaris JumpStart installation of
the flash archive.
-
At run level 2, the Foundation Services packages are installed
but they are not started.
-
At run level 3, the Foundation Services are started and running.
You can create a configuration file for each node group, using the following
file naming rules:
config.node_group_name
node_group_name is the name of the node group
as defined in the file cluster.conf, for example, soft_switch. The user application configuration file name for the
node group soft_switch would be config.soft_switch.
When creating the configuration file for user applications, consider
the following:
-
You cannot have more than two config element
chains in a file.
-
All files in a config chain must be of
the same type (PRE_SCRIPT or POST_SCRIPT).
-
A config element cannot be chained to itself.
-
There must not be circular dependencies between config elements.
-
There must be no infinite config chains.