|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris 10 8/11 Installation Guide: Custom JumpStart and Advanced Installations Oracle Solaris 10 8/11 Information Library|
The custom JumpStart installation method is a command–line interface that enables you to automatically install or upgrade several systems, based on profiles that you create. The profiles define specific software installation requirements. You can also incorporate shell scripts to include preinstallation and postinstallation tasks. You choose which profile and scripts to use for installation or upgrade. The custom JumpStart installation method installs or upgrades the system, based on the profile and scripts that you select. Also, you can use a sysidcfg file to specify configuration information so that the custom JumpStart installation is completely hands-off.
Note - The root password for your client systems can be preset prior to the installation by including the root_password keyword in the sysidcfg. See the sysidcfg(4) man page.
Also, Auto Registration, a feature of Oracle Solaris, is new in the Oracle Solaris 10 9/10 release. When you install or upgrade your system, configuration data about your system is, on rebooting, automatically communicated through the existing service tag technology to the Oracle Product Registration System. This service tag data about your system is used, for example, to help Oracle enhance customer support and services.
If you include the auto_reg keyword in the sysidcfg file prior to the installation or upgrade, the installation can remain completely hands-off. However, if you do not include the auto_reg keyword, you will be prompted to provide your support credentials and proxy information for Auto Registration during the installation or upgrade.
For information about Auto Registration, including instructions about how to disable registrations, see Auto Registration in Oracle Solaris 10 8/11 Installation Guide: Planning for Installation and Upgrade.
The custom JumpStart process can be described by using an example scenario. In this example scenario, the systems need to be set up with the following parameters:
Install Oracle Solaris on 100 new systems.
Seventy of the systems are SPARC based systems that are owned by the engineering group and need to be installed as standalone systems with the Oracle Solaris OS software group for developers.
The remaining 30 systems are x86 based, owned by the marketing group and need to be installed as standalone systems with the Oracle Solaris OS software group for end users.
First, the system administrator must create a rules file and a profile for each group of systems. The rules file is a text file that contains a rule for each group of systems or single systems on which you want to install the Oracle Solaris software. Each rule distinguishes a group of systems that are based on one or more system attributes. Each rule also links each group to a profile.
A profile is a text file that defines how the Oracle Solaris software is to be installed on each system in the group. Both the rules file and profile must be located in a JumpStart directory.
For the example scenario, the system administrator creates a rules file that contains two different rules, one for the engineering group and another for the marketing group. For each rule, the system's network number is used to distinguish the engineering group from the marketing group.
Each rule also contains a link to an appropriate profile. For example, in the rule for the engineering group, a link is added to the profile, eng_profile, which was created for the engineering group. In the rule for the marketing group, a link is added to the profile, market_profile, which was created for the marketing group.
You can save the rules file and the profiles on a diskette or on a server.
A profile diskette is required when you want to perform custom JumpStart installations on nonnetworked, standalone systems.
A profile server is used when you want to perform custom JumpStart installations on networked systems that have access to a server.
After creating the rules file and profiles, validate the files with the check script. If the check script runs successfully, the rules.ok file is created. The rules.ok is a generated version of the rules file that the JumpStart program uses to install the Oracle Solaris software.