IBM Prerequisite Scanner User Manual page 31

– prefix_identifier is the prefix identifier for a predefined category of prerequisite
properties as outlined in Table 3 on page 4. This prefix identifier is required
by some of the predefined categories, for example, env.
– property_name is the prerequisite property name, for example, tcrhome.
Store this type of VBScript collector in the ips_root/lib directory.
v Naming convention for the custom product-specific VBScript collector file
It contains properties to be made available to a specific product and product
versions, that is, one configuration file:
product_code[_<version>].vbs
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.
Store this type of VBScript collector in the ips_root/Windows directory.
v Standard output for each prerequisite property is as follows:
WScript.Echo "property_name=" & <var_for_value>
– property_name that represents the prerequisite property as written in the
configuration file, for example, env.tcrhome.
– var_for_value, that is, the VBScript variable for the actual value that the
collector obtains for the prerequisite property.
For example, the following standard output writes the prerequisite property for
the Tivoli Common Reporting home environment variable and its actual value:
WScript.Echo "env.tcrhome=" & tcr_home
Collectors for UNIX systems
Collectors for UNIX systems are run in the relevant Shell host environment for
either AIX, HP-UX, Linux, or Solaris. They use the commands and options specific
to that platform to access elements of the host environment.
Each UNIX collector obtains data for a prerequisite property or a prerequisite
property with predefined subtypes. The collector writes the result of the check for
the prerequisite property as standard output. Prerequisite Scanner writes this
standard output to a temporary text file.
You can create custom UNIX collectors to collect data for custom prerequisite
properties. Each collector, predefined or custom, is called in the
ips_root/UNIX_Linux/packageTest.sh file.
When you run the Prerequisite Scanner, it runs the collectors in the following
order: predefined collectors with _plug in the file name in the ips_root/lib
directory; predefined collectors in the ips_root/UNIX_Linux directory; and the
custom UNIX collectors in the ips_root/UNIX_Linux directory.
Chapter 1. Prerequisite Scanner overview
21