General Page
The original release of IBM Tivoli Netcool/Impact Fix Pack 7.1.0.39 was affected by the following issues:
- DT503505: Single Sign On and Console Integration fails after upgrading to 7.1.0.39
- DT504154: Netcool Impact: JavaScript policies stop running when they exceed policy.js.maxinstructioncount
A refreshed Fix Pack 7.1.0.39 package has been published to address these issues.
Attention! Do not install the refreshed Fix Pack 7.1.0.39 over an existing installation of the original Fix Pack 7.1.0.39. The refreshed Fix Pack should be applied only to systems that have not already been upgraded to Fix Pack 7.1.0.39. For systems where the original Fix Pack 7.1.0.39 is already installed, you one of the following resolution options: Resolution Options:
Alternatively, you can roll back the original Fix Pack 7.1.0.39 and upgrade with the refreshed Fix Pack 7.1.0.39 package |
Identifying the Installed Fix Pack Version
Under the application directory, run the following:
bin/versioninfo.sh
Included in the output is the version information and build date of the installed package.
If the original Fix Pack 7.1.0.39 is installed, the build date will appear as:
========================================================================
Impact Version Utility: Build date: 7.1.0.39 - 202609211443
========================================================================Checking a Downloaded Fix Pack Before Installation
Extract the package and open :
/scripts/impact_server_health_check.sh|bat
If the package is the refreshed Fix Pack 7.1.0.39, line 12 will contain:
# Build date: 7.1.0.39 - 202610111707 #
Known Issues in the original release of 7.1.0-TIV-NCI-FP0039
DT503505: Single Sign On and Console Integration fails after upgrading to 7.1.0.39
After upgrading to Fix Pack 7.1.0.39:
- Users receive HTTP 401 Unauthorized errors when accessing Netcool/Impact applications from DASH.
- Single Sign-On no longer functions correctly between DASH and Netcool/Impact.
- Impact services continue to process events normally, but UI access through DASH fails.
Cause:
Fix Pack 7.1.0.39 includes a WebSphere Liberty security fix (APAR PH69658, addressing CVE-2025-14923) which enforces stronger password-based encryption for all LTPA key files.
During an upgrade to Fix Pack 7.1.0.39, the installer attempts to preserve and apply the existing LTPA configuration, including the associated LTPA keys and passwords.
In environments where SSO with DASH isn't configured, duplicate ltpa.keys may be generated in separate locations in each server profile.
In environments where Single Sign-On (SSO) is integrated with DASH, LTPA configuration is commonly defined in included Liberty configuration files such as:
- basicRegistry.xml
- ldapRegistry.xml
- omnibusRegistry.xml
However, the original Fix Pack 7.1.0.39 only checks server.xml file when determining whether SSO and LTPA are already configured. As a result, existing LTPA definitions located in included configuration files were not detected.
Consequently, the installer could create a new LTPA key rather than reusing the existing one, causing Impact to use a different LTPA key than the key shared with DASH. This mismatch prevented successful authentication and resulted in SSO failures.
Remediation:
If you need to upgrade additional systems to 7.1.0.39, replace the upgrade installer with the refreshed version of 7.1.0-TIV-NCI-FP0039.
If the system is already configured for SSO with DASH:
1. Open /opt/IBM/tivoli/impact/wlp/usr/servers/ImpactUI/server.xml and delete the following entry:
<ltpa keysFileName="ltpa.keys" keysPassword="XXX"/>
2. Repeat this for the primary backend and any secondary servers.
3. Restart Impact.
If the system doesn't use Single-Sign-On with DASH:
1. Rename, move, or back up the existing ltpa.keys file:
$IMPACT_HOME/wlp/usr/servers/ImpactUI/ltpa.keys
$IMPACT_HOME/wlp/usr/servers/ImpactUI/resources/security/ltpa.keys
2. Generate a new encrypted password using the Liberty securityUtility command:
$IMPACT_HOME/wlp/bin/securityUtility encode
--aesConfigFile=$IMPACT_HOME/etc/impact/keystore/wlp_key.xml
--encoding=aes
"<LTPA_PASSWORD>"where LTPA_PASSWORD is your chosen password to protect the ltpa.keys.
3. Open /opt/IBM/tivoli/impact/wlp/usr/servers/ImpactUI/server.xml and locate the following line:
<ltpa keysFileName="ltpa.keys" keysPassword="XXX"/>Update the line to:
<ltpa keysFileName="${server.output.dir}/resources/security/ltpa.keys" keysPassword="ENCRYPTED_PASSWORD"/>The value of keysPassword should be the encrypted password from step 2.
4. Save the file and restart the Impact server.
5.Repeat these steps for each UI and Backend server.
Complex JavaScript policies may fail with an error similar to:
ERROR: JavaScript policy exceeded maximum loop/instruction limit: 100000000
This can occur when the policy is processing:
- Large datasets
- Large event collections
- Nested loops
- Computationally intensive policies
Cause:
To help prevent JavaScript policies from running indefinitely due to infinite loops, Netcool Impact 7.1.0.39 enforces a maximum JavaScript instruction count. When this limit is exceeded, policy execution is terminated and the above error is logged.
Remediation:
If your policies require a higher instruction count, you can increase the limit by adding the following property to $IMPACT_HOME/etc/NCI_server.props:
impact.policy.js.maxinstructioncount=200000000
The original default limit was set to 100,000,000 instructions. In this refresh, the limit has been increased to 200,000,000 to accommodate more complex policies and larger workloads.
Increase this value with caution, as setting it too high may allow poorly performing or runaway policies to consume excessive system resources.
Additional Information
For more information about loops and avoiding infinite loop conditions, see the While statements topic in the product documentation:
https://www.ibm.com/docs/tivoli-netcoolimpact/7.1.0?topic=structures-while-statements
For details of the Fix Pack 7.1.0.39 release, refer to the download notice:
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 39 (7.1.0-TIV-NCI-FP0039)
Was this topic helpful?
Document Information
Modified date:
12 October 2026
UID
ibm17292014