Sun Microsystems Logo
Products and Services
 
Support and Training
 
 

A  B  C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q  R  S  T  U  V  W  X  Y  Z  
 
File Formatsuserapp.conf(4)


NAME

 userapp.conf - SMCT structured list of user-defined configuration data to be installed at cluster installation and startup

SYNOPSIS

 SMCT_CONFIG_DIR/models/config.node_group_name
 config-dir/models/config.node_group_name

DESCRIPTION

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.

PARAMETERS

This section describes the parameters used in the user application configuration file:

{ ELEMENT config config-name
                 [next config-name]
         INVOLVE {file file-name}+
       }+
{ ELEMENT file file-name
                 location file-location
                 type file-type
                 [runLevel run-level-value] }+
       }+
  • config_name

    The name of the config element. Each config element contains an ordered sequence of user-defined configuration data files to be executed or installed, for example, two user application data files and an application installation script.

  • file_name

    The unique file name for the user application data or the application installation script.

  • file_type

    The file type of the user application data or the application installation script. This value can be one of the following:

    • DATA

      A DATA file type is a user application data file that is not executed but contains nonASCII data, such as static parameters.

    • PRE_SCRIPT

      A PRE_SCRIPT file type is an application installation script that is executed as part of the final stages of the Solaris JumpStart installation.

    • POST_SCRIPT

      A POST_SCRIPT file type is an application installation script that is executed after Solaris JumpStart installation at run level 2 or run level 3, that is, the POST_SCRIPT can be run before or after the startup of the Foundation Services. This is determined by the run_level_value.

  • file_location

    The location of the user application data or the application installation script, expressed as a URI.

  • run_level_value

    The run-level for the execution of the application installation script, either 2 or 3. The default value is 3. The run level is only used for POST_SCRIPT application installation scripts.

  • next

    This is an optional keyword that is used to determine the execution order of the config elements. For example:

    ELEMENT config softSwitch_3 next softSwitch_4

    In this case, the application will execute the softSwitch_4 config element after the softSwitch_3 config element.

EXAMPLE

The following is an example of a user application configuration file config.soft_switch, for a node group soft_switch.

# Configuration of node group softSwitch - first stage -
#
# Script softSwitch_1.sh will be executed during Jumpstart finish stage
#ELEMENT config softSwitch_1
        INVOLVE file data_1_1 
                file data_1_2 
                file script_1_3

ELEMENT file data_1_1 
        type DATA
        location 'file://config/softSwitch_1_1.conf'

ELEMENT file data_1_2 
        type DATA
        location 'file://config/softSwitch_1_2.conf'

ELEMENT file script_1_3 
        type PRE_SCRIPT
        location 'file://config/softSwitch_1.sh'

#
# Configuration of node group softSwitch - second stage -
#
# Script softSwitch_2.sh will be executed at init run-level 2 
# The node will automatically reboot
#
ELEMENT config softSwitch_2
        INVOLVE file data_2_1 
                file script_2_2

ELEMENT file data_2_1
        type DATA
        location 'file://config/softSwitch_2_1.conf'

ELEMENT file script_2_2
        type POST_SCRIPT
        runLevel 2
        location 'file://config/softSwitch_2.sh'

#
# Configuration of node group softSwitch - third stage -
#
# Scripts will be executed at init run-level 3 in the following order:
#	1. softSwitch_3.sh
#	2. softSwitch_4.sh
#
ELEMENT config softSwitch_3 next  softSwitch_4
        INVOLVE file script_3_1

ELEMENT file script_3_1
        type POST_SCRIPT
        location 'file://config/softSwitch_3.sh'

ELEMENT config softSwitch_4
        INVOLVE file script_4_1

ELEMENT file script_4_1
        type POST_SCRIPT
        location 'file://config/softSwitch_4.sh'  

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPEATTRIBUTE VALUE
ArchitectureSPARC
AvailabilitySUNWnhsmc
Interface StabilityEvolving

SEE ALSO

slconfig(1M)


Netra HAS FS 2.1Go To TopLast Changed September 2004