Setting Up Additional Software on the Server

After you have successfully installed and configured your Ignite-UX server, you might want to set up additional software on the server for installation on clients. Commands written for this task handle Software Distributor (SD) depots and bundles, but it is possible to configure Ignite to install non-SD software.

The commands that make SD software available for Ignite are capable of sweeping actions, such as packaging an entire software CD/DVD and then making additions to all configuration clauses of a specified release. These commands may also be used to fine tune a single configuration clause with a single software addition. Care must be taken when using these commands to get the results you want.

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

For a complete discussion, see Ignite-UX Custom Configuration Files available on http://www.docs.hp.com/en/IUX/infolib.html. Look for the sections “Configuration for software to be installed” and “Installation configurations using Software Distributor depots.”

SD Software

Generally speaking, all software supplied by HP for HP-UX is packaged in SD form. Use the steps below to make SD software available to Ignite-UX for installation on clients.

If the software is not in a depot, put it in one. The make_depots command copies SD bundles to a depot for use by Ignite-UX. See make_depots(1M) for more information. For ease of maintenance, HP recommends copying the depots to disk rather than using CD/DVD drives as the source for installation.
Run make_config on all the depots you plan to use. The make_config command creates configuration files for software in a depot. See make_config(1M). You must run make_config each time you add or modify software in your depot. Be aware that any customizations you've made to a configuration file are lost when you recreate a configuration file with make_config.
Use manage_index to add configuration files to configuration clauses in the INDEX file. See manage_index(1M).

Example: Create a configuration for compiler software

Given an SD depot of complier software on another server, this example creates a configuration file for that software and adds it to all configuration clauses for the B.11.31 release.

# make_config -s server:/depots/compiler \
      -c /var/opt/ignite/data/Rel_B.11.31/compiler_cfg
# manage_index -a -f /var/opt/ignite/data/Rel_B.11.31/compiler_cfg




	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”.

Non-SD Software

To make non-SD software sources (tar, cpio, or pax archives) available to Ignite-UX, use the example configuration file /var/opt/data/examples/noncore.cfg.

Make a copy of the /var/opt/data/examples/noncore.cfg file and edit it for your particular software. The file contains extensive comments to help you make the changes you need.
Use manage_index to add configuration files to configuration clauses in the INDEX file. See manage_index(1M).




	IMPORTANT: Do not use archives with files in `/var/adm/sw/` as software sources. Delivering files to `/var/adm/sw/` can corrupt the SD Installed Product Database.

Setting Up Additional Software on the Server

Technical documentation

» Table of Contents

» Glossary

» Index

SD Software

Example: Create a configuration for compiler software

Non-SD Software