IBM Maximo Asset Management, Version 7.6

Programmatically verifying prerequisites from the command-line.

You can use the prerequisite verification utility from the command-line to verify that installation program prerequisites are present on a system. Use this utility before you start the product installation programs.

About this task

When started from the command line, the prerequisite verification utility accepts various parameters. The prerequisite verification utility must be run on the system that hosts the prerequisite to check. You cannot use this utility to check prerequisites on a remote system.
Table 1. System verification parameters
Parameters Details
-component Specifies the type of component to verify. At least one component must be used with the prerequisite verification utility.
dbserver
Use the dbserver parameter to have the prerequisite verification utility check for DB2® prerequisites.
j2eeserver
Use the j2eeserver parameter to have the prerequisite verification utility check for WebSphere® Application Server Network Deployment prerequisites.
pip
Use the pip parameter to have the prerequisite verification utility check for prerequisites that are required by Maximo® Asset Management.  Run the prerequisite verification utility with the pip parameter on the administrative workstation.
asset_mgt_upg
Use the asset_mgt_upg parameter to have the prerequisite verification utility check for prerequisites that are required to connect remotely during configuration. .
rxa
Use the rxa parameter to have the prerequisite verification utility check for prerequisites that are required by Maximo Asset Management.
performance
Use the performance parameter to have the prerequisite verification utility check for prerequisites performance settings for Maximo Asset Management.
Syntax example:
tpae_req_check.bat -component pip

If you do not use the -component parameter, you are prompted to specify components when you use the utility.

Multiple components can be specified as comma-separated values.
-input The prerequisite verification utility can accept a property file as input. The utility verifies property values that are found in the file.

For example, the default DB2 server port parameter is DB2_SERVER_PORT=50000. The prerequisite verification utility verifies that this port is available on the DB2 server host.

The default input property file is tpae.properties, and is found on the middleware installation media in the SystemRequirements directory. Several sample property files are found in the SystemRequirements\sample_property_files directory. These sample property files contain custom values that are defined for particular operating systems. You can copy these property files to the system and modify them, or create your own, before you run the prerequisite verification utility.

Syntax example: 
tpae_req_check.bat -component dbserver -input path to the property file

If you do not use the input parameter when you run the prerequisite verification utility, the utility is run in interactive mode. You are prompted for individual values to be verified.
-mode The prerequisite verification utility can be run in silent or interactive mode.
interactive
By default, the prerequisite verification utility is run in interactive mode. If you do not specify the -mode parameter, the utility defaults to running in interactive mode.
silent
If you use the silent qualifier, you can also use the input parameter and supply a property file. If an input file not provided, default property values are used. The output must also be directed to a file to view the results.
Syntax example: 
tpae_req_check.bat 
-component dbserver 
-mode silent 
-input path to the property file > prereqresults.log
-trace Parameter that is used to specify trace output statements while the utility is running.
None
Selecting this qualifier results in no trace information that is generated while the utility is running.
Verbose
Selecting this qualifier results in detailed trace information that is generated while the utility is running.
Normal
Selecting this qualifier results in default trace information that is generated while the utility is running.
Syntax example: 
tpae_req_check.bat 
-component dbserver 
-trace None

Procedure

  1. Log on to the system you are checking for prerequisites with a user ID that has permission to run scripts on the system.  Ensure that the middleware installation media is mounted or otherwise available to the system. This example procedure uses values that are found in the default tpae.properties file to verify that a system is suitable to host DB2 for a Maximo Asset Management deployment.
  2. Open a command-line window and change directory to the SystemRequirements directory of the middleware installation media.
  3. Run the prerequisite verification utility. Specify the component to check and the property file to use. 
    tpae_req_check.bat 
-component dbserver 
-input d:\SystemRequirements\tpae.properties
    In this example, the tpae.properties file is in the same directory as the tpae_req_check.bat script.

Results

After the prerequisite verification utility successfully completes the verification task, results are printed to the screen.
CTGIN8117I : The Tivoli Pre-requisite Scanner has been launched.
CTGIN8118I : The Tivoli Pre-requisite Scanner exited with the return code
IBM Prerequisite Scanner
    Version  : 1.0.34
    Build    : 20101109
    OS Name  : Microsoft Windows Server 2003, Enterprise Edition Service Pack 2
    User Name: Administrator

Machine Info
   Machine name : MYMACHINE
   Serial Number: KKKKKK0
   OS Serial    : 66666-666-6666666-66666

PAE [not defined] [version 07500000]:
Property                                Result  Found                                   Exp...
========                                ======  =====                                   ===...
os.totalPhysicalMemory                  PASS    2.00GB                                  1.90GB
network.hasFQDN                         FAIL    False                                   True 
Disk#1 (C:\ibm\tivoli\mwi\workspace)    PASS    27.99GB                                 300MB
Disk#2 (C:\Temp\1)                      PASS    27.99GB                                 1000MB
Disk#3 (C:\Temp\1)                      PASS    27.99GB                                 250MB
network.availablePorts.db2              PASS    135,445,1025,2967,3389,5800,5900,139    50000
network.availablePorts.ctginst          PASS    135,445,1025,2967,3389,5800,5900,139    50005 
Disk#4 (C:\Program Files\IBM\SQLLIB)    PASS    27.99GB                                 1.40GB

ALL COMPONENTS :
Property            Result     Found     Exp...
========            ======     =====     ===...
C:                  PASS       27.99GB   2.91GB

Prereq Scanner Overall Result: FAIL
prereq_checker.bat 1

These values can also be redirected to a file when you start the command from the command line.

If any of the verification steps report a failure, resolve the issue and rerun the verification utility before you install Maximo Asset Management components.

The Table 2 table contains a list of the properties checked. Use this information to analyze prerequisite verification utility results.
Table 2. Prerequisite verification utility properties
Property Description
browser.Version Checks browser version.
CpuArchitecture Verifies that the machine architecture is supported.
network.availablePorts.* Verifies that required ports are available.
The following example checks to ensure a port that is required by DB2 is available.
network.availablePorts.db2inst=50000
network.dns Verifies that there is a DNS entry for the system on the DNS server.
network.fqdn Verifies that the system host name is fully qualified.
os.architecture Verifies that the operating system architecture is supported.
os.dir.tmp/home Verifies required permissions for the system directories
os.FreePagingSpace Verifies that adequate free paging space is available on the system.
os.iodevicestatus Verifies the I/O device status of the system.
os.kernelversion Checks kernel version.
os.lib.* Verifies that a prerequisite library is available on the system.
os.mountcheck Checks for the existence of nosuid on the file system.
os.MozillaVersion Checks browser version.
os.package.atk Verifies a prerequisite library that is required for GTK on AIX® is available on the system.
os.package.cairo Verifies a prerequisite library that is required for GTK on AIX is available on the system.
os.package.expat Verifies a prerequisite library that is required for GTK on AIX is available on the system.
os.package.fontconfig Verifies a prerequisite library that is required for GTK on AIX is available on the system.
os.package.freetype2 Verifies a prerequisite library that is required for GTK on AIX is available on the system.
os.package.gettext Verifies a prerequisite library that is required for GTK on AIX is available on the system.
os.package.glib2 Verifies a prerequisite library that is required for GTK on AIX is available on the system.
os.package.gtk2 Verifies a prerequisite library that is required for GTK on AIX is available on the system.
os.package.libjpeg Verifies a prerequisite library that is required for GTK on AIX is available on the system.
os.package.libpng Verifies a prerequisite library that is required for GTK on AIX is available on the system.
os.package.libtiff Verifies a prerequisite library that is required for GTK on AIX is available on the system.
os.package.pango Verifies a prerequisite library that is required for GTK on AIX is available on the system.
os.package.pixman Verifies a prerequisite library that is required for GTK on AIX is available on the system.
os.package.rpm Verifies that prerequisite packages are available on the system.
os.package.xcursor Verifies a prerequisite library that is required for GTK on AIX is available on the system.
os.package.xft Verifies a prerequisite library that is required for GTK on AIX is available on the system.
os.package.xrender Verifies a prerequisite library that is required for GTK on AIX is available on the system.
os.package.zlib Verifies a prerequisite library that is required for GTK on AIX is available on the system.
os.RAMSize Reports system RAM available.
os.SeaMonkeyVersion Checks browser version.
os.SELinux Determines whether selinux is enabled.
os.ServicePack Verifies that required service packs are installed on the system.
os.shell.default Determines the default shell for users.
os.space.* Determines disk space availability for various file systems.
The following example shows the check that is made for the middleware installation program workspace.
os.space.var=[dir:root=/var,unit:MB]512
os.totalPhysicalMemory Reports physical RAM available to the operating system.
os.ulimit Identifies user limits that are configured on the system.
OS.Version Reports the operating system type and version.
Parent topic: Before you begin

Feedback