sun.com | docs.sun.com | How To Buy | My Sun | Worldwide Sites |  |

| Previous Contents Index Next
Chapter 6 # Configuration Stage 2: Adding User-Defined Data to the Flash Archive This chapter describes how to add user-defined data and user-specific installation scripts to an existing flash archive. The flash archive can be: A generic flash archive created in stage 1, as described in Chapter 5, Configuration Stage 1: Creating a Generic Flash Archive. A deployable flash archive that has already been through stage 3, as described in Chapter 7, Configuration Stage 3: Configuring the Flash Archive for Deployment. Stage 2 is optional. If you do not plan to add user applications and user-defined configuration data, you do not need to read this chapter. The `slconfig` command prepares the software load configuration data, and the `flconfig` command incorporates the user-defined configuration data into the flash archives. When stage 2 is complete, you have one or more flash archives that include user applications and user-defined configuration data. These archives are called configured flash archives. This chapter contains the following sections: Configuration Stage 2 Checklist Configuration Stage 2 Procedure Creating a User Application Configuration File for a Node Group Preparing User-Defined Configuration Data Copying User-Defined Configuration Data to an Export Directory Adding User-Defined Configuration Data to the Flash Archive ## Configuration Stage 2 Checklist Before you perform configuration stage 2, ensure you have: Created a generic flash archive as described in Chapter 5, Configuration Stage 1: Creating a Generic Flash Archive. Declared your user applications in the software configuration file(s) described in Creating a Software Configuration File for a Node Group. ## Configuration Stage 2 Procedure The following figure shows the configuration procedure for stage 2, resulting in a configured flash archive. Figure 6-1 Configuration Stage 2 ## Creating a User Application Configuration File for a Node Group The user application configuration file contains a structured list of user-defined configuration data to be run at specific stages of cluster startup. User-defined configuration data can be: 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 a database with the application data to create new records and new entries. A user application configuration file is required for each node group that is to be installed with user applications. If no applications are to be deployed, it is not necessary to have any user application configuration files. The application installation scripts can be executed at any one of three stages during the boot phase of the target cluster: At Solaris JumpStart installation, during the execution of the `finish` script At run level 2, when the Foundation Services packages are installed but they are not started At run level 3, when the Foundation Services are started and are running The following figure illustrates the stages at which the installation scripts run during the final system boot sequence. Figure 6-2 Boot Sequence for User Application Configuration Files Note - When creating the application configuration file, note that the `PRE_SCRIPT` scripts do not run under the root directory (`/`) during the Solaris Jumpstart finish script. For more information, see the Solaris Custom JumpStart Guide. The following example is a user application configuration file `config.soft_switch`, for a node group `soft_switch`. Example 6-1 Example of a User Application Configuration File
    # 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'
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems