Skip to main content

Prerequisite Scanner: What's New in Version 1.2.0.3


News


Abstract

Prerequisite Scanner Version 1.2.0.3 provides enhancements, including new and modified prerequisite properties and configuration files. It also contains fixes for defects and service requests, previously known as PMRs.

Content



Removal of the Microsoft .NET Framework prerequisite

Previous versions of Prerequisite Scanner required an existing installation of Microsoft .NET Framework on Windows systems. This prerequisite has removed in Prerequisite Scanner Version 1.2.0.3.

Removal of temporary prerequisites for Windows 2012 support

In the Prerequisite Scanner Version 1.2.0.2, Prerequisite Scanner had a temporary set of prerequisites for Windows 2012 support, that is, either install Microsoft .NET Framework Version 3.5 or use a Windows activation configuration script. For Prerequisite Scanner Version 1.2.0.3, the VBScript code no longer uses the System.Collections.ArrayList class. Prerequisite Scanner no longer requires these prerequisites to support Windows 2012.

Support for Jazz for Service Management

Prerequisite Scanner provides a set of convenience scripts in the ips_root/JazzSMScripts directory that specify the required and optional parameters to run Prerequisite Scanner and scan for the prerequisites required for each installation scenario and server topology.

This table outlines the convenience scripts for each Jazz for Service Management installation scenario. For more information about running these convenience scripts, see the Jazz for Service Management Information Center.

Attention: The Prerequisite Scanner configuration files for Jazz for Service Management contain default values for installation paths, thereby assuming that you install the integration services and middleware to these default installation locations.

Jazz for Service Management convenience scripts

Installation scenario

Jazz for Service Management server

Installed integration services

Convenience script

Custom installation (two server topology) Database server only

Registry Services database

Scenario1_DB_Server.sh|bat
  Composite server (enterprise and UI and reporting servers)

Administration Services application

Administration Services UI

Dashboard Application Services Hub

Registry Services application

Security Services

Tivoli Common Reporting

Scenario1_EntUI_Server.sh|bat
Simple installation (single server topology) Combined database, enterprise, and UI server

Database and all integration services

Scenario2_Typical.sh|bat
Simple installation (single server topology) Combined database, enterprise, and UI server

Database and the integration services except Tivoli Common Reporting

Scenario2_Typical_NoTCR.sh|bat
Custom installation (three server topology) Database server only

Registry Services database

Scenario3_DB_Server.sh|bat
  Enterprise server only

Administration Services application

Registry Services application

Security Services

Scenario3_Ent_Server.sh|bat
  UI and reporting server only

Administration Services UI

Dashboard Application Services Hub

Tivoli Common Reporting

Scenario3_UI_Server.sh|bat

Documentation changes in this fix pack

Prerequisite Scanner Information Center is not updated for Version 1.2.0.3. This news announcement describes all updates that would otherwise be included in the information center.

Fixed defects

For a list of defects fixed in this fix pack, see the Readme.html file in the ips_root directory.

Known issues

For a list of known issues in this fix pack, see the Readme.html file in the ips_root directory.

This table summarizes new configuration files that were added to the ips_root\Windows and ips_root/UNIX_Linux directories.

New configuration files

File name

Platforms

Product version, platform, operating system

Introduced in

AMA_07000000.cfg All Security Access Manager Authorization Server 1.2.0.3
AMP_07000000.cfg All Security Access Manager Policy Server 1.2.0.3
AMW_07000000.cfg All Security Access Manager WebSEAL 1.2.0.3
DSH_03010000.cfg All Dashboard Application Services Hub Version 3.1 1.2.0.3
ESS_01010000.cfg All Security Services in Jazz™ for Service Management Version 1.1 1.2.0.3
FAS_01010000.cfg All Administration Services in Jazz for Service Management Version 1.1 1.2.0.3
FRS_01010000.cfg All Registry Services in Jazz for Service Management Version 1.1 1.2.0.3
ODP_01010000.cfg All Common prerequisites in Jazz for Service Management Version 1.1 1.2.0.3
TCR_03010000.cfg All Tivoli Common Reporting Version 3.1 1.2.0.3

This table summarizes the modified configuration files to support feature enhancements or documentation and code fixes in the ips_root\Windows and ips_root/UNIX_Linux directories.

Modified configuration files

File name

Platforms

Product version, platform, operating system

Modified in

