IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 5(7.1.0-TIV-NCI-FP0005)

Download Description

**********************************************************
* NOTE !! Before installing this Fix Pack, a health check script MUST be
* executed. The purpose of this Health Check, is to detect potential issues
* on the environment, prior to the installation of a Fix Pack. Failing to
* perform a Health Check, could potentially affect the Fix Pack installation
* process; which might lead to a failed Fix Pack install. The health check
* script can be downloaded from the fixcentral link, detailed at start
* installation instructions below.
*
* A change introduced by this Fix Pack might negatively
* affect existing product function.
*
* Please refer to APAR IV90357 for a description of the
* problem and corrective action.
*
* Please refer to APAR IV89653 for a description of the
* problem and corrective action.
*
* Please refer to APAR IV86760 for a description of the
* problem and corrective action. IMPACTUI DOES NOT HANDLE EAST
* ASIAN LANGUAGE IN UI DATA PROVIDER POLICY RELATED ACTIONS
*
* Evaluate these APARs for the potential impact in your environment.
*************************************************************

7.1.0.5 Release addresses the problems that have been reported in IBM Tivoli

Netcool/Impact version 7.1, 7.1.0.1, 7.1.0.2, 7.1.0.3 and 7.1.0.4. This is a Fixpack only release and not a refresh of full installer. It can only be applied on a previous Impact 7.x release (7.1, 7.1.0.1, 7.1.0.2, 7.1.0.3 and 7.1.0.4).

The following table contains a list of files included in this Fix Pack and operating systems associated with these files:


Platform File

AIX * 7.1.0-TIV-NCI-AIX-FP0005.zip
Linux * 7.1.0-TIV-NCI-LINUX-FP0005.zip
Solaris * 7.1.0-TIV-NCI-SOLARIS-FP0005.zip
Windows * 7.1.0-TIV-NCI-WINDOWS-FP0005.zip
zLinux * 7.1.0-TIV-NCI-ZLINUX-FP0005.zip

all platforms * 7.1.0-TIV-NCI-FP0005.README

Note: The installer only works for 64 bit architectures
Note: Whenever <ARCH> is used in the text of this readme, as part of the
filename of the Fix Pack package, it refers to, and can be
substituted for one of the following operating systems:

* AIX
* Linux
* Solaris
* Windows
* zLinux


Hardware and software requirements
For information about supported hardware and software, check the

Software Product Compatibility Reports (SPCR) here:
http://www-969.ibm.com/software/reports/compatibility/clarity/index.html

And the Planning Section in the Netcool/Impact Administration Guide:
http://www-01.ibm.com/support/knowledgecenter/SSSHYH_7.1.0.5/com.ibm.netcoolimpact.doc/admin/imag_start_c.html

Additional information
For Tivoli Netcool/Impact 7.1.0.5 Documentation, please refer to:

http://www-01.ibm.com/support/knowledgecenter/SSSHYH_7.1.0.5/com.ibm.netcoolimpact.doc/welcome_kc.html

List of APARs
Fixes (APARs) Included In this Fix Pack.

The following Netcool/Impact APARs are delivered with Fix Pack 5:

IV75602: DERBY REPLICATION DOES NOT WORK CONSISTENTLY BETWEEN IMPACT CLUSTER MEMBERS
IV78525: JAVASCRIPT SYNTAX CHECKER FLAGS LINE INCORRRECTLY AS AN ERROR
IV78678: UNABLE TO CREATE NEW UI PROVIDER DATA TYPES WHEN THE DATASET NAMES CONTAIN NEWLINES
IV79004: DIRECTSQL ON OPERATOR VIEW POLICY DOESN'T WORK AFTER FP1
IV79133: EVENT READER STOPS WHEN OBJECT SERVER BECOMES UNAVAILABLE AND DOES NOT RECOVER:REGRESSION
IV79363: STARTING TIME FOR POLICY ACTIVATOR SERVICES IS NOT CORRECTLY LOGGED
IV79827: WEBSERVICE LISTENER IMPLEMENATION TO WORK SAME WAY ON IMPACT 511 IN IMPACT
IV79867: COMMAND LINE METHOD TO DELETE IMPACT ITEM (POLICY/SERVICE) IS NOT WORKING
IV79910: REXTRACTALL FUNCTION DOES NOT RETURN MATCHING CONTENT :REGRESSION
IV80038: ERROR GENERATED WHEN LOG POLICY FUNCTION USED WITH NULL ORGNODE
IV80183: POLICYLOGGER ON SECONDARY DON'T GET UPDATE IT
IV80613: WITH IMPACT POLICY, OUTPUT OF SNMPGETNEXTACTION IS GARBLED
IV80747: THE PARAMETER SECURITYTOKENFROMREQUEST HAS THE SESSION INFORMATION
IV80800: POLICY CHAINING NOT FUNCTIONAL IN 7104: REGRESSION
IV80818: POST MIGRATING TO 710 POLICY PROCESSING TIME DETERIORATED: REGRESSION
IV80891: POLICY LOGGER THROWS EXCEPTIONS WHEN PROCESSING SQL PARAMETERS TO LOG
IV81135: JAVA ISSUE AFTER INSTALLING FP4 FOR IMPACT 7.1 :REGRESSION: AIX
IV81155: WEB SERVICES DSA INTERMITTENT CLASS NOT FOUND EXCEPTION
IV81630: USING THE NCI_EXPORT UTILITY ON A IMPACT 7.1 INSTALL, WHICH IS ON A SOLARIS OPERATING SYSTEM, RESULTS IN AN ERROR
IV81644: UNABLE TO CREATE RE/SE CONFIGURATION WHEN USING MSSQL DATABASE
IV83071: INCORRECT ENTRIES FOR NWEEKDAYOFMONTH FIELD BY POLICY OPVIEW_ADDRWIN
IV83358: ATTEMPTING TO ADD A RECURRING MWM WINDOW FOR ALL NTH WEEKDAY OPTIONS PRODUCES ERROR REGARDING THE DERBY FIELD SIZE
IV81613: NCI_TRIGGER REPORTS SUCCESS WHEN INCORRECTLY RUN AGAINST A NON-EXISTENT POLICY

