Advanced Installation Topics

Set Up or Update the Software Source

For a more complete discussion of this task, refer to the "Ignite-UX Custom Configurations Files" document, specifically the "Installation configurations using Software Distributor depots" and the "Configuration for software to be installed" sections. To access this document see the following web page:

http://www.docs.hp.com/en/IUX/infolib.html

This section is limited in scope and does not attempt to address fully what can become a complex task.

Ignite-UX offers many options for installing software on clients. The basic option is to install all software from SD depots on the server. This section describes how to set up the software to install on the Ignite-UX server.

If you plan to use both SD sources and non-SD sources (tar, cpio, or pax), reference the applicable section below for each source type.

For SD Software

HP recommends you copy the depots you want to use to disk rather than using the CD/DVD drives as the source for installation.

Follow these steps to make an SD source available to Ignite-UX:

For more information, see ignite(5).

For Non-SD Software

If the software source is not an SD depot, the make_config command is not applicable. You must create a unique configuration file that represents the non-SD software. An example configuration file is found here: /opt/ignite/data/examples/noncore.cfg

Copy this file and make edits to it as instructed in the comments contained in the file. Then use the manage_index command to insert a reference to your new configuration in the /var/opt/ignite/INDEX file. Use of configuration files is described in Chapter 10. For more information, see the Installing and Updating Ignite-UX White Paper, available on the "Information Library" page of the Ignite-UX website at

http://www.docs.hp.com/en/IUX/infolib.html

Add Optional Applications

If you have other SD-packaged software you want to install onto clients, and you want to make the software available for selection in the Ignite-UX interface, run the make_config and manage_index commands on those depots.

	IMPORTANT: Inclusion of multiple versions of Veritas Volume Manager from Symantec (VxVM) in the same installation depot, or in separate depots that are used together in a single cold-installation session, is not supported. Doing so generates errors when attempting to use the installation depot or during reboot when using non-SD depots. For more information, see “Considerations When Using Veritas Volume Manager from Symantec”.

For SD Application Software

Run the following commands for each SD depot you plan to install software from during the installation. The make_config command only handles SD software packaged in bundle form. All software supplied by HP is packaged in this form. For more information about making SD bundles in an SD depot, see make_bundles(1M).

To make compiler depot bundles available, as superuser enter the following commands:

Replace the depot server name (in this example server.corp.com) with the server from which you plan to install SD software. You can omit the server name to use the server where this command is being executed. The depot server can be a different system from the Ignite-UX server.

	TIP: You must rerun the make_config command each time you add or modify software in the depot. Be aware that if you customize any configuration file created by make_config, your customizations are lost when you recreate it with make_config.

The make_config command constructs Ignite-UX configuration files that correspond to SD depots. When an SD depot is used as part of the Ignite-UX process, it must have a configuration file that describes the contents of the depot to Ignite-UX. This command can automatically construct such a configuration file when it is given the name of an SD depot target. Run this command when you add or change a depot that is to be used by Ignite-UX.

The manage_index utility manipulates the clauses containing configuration file information in /var/opt/ignite/INDEX file. This utility is primarily started by other Ignite-UX tools but can also be started directly. For more information, see manage_index(1M).

For Non-SD Application Software

If the source is not an SD depot, the make_config command is not applicable. You must create a unique configuration file that references the non-SD software. Refer to the sample configuration file (/opt/ignite/data/Rel_release/examples/noncore.cfg), which illustrates a noncore archive.

	NOTE: Do not attempt to use golden images (such as layered applications) that contain files that get installed in /var/adm/sw/*. Delivering files to this directory in this method can corrupt the SD database.