Create the HP-UX OE Configuration Information on the Ignite-UX Server

Create the configuration file, named core_media_cfg, to describe this HP-UX OE depot, named core_media. In this example we are using HP-UX 11i v2, but this process can easily be customized for any HP-UX release by substituting your release information for the HP-UX 11i v2 information.

If you want more than one configuration available for a version of HP-UX, such as 11i v2 June, 2008 and 11i v2 December, 2007, then each configuration must have a unique name for the configuration file created with make_config in this step and the configuration clause created and modified by manage_index in Step 2.

If you wish, you may safely complete the section “Configure the System as an Ignite-UX Server” before this one.

Procedure

# /opt/ignite/bin/make_config -s /var/opt/ignite/depots/Rel_B.11.23/core_media \
  -c /var/opt/ignite/data/Rel_B.11.23/core_media_cfg

Common Errors

ERROR: Depot depot_name does not exist.

Diagnosis: The depot name was mistyped.

Correction: Check the make_config command line for typos.

Explore

List the /var/opt/ignite/data/Rel_B.11.23 directory to see the core_media_cfg file just created with the make_config command.

Configuration files are typically named after the depot, with a _cfg appended.

This process is described fully in the section on creating the configuration file to describe the depot in the Ignite-UX Custom Configuration Files web-only document, available at http://docs.hp.com/en/IUX/infolib.html.

Add the configuration information to the Ignite-UX /var/opt/ignite/INDEX file. First, the default B.11.23 configuration clause is copied to a new clause called “B.11.23 From OE Media”, and then the core_media_cfg file we created in step 1 is added to the “B.11.23 From OE Media” clause.

If you want more than one configuration available for a version of HP-UX, such as 11i v2 June, 2008 and 11i v2 December, 2007, then each configuration must have a unique name for the configuration file created with make_config in Step 1 and the configuration clause created and modified by manage_index in this step.

Procedure

# /opt/ignite/bin/manage_index -n "HP-UX B.11.23 Default" \
  -c "B.11.23 From OE Media"
# /opt/ignite/bin/manage_index -a \
  -f /var/opt/ignite/data/Rel_B.11.23/core_media_cfg \
  -c "B.11.23 From OE Media"

Common Errors

NOTE: Cannot access index file /var/opt/ignite/INDEX: No such file or directory.

ERROR: Couldn't accomplish the requested operation.

Diagnosis: The /var/opt/ignite/INDEX file is missing or mistyped.

Correction: Check for typos. Otherwise, list the /var/opt/ignite directory to see if the INDEX file is there under another name. Check with a systems administrator responsible for the Ignite-UX server to find the correct INDEX file.

Explore

This process is described fully in the section on creating a minimalist cfg clause for installation in the Ignite-UX Custom Configuration Files web-only document, available at http://docs.hp.com/en/IUX/infolib.html.

View the description of the “B.11.23 From OE Media” configuration clause to see that it is the same as the default clause we copied, “HP-UX B.11.23 Default”. Note that when no INDEX file is specified, the manage_index command defaults to /var/opt/ignite/INDEX.

# manage_index -x -c "B.11.23 From OE Media"

Change the description to something that makes sense to you.

# manage_index -c "B.11.23 From OE Media" -y "B.11.23 0712 OE"

See manage_index(1M).

Create the HP-UX OE Configuration Information on the Ignite-UX Server

Technical documentation

» Table of Contents

» Glossary

» Index