List of Impact APARs that have documentation updates or have additional information:

IV75734: ERROR HANDLING NOT HANDLE BY POLICY EXECUTED FROM POLICY ACTIVATOR
IV79086: LACK OF DETAILED DESCRIPTION OF FEDERATING LDAP
IV79133: EVENT READER STOPS WHEN OBJECT SERVER BECOMES UNAVAILABLE AND DOES NOT RECOVER:REGRESSION
IV79631: RUNPOLICY FUNCTION IN IMPACT 7.1 DOC NEEDS TO BE CORRECTED IN SOME PLACES

To check the APARs that were part of the previous FixPack (7.1.0.4), please check this link:

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Netcool%20Impact/page/Impact%207.1.0.4%20README


Browser Support with Fix Pack 5
Impact 7.1.0.5 supports:

Firefox ESR 38
Internet Explorer 10 and 11

Component Updates
1. Java has been updated to version 7.0.9.30
2. Websphere Liberty has been updated to version 8.5.5.6 + PI45266 + PI52103 + PI56455 + PI55670 + PI47476


Enhancements in Fix Pack 5
Fix Pack includes the following enhancements:

Maintenance Mode Windows (MWM)
• MWM: Ability to edit existing Maintenance Mode Windows
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=39325
• MWM: Ability to Sort Column Data (Ascending/Descending) order by clicking the Column Header
• MWM: New MWM User Role called impactMWMUser was added to allow Read/Write Access only to MWMs created by a specific user. This is in addition to the impactMWMAdminUser provided in Impact 7104 that allows access to all Maintenance Mode Windows.
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=21122
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=31779


Operator Views
• New Operator View User Role called impactSelectedOpViewUser to allow access only to selected Operator Views. This addresses the requirements raised for these RFEs:
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=46810
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=15793
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=39324

• Operator View access auditing by logging Operator View related activities in opviewaudit.log

UI Provider
• Ability to customize the Topology widget layout.
• Ability to set Nodes links with different status than the child node

User Interface
• Ability to search data in the rows/columns of the View Data Items Page
• Updated Error messages and Dialogs

Install
• Autostartup scripts to configure Impact, GUI and JRExec servers to autostart on machine reboot
• Added support for RHEL 7.2, SUSE 12 SP1 and Solaris 11.3


Service Level Objectives (SLO) Reporting Enhancements
The information in this section applies only if you have deployed the Impact Solution called "Service Level Objectives (SLO) Reporting". The following changes were made for Fixpack 5:
• Addition of a primary key column for SLO_CONFIGURATION table added in Fixpack 4.
• Miscellaneous fixes and performance improvements, including improved design for sample policies that collect data from the TBSM Metric History database.

This function is documented on the following page in the Knowledge Center: http://www-01.ibm.com/support/knowledgecenter/SSSHYH_7.1.0.5/com.ibm.netcoolimpact.doc/solution/imsg_slo_reporting_c.html?lang=en

If you have not deployed this solution, then you can skip this section.

Update the SLORPRT database schema using the following steps:

a) You will need access to the machine where the SLORPRT database was installed. If this database has not been installed, then the SLO solution has not been deployed and there is no need to continue this update to the schema.
b) It is recommended to make a backup of the SLORPRT database before continuing.
c) Copy sql files needed to update the SLORPRT database schema:

If you have not previously installed Fixpack 3, copy files add_timezone.sql and update_views_timezone.sql from [InstallDirectory]/impact/add-ons/slo/db to a location accessible from the system you will use to update the database schema in the next step.

If you have not previously installed Fixpack 4, copy file slo_utility.sql from [InstallDirectory]/impact/add-ons/slo/db to a location accessible from the system you will use to update the database schema in the next step.

Copy file slo_configuration_pkey.sql from [InstallDirectory]/impact/add-ons/slo/db to a location accessible from the system you will use to update the database schema in the next step.

d) Open a DB2 command window on a system with access to the SLORPRT database and run the following commands based on what you have previously installed:

db2 connect to SLORPRT user dbuser using dbpassword
(replace dbuser and dbpassword with the user/password specified in datasource SLOReportDatasource )


If you have NOT previously installed Fixpack 3

db2 -tvf <slo_sql_dir>/add_timezone.sql

db2 -tvf <slo_sql_dir>/update_views_timezone.sql

db2 -tvf <slo_sql_dir>/slo_utility.sql

If you have not previously installed Fixpack 4

db2 -tvf <slo_sql_dir>/slo_utility.sql

If you have previously installed Fixpack 4

db2 -tvf <slo_sql_dir>/ slo_configuration_pkey.sql


db2 connect reset

Where <slo_sql_dir> would be [InstallDirectory]/impact/add-ons/slo/db if on the same machine as the Impact server, or the directory where you copied the files in step c if the SLORPRT database is on a different machine.