Installing Custom OS Updates

The N1 System Manager also enables you to install OS updates that don't use the standard patch, package, or RPM update commands, such as .tgz, .tar, .Z, or .zip files. Examples of files you can install include:

• Complete software packages or libraries

• Custom RPM files or variants of RPM installs not supported by N1 System Manager

• Executable images or scripts

• Image files, such as .jpg or .gif files

• Text files

The overall process to copy and install standard OS updates using N1 System Manager is the same for custom OS updates, with the following exceptions:

• When copying custom OS updates to the management server using the create update command, the osupdatetype=other attribute is required with the create update command and an installation script is mandatory.

• The OS update's metadata is not automatically extracted during the copy, so you must provide the description, vendor, and version attribute values or they will be empty.

• When installing a custom OS update, the native OS update mechanisms are not used. Instead, the installation script is used and you are responsible for making sure it works properly.

• You cannot use the unload update command to uninstall a custom OS update, since there is no support to specify an uninstall script when copying the OS update.

• When installing Solaris packages, the pkgadd command in the installation script must explicitly specify the admin file to use for the install. The admin file's name will be source-filename.admin, where source-filename is the name of the actual source file used in the create update command.