BSM_06010100.cfg All Tivoli Business Service Manager Version 6.1.1 1.2.0.3–Updated prerequisite properties
NCI_06010100.cfg All Tivoli Netcool/Impact Version 6.1.1 1.2.0.3–Updated prerequisite properties
DMO_07020000.cfg UNIX Prerequisite Scanner demo Version 7.2 1.2.0.3–Renamed from DMO_0720000.cfg
DMO_07050000.cfg UNIX Prerequisite Scanner demo Version 7.5 1.2.0.3–Renamed from DMO_0750000.cfg
NOC_07030100.cfg All Tivoli Netcool/OMNIbus server components and desktop component Version 7.3.1 1.2.0.2–Renamed from NOC_07310000.cfg
NOD_07030100.cfg All Tivoli Netcool/OMNIbus desktop component Version 7.3.1 1.2.0.2–Renamed from NOD_07310000.cfg
NOS_07030100.cfg All Tivoli Netcool/OMNIbus server components Version 7.3.1 1.2.0.2–Renamed from NOS_07310000.cfg
BSM_06010000.cfg All Tivoli Business Service Manager Version 6.1 1.2.0.1–Renamed from BSM_06100000.cfg
NCI_06010000.cfg All Tivoli Netcool/Impact Version 6.1 1.2.0.1–Renamed from NCI_06100000.cfg
PAE_07050000.cfg All Tivoli Process Automation Engine Version 7.5 1.2.0.0–Renamed from PAE_07500000.cfg

This table summarizes the new prerequisite properties added in this fix pack.

Property name

Platforms

Description

Valid Values

Introduced in

numLogicalCPU All

The number of logical processors available to the operating system on the computer. The check can run under the following conditions:

  • On Windows 2003, hotfix 932370 must be installed.
  • On Windows XP, either SP3 and later or hotfix 93270 must be installed.
  • ON UNIX systems, the binary for the command to return the number of logical processors must be available on the local system and set in the PATH environment variable.

Note: This property is not supported on Windows 2000 operating systems.

Number, for example, 2 1.2.0.3

os.isUnixServiceRunning.
daemon_name

UNIX

Checks whether the daemon_name daemon or service is running on the machine. daemon_name represents the following daemon processes or services for which the tool checks:

  • SSHD for the sshd daemon process

The tool requires that the path to the following command, which checks the status of the daemon process or service, is set in the PATH environment variable:

  • On AIX systems: lssrc
  • On Linux systems: service
  • On HP-UX: ps
  • On Solaris: svcs

Note: If the tool runs the scan on a UNIX system that has the running daemon process or service, it returns a PASS result; otherwise, it returns a FAIL result.

Boolean value, for example:

True

1.2.0.3

os.UACEnabled

Windows

Checks whether User Account Control (UAC) is enabled on the target computer

Note: If the tool runs the scan on a Windows system that does not have this security component, it returns a FAIL result, with [Not Found] as the actual value.

Boolean value, for example:

True
1.2.0.3

This table summarizes the prerequisite properties modified in this and previous fix packs.

Modified prerequisite properties

Property name

Platforms

Description

Modified in

numCPU

All

The number of independent physical processors on the computer. If the tool scans the computer and does not find any physical processors, it returns a Not Found result.

Restriction: The prerequisite property is not supported on HP-UX 11i v2, Linux virtual machines, Linux for System z®, and POWER® hardware.

Valid values

Number, for example, 4

1.2.0.3

DB2 Version

All

The version of DB2® that is currently installed on the machine

Valid values

The value can be any of the following types:

  • String, for example: v9.5.100.179FP4
  • Comma separated list of strings, for example: v9.1 FP1+, V9.5 FP0+

You can use the + special character with the fix pack number to indicate a fix pack of this level or later is acceptable. For example, FP5+, checks whether fix pack 5 or later is installed.

Important: Unlike other properties that use the + special character to check for that version number or later, this property supports the special character on the fix pack number only. For example, if you specify an expected value of v9.5+, and you have DB2 Version 9.7 installed, the check fails; If you specify an expected value of V9.7 FP1+, and you have DB2 Version 9.7 FP4 installed, the check passes.

1.2.0.3

Memory

All

The total amount of physical memory that is currently available on the machine.

Tip: Separately check for the amount of physical and virtual memory available by the using predefined prerequisite properties in the operating system category.

On AIX systems only, the following conditions apply:

  • For AIX 5.3 TL9 or later, the prerequisite property checks for the available memory; For AIX 5.3 TL8 or earlier, it checks for the free physical memory.
  • For AIX 6.1 TL2 or later, the prerequisite property checks for the available memory; For AIX 6.1 TL1 or earlier, it checks for the free physical memory.

Valid values

Numeric format in GBs or MBs, for example: 300MB

1.2.0.3

network.
availablePorts.
app_type

All

