Creating Custom Vbscript Collectors Specific To A Product And Product Version - IBM Prerequisite Scanner User Manual

Creating custom VBScript collectors specific to a product and
product version
When you create custom product-specific VBScript collectors, the file name must
be the same product code as the configuration file and stored in the/Windows
subdirectory. The collector can contain code to gather actual values for one or
many prerequisite properties. It can also use the common functions and sub
routines to gather those values if required.
Before you begin
Ensure that you review the set of functions and sub routines in the following
appendixes before you create the collectors. Determine whether you can use any of
them to obtain the actual values:
v Appendix E, "Common functions for Windows systems," on page 113
v Appendix G, "File utility sub routines for Windows systems," on page 129
v Appendix F, "Logging utility sub routines for Windows systems," on page 127
v Appendix H, "Other common functions and sub routines for Windows systems,"
Determine whether the collector must check that the prerequisite property exists
and if it does, what other information must be gathered. Each check must return a
value, whether one exists. For example:
v Check whether the directory exists.
v Check the available disk space for a directory.
v Check whether a product is installed.
v Check what version of the product is installed.
Procedure
1. Create a VBScript file. Save the file in the ips_root/Windows directory, with a
2. Using a VBScript editor, open the file and include the path to the
3. If you must use the values of the PATH and -p flag passed from the Prerequisite
48
Prerequisite Scanner: User's Guide
on page 131
variant of the following file naming convention:
product_code[_version].vbs
where:
v 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.
v 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.
common_function.vbs if you must use common functions, as follows:
Include("..\lib\common_function.vbs")
Scanner, then use Wscript.Arguments() where Wscript.Arguments(0) is the
value for PATH. Wscript.Arguments(1) is the -p flag and its values.