Required Checks And Extension Tasks For Unix Systems; Checks And Tasks Before Using A Configuration File For Unix Systems - IBM Prerequisite Scanner User Manual

Table 12. Checks and tasks before using a configuration file for Windows systems (continued)
Check
For any new prerequisite properties, check whether
h
predefined collectors can collect the actual values for
the prerequisite properties.
For any new or edited prerequisite properties, check
h
whether predefined evaluators can compare the
expected and actual values for the prerequisite
property.
Ensure all files have been saved in the correct
h
directories:
v Configuration files, any custom product-specific
collectors and associated batch files, and any
custom evaluator files in the ips_root/Windows
directory
v Custom common collectors in the ips_root/lib
directory

Required checks and extension tasks for UNIX systems

You should perform a set of prerequisite checks and tasks before you run the IBM
Prerequisite Scanner. These checks determine whether you can edit and use
existing configuration files or you must extend Prerequisite Scanner.
Table 13 provides a list of required checks and tasks to perform.
Table 13. Checks and tasks before using a configuration file for UNIX systems
Check
Check whether the product is listed in the
h
codename.cfg file.
Check whether a configuration file exists for the
h
product code associated with the product.
Open the configuration file and check whether it
h
contains the correct prerequisite properties.
Check whether the prerequisite properties have the
h
expected values.
40
Prerequisite Scanner: User's Guide
Task
v If yes, perform the next check.
v If no, create custom collectors. For more
information, see "Creating custom collectors for
Windows systems" on page 46.
v If yes, perform the next check.
v If no, create custom evaluators. For more
information, see "Creating custom evaluators for
Windows systems" on page 53.
Run the Prerequisite Scanner. For more information,
see Chapter 4, "Running Prerequisite Scanner," on
page 59.
Task
v If yes, perform the next check.
v If no, add a product code to the codename.cfg file.
For more information, see "Adding product codes"
on page 41.
v If yes, perform the next check.
v If no, create a configuration file to contain the
prerequisite properties for all supported platforms
of the product. For more information, see
"Creating custom configuration files" on page 41.
v If yes, perform the next check.
v If no, add prerequisite properties. For more
information, see "Adding prerequisite properties"
on page 43.
v If yes, run the Prerequisite Scanner. For more
information, see Chapter 4, "Running Prerequisite
Scanner," on page 59.
v If no, edit the prerequisite properties. For more
information, see "Editing prerequisite properties"
on page 45.