Use this naming convention for checking whether the TCP port or range of TCP ports are available for the app_type application type. Check which TCP ports are not being listened to, for example:

  • network.
    availablePorts.DB2
    checks TCP ports for DB2 database server, where app_type is DB2
  • network.
    availablePorts.WAS
    checks TCP ports for WebSphere® Application Server, where app_type is WAS

The scan returns the PortsInUse: prefix and list of ports in use, as the actual value. If the expected port is not in the list, then the port is available.

Valid values

Single positive integers, for example:

network.
availablePorts.
WAS = 8080

A range of positive integers, for example:

network.
availablePorts.
DB2 = 50900-50905

1.2.0.3

network.
portsInUse.
app_type

All

Use this naming convention for checking whether the TCP port or range of TCP ports are in use for the app_type application type. Check which TCP ports are being listened to, for example:

  • network.
    portsInUse.DB2
    checks TCP ports for DB2 database server, where app_type is DB2
  • network.
    portsInUse.WAS
    checks TCP ports for WebSphere Application Server, where app_type is WAS

The scan returns the PortsInUse: prefix and list of ports in use, as the actual value.

Valid values

Single positive integers, for example:

network.
portsInUse.
WAS = 8080

A range of positive integers, for example:

network.
portsInUse.
DB2 = 50900-50905

1.2.0.3

network.
UDPavailablePorts.
app_type

All

Use this naming convention for checking whether the UDP port or range of UDP ports are available for the app_type application type. Check which UDP ports are not being listened to, for example:

  • network.
    UDPavailablePorts.TCR
    checks UDP port for Tivoli Common Reporting logging features, where app_type is TCR.
  • network.
    UDPavailablePorts.WAS
    checks UDP ports for multicasting between Tivoli Provisioning Manager for OS Deployment servers, where app_type is TPM_MCAST.

The scan returns the PortsInUse: prefix and list of ports in use, as the actual value. If the expected port is not in the list, then the port is available.

Valid values

Single positive integers, for example:

network.
UDPavailablePorts.
TCR = 9362

A range of positive integers, for example:

network.
UDPavailablePorts.
TPM_MCAST = 10000-10500

1.2.0.3

network.
UDPportsInUse.
app_type

All

Use this naming convention for checking whether the UDP port or range of UDP ports are in use for the app_type application type. Check which UDP ports are being listened to, for example, for example:

  • network.
    UDPportsInUse.TCR
    checks UDP port for Tivoli Common Reporting logging features, where app_type is TCR.
  • network.
    UDPportsInUse.WAS
    checks UDP ports for multicasting between Tivoli Provisioning Manager for OS Deployment servers, where app_type is TPM_MCAST.

The scan returns the PortsInUse: prefix and list of ports in use, as the actual value.

Valid values

Single positive integers, for example:

network.
UDPportsInUse.
TCR = 9362

A range of positive integers, for example:

network.
UDPportsInUse.
TPM_MCAST = 10000-10500

1.2.0.3

os.
isServiceRunning.
service_name

Windows

Checks whether the service_name service is running on the machine. service_name represents the following services for which the tool checks:

  • remoteRegistry for the Remote Registry Service
  • DNSClient for the DNS Client Service
  • terminalServices for Remote Desktop Services or Terminal Services

Note: Ensure this prerequisite property is located after network.UDPportsInUse.
app_type
or network.UDPavailableports.
app_type
prerequisite properties. The os.isServiceRunning.service_name collector uses UDP ports temporarily and might return invalid results for the UDP port prerequisite properties.

Valid values

Boolean value, for example:

True

1.2.0.3

os.kernelversion

UNIX

Checks the release of the kernel for UNIX operating systems

Valid values

String, for example:

  • For AIX 6.1: 6.1.6.2+
  • For HP-UX 11: B.11.23+
  • For Red Hat Enterprise Linux Server 6.0: 2.6.32
  • For Red Hat Enterprise Linux Server 5.x and 6.x: 2.6.*
  • For SUSE Linux Enterprise Server: 2.6.27.19
  • For Solaris 10: 5.10

Note: The check supports using the special characters + and * in the expected value.

1.2.0.3

os.shell.default

Red Hat Enterprise Linux

Checks whether the default system shell script is installed

Valid values

String to represent the default system shell script, for example, bash

1.2.0.3

Related information

Version 1.2.0.2 Information Center
Version 1.2.0.3 Download Document

Product Alias/Synonym

PRS

Rate this page:

(0 users)Average rating

Copyright and trademark information

IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Rate this page:


(0 users)Average rating

Add comments

Document information

IBM Prerequisite Scanner


Software version:
1.2.0.3


Operating system(s):
AIX, HP-UX, Linux, Solaris, Windows


Reference #:
1624769


Modified date:
2013-02-06

Translate my page

Content navigation