This fix pack is a cumulative fix release and addresses several APARs and internally found issues since the release of IBM Tivoli Netcool/Impact Fix Pack 9.
18.104.22.168 Release addresses the problems that have been reported in IBM Tivoli Netcool/Impact version 7.1, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, and 188.8.131.52. This is a Fixpack only release and not a refresh of full installer (Impact 184.108.40.206 was both). It can only be applied on a previous Impact 7.x release (7.1, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, and 22.214.171.124).
Note: Impact 126.96.36.199 Release is both a Fixpack and also GA Install Refresh Release. If you are planning to Install Impact 7.1.x for the first time, you can do a direct 188.8.131.52 Full Install and then can apply Impact 184.108.40.206 on top of it (Instead of starting with Impact 220.127.116.11). For those migrating from previous releases (5.1.1 or 6.1/6.1.1), you can install Impact 18.104.22.168, migrate directly to 22.214.171.124 and then apply 126.96.36.199 Fixpack.
You can access the Impact 188.8.131.52 README here:
The following table contains a list of files included in this Fix Pack and operating systems associated with these files:
all platforms * 7.1.0-TIV-NCI-FP0010.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:
2.0 Hardware and software requirements
For information about supported hardware and software, check the Software Product Compatibility Reports (SPCR) here:
And the Planning Section in the Netcool/Impact Administration Guide:
4.0 Additional information
For Tivoli Netcool/Impact 184.108.40.206 Documentation, please refer to:
As of NOI 220.127.116.11 Q1 2017 / Impact 18.104.22.168, Impact will no longer automatically create indexes on the events history table for the filter date column (FIRSTOCCURRENCE by default) and the Identity field for Seasonality. It is the responsibility of the database admin to construct (and maintain) appropriate indexes on the REPORTER history database. It is recommended to review the filter fields for the reports as a basis for an index, plus review if an index is required for Identity fields.
5.0 List of APARs
5.1 Fixes (APARs) Included in this Fix Pack
The following Netcool/Impact APARs are delivered with Fix Pack 10:
IV90149: NEWEVENT() FUNCTION NOT WORKING PROPERLY WHEN USING AN OMNIBUS EVENT READER WHICH USES THE USEDEVIANTFIELDS PROPERTY
IV90914: THE RESTFUL API DSA DOESN'T INTERPRET THE URL PARAMETER VALUE CORRECTLY WHEN IT CONTAINS AN EQUAL SIGN
IV91528: SNMPGETACTION() FUNCTION: THE IBMSNMPCOMMUNICATOR TRIES TO PARSE THE SNMP TIMETICK AS A SIGNED 32BIT INTEGER
IV91670: LIST WIDGET FILTER IS LOST WHEN USING LARGE DATA MODEL
IV92243: IMPACT ESCAPES ONLY FIRST INSTANCE OF EQUAL SIGN
IV92416: A JS POLICY THAT GETS A NULL VALUE FROM A DB OUTPUTS UNEXPECTED VALUE
IV92997: DATABASE EVENT READER SERVICE SKIPS EVENTS
IV93180: TIMESTAMP DATA FROM DATABASES WITH MICROSECONDS CAUSES CORRUPTION
IV93181: TIMESTAMP VALUE WITH MILLISECS DOES NOT CONTAIN THEM IN DASH TABLE
IV93442: OPTION TO ALLOW DERBY TO BIND TO A HOST DIFFERENT TO SYSTEM HOSTNAME
IV93663: CHANGES REQUIRED FOR MANUAL/SEMI AUTOMATED RUN BOOKS, SUCH THAT ONLY ONE FIRST EVENT ENTRY IS RECORDED IN THE JOURNAL
IV93756: DOWNLOAD FROM RELATED/SEASONAL EVENTS EXPORT NOT WORKING WITH LOAD BALANCER
IV93881: LIMIT WAIT TIME FOR CHECKPOINT TO PREVENT OUT OF MEMORY CONDITION
IV93941: SYNTAX CHECKER FOR JSP POLICIES
IV94205: SOCKET DSA TO BE ADDED IN IMPACT 7.1 STARTING WITH FP10
IV94819: ACTIONS.0.RESTRICTED=TRUE IMPACT POLICY ACTION DOES NOT WORK CONSISTENTLY
IV94887: ADD ADDITIONAL CIPHER SUPPORT TO IMPACT
IV95469: NEED TO DETECT A BAD CERTIFICATE EARLY IN THE FIX PACK INSTALL PROCESS
IV97414: INSTALL OF FIX PACK 9 FAILS DUE TO TIMING ISSUE WITH INSTALLER SHUTDOWN OF IMPACTSERVER
List of Impact APARs that have documentation updates or have additional information:
IV89602: MAPROLES.SH CAUSES A LIBERTY STOP/RESTART
IV91598: MORE DETAILS ON PERL CGI SCRIPT IN THE "XMLHTTPTESTPOLICY"
IV92506: RESTFULAPI POLICY SAMPLE CODE IN DOCS PRODUCES SYNTAX ERROR
IV92980: SECONDARY IMPACT FAILS TO INSTALL
IV92997: DATABASE EVENT READER SERVICE SKIPS EVENTS
To check the APARs that were part of the previous FixPack (22.214.171.124), please check this link:
6.0 New support and features
6.1 Browser Support with Fix Pack 10
Impact 126.96.36.199 supports:
Firefox ESR 52
Internet Explorer 11
6.2 Component Updates
Java has been updated to version 188.8.131.52
WebSphere Application Server Liberty has been updated to version 184.108.40.206
CURI integration component to the TWL 220.127.116.11-build->irm-09Dec2016-irm_patch1 level
6.3 Enhancements in Fix Pack 10
Fix Pack includes the following enhancements:
· Impact Audit feature.
This feature can be enabled via the the <Server>_server.props file on the Impact etc directory.
The following are new parms available within the <Server>_server.props file:
If enableaudit is set to true, there will be a <Server_Name>_impactauditor.log file created and written to (within the Impact logs directory)
This feature encompasses the following RFEs:
1. Auditing feature required in Impact :
2. Add audit log for privileged/admin user accounts
3. Script to enable easier retrieval of the subversion audit information
7.0 Known Issues in Fix Pack 10
If the IBM Runbook Automation (IBM RBA) has been previously enabled on Impact (before Fix Pack 10), the Fix Pack 10 installer does not properly update the RBA_ManageTriggers.js file. To address this issue, perform the following actions:
1. Backup the <installdir>/policy/*_RBA_ManageTriggers.js
2. Copy the RBA_ManageTriggers.js file from
3. Rename the <installdir>/policy/RBA_ManageTriggers.js file to have the name it previously had <installdir>/policy/*_RBA_ManageTriggers.js
The Datatype RBA_Status needs to be refreshed after fix pack update. To do so, do the following:
1. In the Data Model tab, select the RBA_Status Data type for editing.
2. Select Refresh Fields Button.
3. Ensure the Key field is set to Yes for both the Serial and Identifier rows. If they say No, double click on this table entry and select the checkbox that appears in edit mode.
3. Save the Datatype chages and close the editor.
This is a Fixpack only release and not a refresh of full installer (Impact 18.104.22.168 was both). It can only be applied on a previous Impact 7.x release (7.1, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199 and 188.8.131.52 ).
Note: Impact 184.108.40.206 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 220.127.116.11 Full Install and then can apply Impact 18.104.22.168 on top of it (Instead of starting with Impact 22.214.171.124). For those migrating from previous releases (5.1.1 or 6.1/6.1.1), you can install Impact 126.96.36.199, migrate directly to 188.8.131.52 and then apply 184.108.40.206 Fixpack.
3.0 Installation information
Note 1: If you plan to install 220.127.116.11 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.
Note 2: Starting with Impact 7.1.0 Fix Pack 10, a new utility is now available (and run automatically right before the update). This is the Impact server Health Check utility! This utility will perform an overall Health Check of Impact, prior to allowing the update installer to continue with the update. The utility is also available as a standalone utility; which can be retrieved via the following url:
This fixpack is a cumulative fixpack, in other words you can apply it to any of the previous 7.x releases (7.1, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, and 126.96.36.199) including Intermix Fix releases (IF2, IF3 and IF4) for both Impact Core and Impact for NOI releases.
Note: If you plan to install 188.8.131.52 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>-FP0010.zip file to your system.
2. Create a directory Impact_FP10 for example.
3. Unzip the file 7.1.0-TIV-NCI-<ARCH>-FP0010.zip to directory Impact_FP10.
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)
NOTE: Starting with Fix Pack 10, before the Fix Pack is installed; an overall Impact server Health Check is performed. This process may take some time to complete; depending on environmental conditions. Depending on the outcome of the Health Check, the installer will continue or abort the Fix Pack installation process. The installation process will not be allowed to start, unless all Health Check conditions are met. If issues are detected by the Health Check process; information will be shown on the noted logs. General information can be found here:
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 1: If you are rolling back to Impact 184.108.40.206 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:
Note 2: If during rollback, you intent to skip multiple Fix Packs (for example, after upgrading from FP4 to FP5, and then to FP5 to FP7, and then FP10; and then rollback from FP10 all the way to FP4); you could potentially run into an issue where start/stop scripts for either Impact GUI and Impact server may no longer function properly. To correct the issue; run the restore_from_backup script (described above). Better yet, it is best to roll back one Fix Pack level at a time!
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:
IV97414 IV95469 IV94887 IV94819 IV94205 IV93941 IV93881 IV93756 IV93663
IV93442 IV93181 IV93180 IV92997 IV92416 IV92243 IV91670 IV91528 IV90914
IV90149 IV91598 IV92980 IV92506 IV90731 IV89602 IV87831 IV89098 IV89129
IV89131 IV89286 IV89440 IV89979 IV90657 IV90875 IV91187 IV91260 IV91519
IV91549 IV91629 IV91636 IV91667 IV93611 IV90657 IV89440 IV85425 IV86760
IV87141 IV87548 IV87550 IV87987 IV88599 IV88725 IV88858 IV89194 IV89225
IV89384 IV89390 IV89410 IV89415 IV89425 IV89467 IV89653 IV89676 IV89768
IV89930 IV90357 IV90438 IV90659 IV89537 IV89425 IV89570 IV89847 IV90243
IV90408 IV89003 IV88914 IV87838 IV87240 IV87089 IV86146 IV87164 IV86919
IV86725 IV86762 IV86040 IV86253 IV84106 IV85981 IV85849 IV85669 IV85535
IV85284 IV84955 IV84125 IV85746 IV85304 IV84274 IV84201 IV84121 IV84040
IV83829 IV83725 IV83663 IV83127 IV83051 IV82945 IV82909 IV82883 IV82584
IV81912 IV81745 IV81409 IV80388 IV79350 IV81745 IV82883 IV83051 IV83127
IV81226 IV84040 IV81409 IV81625 IV82945 IV75602 IV78525 IV78678 IV79004
IV79133 IV79363 IV79827 IV79867 IV79910 IV80038 IV80183 IV80613 IV80747
IV80800 IV80818 IV80891 IV81135 IV81155 IV81630 IV81644 IV75734 IV79086
IV79133 IV79631 IV72531 IV74071 IV74485 IV74878 IV75552 IV75913 IV76395
IV76875 IV77882 IV77953 IV78327 IV79776 IV79806 IV60062 IV65958 IV66441
IV66950 IV68163 IV68195 IV68934 IV69164 IV69904 IV70656 IV70712 IV70836
IV71068 IV71157 IV71513 IV71554 IV72091 IV72486 IV72561 IV72673 IV73098
IV73376 IV73620 IV74071 IV74211 IV74300 IV74421 IV74765 IV75085 IV70628
IV68912 IV74334 IV70784 IV69906 IV55989 IV59886 IV60438 IV61084 IV61538
IV61725 IV61956 IV62792 IV63137 IV63138 IV63535 IV63942 IV64075 IV64152
IV64837 IV65055 IV65179 IV66164 IV66210 IV66337 IV67091 IV67829 IV67936
IV68383 IV55600 IV66968 IV67231 IV67839 IV67936 IV83358 IV83071 IV81613
Problems (APARS) fixed
Problems (APARS) fixed
23 June 2018