As in in the previous section, there are several ways to deal with this:

∙Always place the applications depot into the core OE depot. This also assumes a different version of VxVM/VxFS is not available on the application media - you can’t cold install a different version of VxVM/VxFS to the version available from the core OE media.

∙Use the load_order keyword to change the load order of the depots so that the applications depot is always loaded after the core OE depot and before any other depots. The core OE depot is always loaded at load order 0, and by default other depots are loaded at load order 5. Change the applications depot so it has a load order of 1 to 4 to ensure it is loaded before the vPars software.

It is important to understand the impacts of the choices you make when deciding how your depots and configuration will be laid out.

Other software could be affected in similar ways to this vPars example.

Resolving applications that are not in SD format

There are two solutions when you find that you have an application that is not in SD format:

∙Package an application in SD format

∙Define an application in a non-SD format

The following topics describe both solutions.

Package an application in SD format

You could learn how to write an SD product specification file (psf) for use with swpackage to produce an SD depot of your application. Learning how to write a PSF can be difficult and time consuming. For information regarding the creation of PSF files, see Software Distributor Administration Guide for HP-UX 11i.

Alternatively, you can use the HP Software Package Builder (SPB) product makes it easy to package applications into SD format. SPB provides a window into the software package structure, showing attributes that can be set for each package element.

You can find SPB product information and download it from the HP Software Depot at:

http://software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=SwPkgBuilder

Once you have the software in SD format, using either solution, you can:

1.copy it into a depot;

2.run make_config to generate a config file;

3.then run manage_index to add the configuration file to the desired cfg clause in

/var/opt/ignite/INDEX.

Important:

SD depots must contain software in bundles after you have packaged the software. If it is not packaged at the bundle level, you will have to create a bundle for it with the make_bundles command.

179