Download
Abstract
This Fix Pack will address problems found in Netcool/Impact V7.1.0
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 IV97414 for a description of the
* problem and corrective action.
*
* Please refer to APAR IV90875 for a description of the
* problem and corrective action.
*
* Evaluate these APARs for the potential impact in your environment.
*************************************************************
7.1.0.8 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, 7.1.0.4, 7.1.0.5, 7.1.0.6, and 7.1.0.7. This is a Fixpack only release and not a refresh of full installer (Impact 7.1.0.4 was both). 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, 7.1.0.4, 7.1.0.5, 7.1.0.6, and 7.1.0.7).
Note: Impact 7.1.0.4 Release is both a Fixpack and also GA Install Refresh Release. If you planning to Install Impact 7.1.x for the first time, you can do a direct 7.1.0.4 Full Install and then can apply Impact 7.1.0.8 on top of it (Instead of starting with Impact 7.1.0.1). For those migrating from previous releases (5.1.1 or 6.1/6.1.1), you can install Impact 7.1.0.4, migrate directly to 7.1.0.4 and then apply 7.1.0.8 Fixpack.
You can access the Impact 7.1.0.4 README here:
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-FP0008.zip |
| Linux | 7.1.0-TIV-NCI-LINUX-FP0008.zip |
| Solaris | 7.1.0-TIV-NCI-SOLARIS-FP0008.zip |
| Windows | 7.1.0-TIV-NCI-WINDOWS-FP0008.zip |
| zLinux | 7.1.0-TIV-NCI-ZLINUX-FP0008.zip |
all platforms * 7.1.0-TIV-NCI-FP0008.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
2.0 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:
4.0 Additional information
For Tivoli Netcool/Impact 7.1.0.8 Documentation, please refer to:
http://www.ibm.com/support/knowledgecenter/SSSHYH_7.1.0.8/com.ibm.netcoolimpact.doc/welcome_kc.html
5.0 List of APARs
5.1 Fixes (APARs) Included in this Fix Pack
The following Netcool/Impact APARs are delivered with Fix Pack 8:
IV85425: SELFMONITORING OF MEMORY - NCI_MEMORY - NOT WORKING IN REDHAT 7
IV86760: IMPACTUI DOES NOT HANDLE EAST ASIAN LANGUAGE IN UI DATA PROVIDER POLICY RELATED ACTIONS
IV87141: UNEXPECTED RESULTS AFTER CREATING AND/OR EDITING WEEK OF THE MONTH AND DAY OF THE WEEK, WITHOUT HITTING BACK BUTTON FIRST
IV87548: EXCESSIVE LOGGING WITHIN THE IMPACTSERVER.LOG REGARDING THE EXITING AND DISABLING OF HIBERNATIONS
IV87550: SELFMONITORING SERVICE STATUS NOT WORKING
IV87987: HANDLE UNEXPECTED OUTPUT FROM COMMAND RESPONSE
IV88599: WHEN ENTERING AN OUTAGE USING 'NODE IN' WITH A SIGNIFICANT NUMBER OF NODES, THE COLUMN CONTINUES TO WIDEN
IV88725: DATA TYPE EDITOR REPLACING PERCENT CHARACTERS WITH PARTIAL HTML
IV88858: IMPACTWEBSERVICEUSER ROLE MISSING FROM MAPROLES.SH
IV89194: NOI: PG_PROCESSTYPES POLICY SENDING FLOOD OF ERRORS
IV89225: NOI: OLD DATA NOT REMOVED FROM RELATEDEVENTS.RE_GROUPASC
IV89384: NOI: SEASONALITY 'REVIEWED BY' COL VAL LOST AFTER CONFIG RE-RUN
IV89390: NOI: StackOverFlow in RE_STARTPROCESSING.js
IV89410: NOI: DB field mapping problem with Event Types configuration in defaults file
IV89415: NOI: While Processing Event Types with PG_PROCESSTYPES need to escape special characters in SQL values
IV89425: DATABASEEVENTREADER TO NULLIFY SIMPLEDATEFORMAT CONVERSION IF REQUIRED
IV89467: BACKUP DERBY NOT STARTING IN SLAVE MODE: 710
IV89653: NOI: RELATED EVENT PROCESSING FAILS ON RE-RUN OF CONFIGURATION
IV89676: SNMP OID NOT READABLE
IV89768: IMPACT 7.1 Status data type is not returning all available status to widgets
IV89930: NOI: GROUP SOURCES PORTLET TIMING OUT WITH 'FAILED TO LOAD DATA!'
IV90357: FEDERATEDREPOSITORY BREAKS LDAP/SSO CONNECTION IN IMPACT
IV90438: NOI: RUNNING OUT OF ORACLE CONNECTIONS WHEN QUERYING TIMESTAMP DATA
IV90659: NOI: COMBINED REPORT, SEASONAL AND RELATED EVENT FAILS
List of Impact APARs that have documentation updates or have additional information:
IV89537: NOI: ROLLUPS FORMAT CORRECTION NEEDED IN "UPDATING ROLLUP CONFIGURATION" CHAPTER
IV89425: DATABASEEVENTREADER TO NULLIFY SIMPLEDATEFORMAT CONVERSION IF REQUIRED
IV89570: TROUBLESHOOTING MIGRATION ISSUES WHEN DATATYPE CONTAINS A RESTRICTED CHARACTER
IV89847: DESCRIPTION OF IV85849 ON REXTRACT FUNCTION IS CONFUSING
IV90243: WHEN SET THE NOPASSVARIABLE VARIABLE TO TRUE, BUILT-IN VARIABLES NO LONGER WORK
IV90408: STATS(TIMES FIRED,TIMES FIRED IN LAST MONTH, LAST FIRED) NOT BEING UPDATED
To check the APARs that were part of the previous FixPack (7.1.0.7), please check this link:
6.0 New support and features
6.1 Browser Support with Fix Pack 8
Impact 7.1.0.8 supports:
Firefox ESR 45
Internet Explorer 11
6.2 Component Updates
Java has been updated to version 7.0.9.60
WebSphere Application Server Liberty has been updated to version 16.0.0.3
6.3 Enhancements in Fix Pack 8
Fix Pack includes the following enhancements:
· Custom Status attributes create unique granularity of Node's Status. This feature can be configured globally and made available for all datasets through server.props.
At the same time, it can be configured locally for individual datasets through properties files, allowing also to selectively (locally) override the global configuration
Install
· LDAP based authentication – support for Custom LDAP Attributes
· Runbook Automation (RBA) – Automated scripts to ease setup process
DASH
· Supports DASH 3.1.2.1 CP6
7.0 Known Issues in Fix Pack 8
· When using LDAP based authentication with more than one repositories, if any one of them is unreachable (ex: Network cable is out, Network Interface card is corrupted etc), then there could be problems during server initialization.
Note: This is only if one or more LDAP servers are unreachable. In this case, even a ping from the machine where Impact server is running to the target LDAP server machine hangs and never returns back.
Once the network communication problem in the machine where LDAP server is setup gets resolved, it should fix the Impact server startup issue. The other option is to comment out the rogue LDAP server information from ldapRegistry.xml and only use the LDAP server which is running and reachable.
· Event Analytics: Re-running a configuration with a changed profile strength creates two separate profiles. Currently there is no clean up of the Impact data to remove the groups from the older profile. As a result, changing the profile strength of a configuration results in the same configuration having different profiles, for example Weak and Strong.
To avoid this issue, run a new configuration with a different profile strength instead of re-running the same configuration. You can use the same criteria as the original and change only the profile strength to Weak, Medium, or Strong.
Prerequisites
This is a Fixpack only release and not a refresh of full installer (Impact 7.1.0.4 was both). 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, 7.1.0.4, 7.1.0.5, 7.1.0.6, and 7.1.0.7).
Note: Impact 7.1.0.4 Release is both a Fixpack and also GA Install Refresh Release. If you planning to Install Impact 7.1.x for the first time, you can do a direct 7.1.0.4 Full Install and then can apply Impact 7.1.0.8 on top of it (Instead of starting with Impact 7.1.0.1). For those migrating from previous releases (5.1.1 or 6.1/6.1.1), you can install Impact 7.1.0.4, migrate directly to 7.1.0.4 and then apply 7.1.0.8 Fixpack.
Installation Instructions
***********************************************************************************************************************************
* Before installing this Fix Pack, it is recommended to run the following health check script to verify the system.
*
* See Fix Central:
http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Netcool+Impact&fixids=impact_server_health_check&source=SAR
*
* If any problem is reported by this script, it is essential that these are resolved before the Fix Pack is installed.
*
* Instructions for running Health Check Scripts:
* 1. unpack the zip to <Impact Install Directory>/install/configuration/cfg_scripts
* 2. For UNIX, make the script executable with either:
* chmod u+x impact_server_health_check.sh
* or
* chmod 744 impact_server_health_check.sh
* 3. Execute either the bat or sh script, from <Impact Install Directory>/install/configuration/cfg_scripts
* 4. For UNIX, run using
* <Impact Install Directory>/install/configuration/cfg_scripts/impact_server_health_check.sh
* 5. For WINDOWS , run using
* <Impact Install Directory>/install/configuration/cfg_scriptsimpact_server_health_check.bat
* 6. Scripts are successful, if the following is seen:
* On Unix:
* checkownership completed successfully!
* BUILD SUCCESSFUL
* On Windows:
* BUILD SUCCESSFUL
* Only install the Fix Pack if the script is successful.
* 7. Please NOTE!!!
* The Health Check will recycle the Impact server, therefore, it's recommended that you only run it during
* scheduled downtime.
*
* The Impact 7.1.0 FP 10 installer, will automatically run the same logic.
* Please refer to APAR IV95469 for a description of the problem and corrective action.
*
***********************************************************************************************************************************
3.0 Installation information
Note: If you plan to install 7.1.0.8 from Passport Advantage, the version of Installation Manager on your machine should be 1.8.3 or higher. Older Installation Manager (1.7.3 for example) will not work because of older SSL code.
3.1 Dependencies
This fixpack is a cumulative fixpack, in other words you can apply it to any of the previous 7.x releases (7.1, 7.1.0.1, 7.1.0.2, 7.1.0.3, 7.1.0.4, 7.1.0.5, 7.1.0.6, 7.1.0.7) including Intermix Fix releases (IF2, IF3 and IF4) for both Impact Core and Impact for NOI releases.
Note: If you plan to install 7.1.0.8 from Passport Advantage, the version of Installation Manager on your machine should be 1.8.3 or higher.
3.2 Before you begin applying the Fix Pack
1. Backing up Directories
To apply this Fix Pack you will need 3 GB of free disk space
Check Instructions mentioned here:
2. Backup the entire Impact directory
This Fix Pack does not backup the entire Impact application. It only makes a backup of Impact configuration files.
A backup copy of Impact configuration files is located at [ImpactInstallDirectory]\backup\install
3.3 Extracting Fix Pack files
3.3.1 Extracting on Linux, Solaris, AIX , Windows and zLinux platforms
1. Copy the 7.1.0-TIV-NCI-<ARCH>-FP0008.zip file to your system.
2. Create a directory Impact_FP8 for example.
3. Unzip the file 7.1.0-TIV-NCI-<ARCH>-FP0008.zip to directory Impact_FP8.
3.3.2 Fix pack directories
When you extract the Fix Pack file, the following directories are created:
ImpactExtRepository (Contains Impact Extensions for NOI, Server and GUI Server updates)
ImpactRepository (Contains Impact Server and GUI Server updates)
response files (Contains response files for silent update)
scripts files (Contains installer update files)
and the following files are available:
update_console.sh (Update in console mode)
update_gui.sh (Update in GUI mode)
update_silent.sh (Update in Silent mode)
3.3.3 Installing Fix Pack in GUI and Console Mode
Check Instructions Here:
3.3.4 Installing Fix Pack in Silent Mode
Check Instructions Here:
3.4 Installation in a Cluster Environment
Stop all Impact servers in a cluster environment before and after each update.
Example: A two server cluster would be updated as follows:
Stop all servers in the cluster
Update the primary
Stop the primary
Update the secondary
Stop the secondary
Start the primary
Start the secondary
3.5 Post Fix Pack Considerations
The Browser cookies and cache should be cleaned up before launching the UI. If you are using IE and have the Impact URL saved to your Favorites, then you must ensure that the "Preserve Favorites website data" is not enabled.
3.6 Rollback to previous version
You can remove the Fix Pack by doing a rollback to a previous version.
This rollback process is different from uninstall which removes Impact product entirely.
Check instructions here:
Note: If you are rolling back to Impact 7.1.0.1 or 7.1 GA, you must not run the Rollback feature directly from Installation Manager. Instead, the rollback scripts (rollback_gui/rollback_console) and restore script (restore_from_backup) scripts located at IMPACT_HOME/install/rollback should be run. Details here:
3.7 Recovering from a failed Fix Pack installation
Check instructions here:
3.8 Policies overwritten by this Fix Pack
When applying Test Fixes and Interim Fixes/Fix Packs to an existing system, the policies
provided by Netcool/Impact may be overwritten with newer versions to fix issues. If these policies contain custom changes, you will need to update these newer files with the custom changes.
If you are using a Netcool Operations Insight (NOI) install, the following policies would be overwritten:
NCI_acknowledgeSeasonalReportEntry.js
NCI_ConfigureResults.js
NOI_Constants.js
NCI_NOI_DB2QUERY.js
NCI_NOI_MSSQLQUERY.js
NCI_NOI_ORACLEQUERY.js
NCI_NOI_GETANALYTICSCONFIG.params
NCI_NOI_UTILS.js
NCI_PG_GETTYPES.js
NCI_PG_GETALLTYPES.js
NCI_PG_GETGENERALIZEDPATTERNS.js
NCI_PG_GETGENERALIZEDPATTERNS.params
NCI_PG_GETPATTERN.js
NCI_PG_PROCESSPATTERNS.js
NCI_PG_PROCESSTYPES.js
NCI_PG_SAVEPATTERN.js
NCI_PG_SAVEPATTERN.params
NCI_PG_UTILSGROUP.js
NCI_RE_ACT_GROUPSYNTHETIC.js
NCI_RE_CONFIGURE.js
NCI_RE_GETCONFIGS.js
NCI_RE_GETCONFIGS_ACTIVE.params
NCI_RE_GETCONFIGS_ARCHIVED.params
NCI_RE_GETCONFIGS_EXPIRED.params
NCI_RE_GETCONFIGS_WATCHED.params
NCI_RE_GETGROUPEVENTS.js
NCI_RE_GETGROUPINSTANCES.js
NCI_RE_GETGROUPINSTANCEV1.js
NCI_RE_GETGROUPS.js
NCI_RE_GROUPSOURCES.js
NCI_RE_PROCESS.js
NCI_RE_STARTPROCESSING.js
NCI_RE_RULE.js
NCI_RE_UTILS.js
NCI_seasonalityProcess.js
NCI_seasonalityStartProcessing.js
NCI_seasonalEventDatasource.js
NCI_SE_CONFIGRULES.js
NCI_SE_GETRULES.js
NCI_SE_GETRELATEDEVENTS.js
NCI_SE_GETHISTORICALEVENTS.js
NCI_SE_PROCESSCONFIG.js
NCI_SE_RULE_DAY_OF_WEEK_CONFIDENCE.js
NCI_SE_UTILS.js
NCI_unacknowledgeSeasonalReportEntry.js
NCI_visualizeDayOfWeek.js
and the following are the new policies shipped for a NOI install:
NCI_NOI_CLEANUP_REPORTS.js
NCI_NOI_MANAGE_EXPORT.js
NCI_NOI_MANAGE_EXPORT.params
NCI_NOI_MANAGE_EXPORT_DATASETS.js
NCI_NOI_MANAGE_EXPORT_DATASETS.params
NCI_NOI_MANAGE_EXPORT_FILES.js
NCI_NOI_MANAGE_EXPORT_STATUS.js
NCI_NOI_MANAGE_EXPORT_STATUS.params
NCI_NOI_MANAGE_TOKENS.js
NCI_NOI_MANAGE_TOKENS.params
NCI_PG_REGEX_FIELD_VALUES.js
NCI_PG_REGEX_FIELD_VALUES.params
NCI_SE_REINSERTDATA.js
NCI_SE_REINSERTDATA.params
Problems (APARS) fixed
Problems (APARS) fixed
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg24042885