Customizing an XML AI Manifest File

Use the following procedure to create and apply a custom XML AI manifest file:

How to Customize an XML AI Manifest File

Copy an existing AI manifest.
When you create an AI install service, that install service has a default AI manifest. See Chapter 8, Setting Up an Install Server for information about creating an install service.
1. List existing manifests.
  Use the installadm list command to see what AI manifests you already have associated with a particular install service.
```
$ installadm list -m -n solaris11_1-i386
Service/Manifest Name  Status   Criteria
---------------------  ------   --------
solaris11_1-i386
   orig_default        Default  None
```
2. Retrieve a copy of a specific manifest.
  Use the installadm export command to extract the contents of this default manifest or any other AI manifest that has been added to this service.
```
$ pfexec installadm export -n solaris11_1-i386 -m orig_default -o mem1.xml
```
  A copy of orig_default is now in the file mem1.xml.
Modify the manifest copy.
Modify mem1.xml, adding tags and values according to the information in the ai_manifest(4) man page.
Add the new manifest to the install service.
Add the new AI manifest to the appropriate AI install service, specifying criteria that define which clients should use these installation instructions.
```
$ pfexec installadm create-manifest -n solaris11_1-i386 -f ./mem1.xml -m mem1 \
-c mem="2048-unbounded"
```
You can specify multiple -c options or one -C file. See Chapter 9, Customizing Installations and the set-criteria subcommand for information about specifying client criteria.
```
$ installadm list -m -n solaris11_1-i386
Service/Manifest Name  Status   Criteria
---------------------  ------   --------
solaris11_1-i386
   orig_default        Default  None
   mem1                         mem  = 2048 MB - unbounded
```
- Make the new manifest the default.
  You can designate any manifest file or derived manifests script to be the default manifest or script for a service. To change the default among manifests and scripts that you have already added to the service, use the -o option with the set-service subcommand.
```
$ pfexec installadm set-service -o default-manifest=mem1 solaris11_1-i386
$ installadm list -m -n solaris11_1-i386
Service/Manifest Name  Status   Criteria
---------------------  ------   --------
solaris11_1-i386
   orig_default        Inactive None
   mem1                Default  (Ignored: mem  = 2048 MB - unbounded)
```
  In this example, the original default is now inactive because it has no criteria to specify which clients should use it. Only the default manifest or script can have no client selection criteria and still be active.
- Add the new manifest as the default.
  If you want to add a new default manifest or script for this service, use the -d option with create-manifest. Any criteria specified are stored and ignored until another manifest is made the default.
```
$ pfexec installadm create-manifest -n solaris11_1-i386 -d \
-f ./region1.xml -m region1
$ installadm list -m -n solaris11_1-i386
Service/Manifest Name  Status   Criteria
---------------------  ------   --------
solaris11_1-i386
   orig_default        Inactive None
   mem1                         mem  = 2048 MB - unbounded
   region1             Default  None
```
- Customize an existing manifest.
  Use the installadm update-manifest command to change the content of an existing manifest or script without adding a new manifest or script. Criteria, default status, and the manifest name or the script name are not changed as a result of the update.
```
$ pfexec installadm update-manifest -n solaris11_1-i386
    -f ./newregion1.xml -m region1
```
Validate the customized manifest.
The create-manifest and update-manifest subcommands syntactically validate the XML manifest files before adding them to the install service. AI semantically validates the AI manifests at client installation time.

Note - If an invalid manifest is provided to a client, the automated installation aborts. To investigate the cause of the validation failure, see the /system/volatile/install_log on the client.

See also Maintaining an Install Server for more information about the installadm list, export, create-manifest, set-criteria, update-manifest, and set-service subcommands.

Skip Navigation Links
Exit Print View
	Installing Oracle Solaris 11.1 Systems Oracle Solaris 11.1 Information Library