Migrating From JumpStart to AI

AI performs automated installations of single or multiple systems. This tool replaces JumpStart in this release. The following table describes the similarities and differences between AI and JumpStart. See also Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11 Automated Installer.

Table 2-2 JumpStart Tasks Compared to AI Tasks

Task	JumpStart Command or Method	AI Command or Method
Set up an install server.	`setup_install_server`	`installadm create-service`
Add clients to the installation.	`add_install_client`	`installadm create-client`
Create derived profiles.	Use a begin script.	Use the derived manifest mechanism.
Specify installation instructions.	Use profile files.	Use AI manifests.
Provision the client.	Use DVDs.	Use a package repository on the Internet or a local network.
Specify client customizations.	Use rules files to associate clients with profile files.	Use `installadm` with the appropriate subcommands to associate clients with AI manifests and system configuration profiles.
Specify client configurations.	Use finish scripts and `sysidcfg` files.	Use an SMF system configuration profile file or scripts that are executed by an SMF service that runs once during the first boot.

Using the JumpStart Migration Utility

The js2ai utility converts Oracle Solaris 10 JumpStart rules and profiles to a format that is compatible with AI manifest entries. To use the js2ai utility, first install the pkg:/install/js2ai package. See the js2ai(1M) man page and Chapter 2, Converting Rules and Profile Files, in Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11 Automated Installer.

JumpStart to AI Conversion Tasks

To migrate from JumpStart to AI, you must complete the following tasks. Some of these tasks can be performed by using the js2ai utility.

Specify AI client criteria.

You can specify AI client criteria as follows:
- By using the installadm add-manifest or installadm create-profile command with the -c option, or by using the installadm set-criteria command with the -c or -a options.
- By using the installadm add-manifest command to specify criteria files, by using the installadm create-profile command, or by using the installadm set-criteria command with the -C option.
For example, the karch i86pc JumpStart keyword is specified as an AI criteria directive in command-line format as follows:
```
# installadm add-manifest -c arch=i86pc
```
The same directive is specified in a criteria file as follows:
```
<ai_criteria name="arch">
 <value>i86pc</value>
</ai_criteria>
```
See Chapter 9, Customizing Installations, in Installing Oracle Solaris 11 Systems.
Convert a JumpStart profile to an AI manifest.

AI uses XML manifest files to define client installation information. Use the js2ai utility to convert both JumpStart rules and their associated profiles to AI criteria and manifests. See Customizing an AI Installation.
Convert the sysidcfg configuration to system configuration (SC) profile specifications.

The sysidcfg file keywords must be converted to SC profile specifications. AI uses SMF XML profile files to specify this configuration. See Chapter 10, Provisioning the Client System, in Installing Oracle Solaris 11 Systems and ai_manifest(4). For information about migrating from JumpStart to AI, see Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11 Automated Installer.

Skip Navigation Links
Exit Print View
	Transitioning From Oracle Solaris 10 to Oracle Solaris 11 Oracle Solaris 11 Information Library