Prerequisite Scanner Configuration Files - IBM Prerequisite Scanner User Manual

Prerequisite Scanner configuration files

The IBM Prerequisite Scanner configuration files for individual platforms contain
the prerequisite properties and their expected values for each platform that is
supported by the product. Prerequisite Scanner provides a predefined set of
configuration files that you can edit. You must create configuration files for new
products and platforms to be supported.
When the operating system of the machine is supported, Prerequisite Scanner
checks the prerequisite properties in the configuration files. It can also check in
only the sections associated with that operating system.
Configuration files have a .cfg file extension. You store them in the ips_root/<OS>
directory, where <OS> is the name of the operating system type, for example,
Windows or UNIX_Linux.
Configuration files must adhere to the following rules:
v File extension must be .cfg
v Naming convention for the file name:
product_code[_<version>].cfg
where:
– product_code
It is the variable to represent a product code on either Windows or UNIX
systems. Product codes identify the product, an individual platform such as
Windows, AIX, HP-UX, Linux, and Solaris, and optionally the version of the
operating system that is supported by that product. They are stored in the
codename.cfg file. Any product that supports multiple platforms has multiple
product codes, with each one identifying a product, platform, and version of
the operating system as required.
– <version> is the 8-digit code to represent the version, release, modification,
and level, with two digits for each part of the code; for example, 7.3.21 is
07032100.
v Group prerequisite properties under sections that must follow a naming
convention for the section titles.
v Standard format for each prerequisite property is a name value pair with
optional qualifiers, and only one property on each line:
[<prefix_identifier>.]<property_name>[.<suffix_identifier>]=
[[<qualifier_name>:<qualifier_value>]]<property_value>
Example of a configuration file without sections
This example checks for prerequisite properties but does not differentiate between
different prerequisite properties for the required operating system versions.
os.space.var=[dir:root=/var/ibm/common/acsi,unit:MB]1.0
os.space.usr=[dir:root=/usr/ibm/common/acsi,unit:MB]200
os.space.home=[dir:non_root=USERHOME/.acsi_HOST,unit:MB]200
os.space.tmp=30MB
env.classpath.derbyJAR=False
network.pingSelf=True
network.pingLocalhost=True
network.availablePorts.Derby=4130
OS Version=RedHat Enterprise Linux 4.*,RedHat Enterprise Linux 5.*
os.package.compat-libstdc++-33=compat_libstdc++_33
os.package.libgcc=libgcc-3.4.3-9
Chapter 1. Prerequisite Scanner overview
13