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

Problems Solved

To view details on specific Known Issues, visit the IBM Support Search site, enter the Known Issue identifier, and click Search.

Known Issues Resolved

• DT466480: Installation failures resulting from insufficient execute rights on the /tmp directory
• DT464676: Improve Omnibus connection handling when Omnibus Authentication is enabled
• DT466377: Hibernate cannot be used within a synchronized block
• DT466424: Threads Block on Impact JDBC Connection Done With Operation
• DT466423: Threads Block on Impact Event Processor Fetch Events Operation
• DT467170: Impact 7.1.0 FP38 upgrade fails if self-monitoring is enabled
• DT495678: Log viewer stripping newline characters
• DT467143: Kafka - org.apache.kafka.common.header.internals.RecordHeader is not serializable, RMI issue
• DT468131: Version control history not created or updated after applying Fix Pack 7.1.0.38
• DT474860: Derby_ImpactDB_Backup scripts fail when executed outside its installation directory
• DT469599: EventContainer throws a Null Pointer Exception in 7.1.0.38
• DT498873: RMI connections fail when SSL is enabled after applying FP38 in a multi-nic install causing clustering to fail, due to SAN
• DT499268: Enabling FIPS mode in Impact requires version 7.1.0.39 or later
• DT473452: 7.1.0.37 NullPointerException occurs when nextElement() returns null during OrgNode retrieval
• DT464887: Cannot trigger a runbook from impact in NOI 1.6.14 and NOI 1.6.15
• DT473889: EventReader Event Locking expression persists but Enable checkbox resets to unchecked after save/reopen
• DT473571: RESTfulAPIGET does not return JSON objects for AIOps Alerts
• DT495959: Allow a user to specify the bind host for JRExecServer
• DT474583: Cannot delete Policy Activator from the Services page
• DT467426: nci_trigger does not enforce role requirements
• DT470243: Update administration guide for clustered environments
• DT464939: Preventive Improvements to Detect Possible Corruption of Impact ServiceList and Other Configuration Artifacts
• DT496946: OMNIbus Password Length Limitation Can Cause Authentication Failures
• DT472610: DB2 with AUTH_MECHANISM as DATA_ENCRYPT (deprecated by IBM) is not supported as datamodel connection due to Java 11+ crypto restrictions
• DT475707: Netcool Impact 7.1.0.30 and later: WSInvokeDL() ignores callProps.Timeout and consistently times out after 60 seconds
• DT472705: Enabling SAML authentication in ImpactUI results in deployment failure on initial load
• DT473410: OMNIbusEventReader fails to manually start with inactive event filters
• DT468704: RESTfulAPI DSA not working with OAuth
• DT473823: Fix pack upgrade may fail when Derby SSL is enabled
• DT470477: RMI SSL Connections fails if SSL certificate lacks SAN with IP address
• DT496952: Syntax Checker Incorrectly Reports Errors
• DT500521: ObjectServer DSA does not failback correctly when OMNIbus is setup for controlled failback

List of Impact Known Issues that have documentation updates or have additional information 

• DT474861: Derby backup and restore process documentation lacks clarity and completeness
• DT495970: Documentation update for Certificate Hostname Verification in 7.1.0.38
• DT470971: Document the useiducforinserts property

Security-related Known Issues

• DT472981: UPGRADE WEBSPHERE IN IMPACT 710
• DT472982: UPGRADE JAVA IN IMPACT 710
• DT474418: UPGRADE JACKSON CORE TO 2.21.1 IN IMPACT 7.1.0
• DT473835: UPGRADE DB2 JDBC DRIVER IN IMPACT 7.1.0
• DT474443: UPGRADE LOG4J TO 2.25.6 IN IMPACT
• DT473832: UPGRADE NEETHI TO 3.2.3 IN IMPACT 7.1.0
• DT473828: UPGRADE RHINO IN IMPACT 7.1.0
• DT473829: UPGRADE PICOMATCH IN IMPACT 7.1.0
• DT473833: UPGRADE i18next-http-backend IN IMPACT 7.1.0
• DT498789: UPGRADE ACTIVEMQ IN IMPACT 710
• DT498790: UPGRADE APACHE SSHD MINA TO 2.19.0 IN IMPACT 710
• DT500146: UPGRADE HTTPCORE AND HTTPCLIENT IN IMPACT 710
• DT500643: UPGRADE KAFKA TO 3.9.2 IN IMPACT 710

• IRISCART-I-1523 - Monaco-Based Policy Editor
  Starting with Impact Fix Pack 7.1.0.39, the Impact Policy Editor has been enhanced through the integration of the Monaco Editor, the editor technology that powers Visual Studio Code (VS Code). Monaco Editor is set as the default Impact Policy Editor, while the previous Dojo editor is now labeled as the ‘legacy’ editor. This enhancement modernizes the policy development experience and provides a foundation for future developer productivity improvements.

  Key capabilities include:

  • Improved syntax highlighting for Impact Policy Language (IPL) and JavaScript.
  • Intelligent code completion (IntelliSense) for Impact built-in functions.
  • Function signature assistance and inline documentation.
  • Enhanced code navigation and editing capabilities.
  • Code folding, bracket matching, and automatic indentation.
  • Support for dark mode and additional editor themes.
  • Mini-map navigation for large policy files.
  • Keyboard shortcuts and editing behavior consistent with modern development environments.

  
  For more information, see:
  https://www.ibm.com/support/pages/node/7288681
   

• IRISCART-I-1975: Maintenance Window Manager (MWM) Event Processing Enhancement

  Starting with Impact Fix Pack 7.1.0.39, the Maintenance Window Manager (MWM) solution introduces support for identifying events that have not yet been evaluated by an MWM policy.

  A new value of -1 (Unknown) is assigned to the existing SuppressEscl field to indicate that an event has not yet been processed by MWM. When MWM evaluation is completed, the field is updated as follows:

    SuppressEscl = 6 when the event matches an active maintenance window.
    SuppressEscl = 0 when the event does not match any active maintenance window.

This enhancement enables gateways, readers, and downstream integrations to distinguish between events that have not yet been evaluated and events that have already been classified by MWM processing.

For more information, see:

- Considerations When Creating Policies That Interact with MWM Entries

- Excluding Alerts Not Yet Processed by MWM

- Configure MWM Properties Policy

 

• Introduced support for FIPS 140-3

  Starting with IBM Tivoli Netcool/Impact Fix Pack 7.1.0.39, support for Federal Information Processing Standards (FIPS) 140-3 mode has been introduced. FIPS support was unavailable in Fix Packs 7.1.0.36, 7.1.0.37, and 7.1.0.38 following the transition to Java 17, which did not initially provide the required support for FIPS operation.

  Customers requiring FIPS-compliant environments can now enable and use FIPS mode with Impact 7.1.0.39.

  This enhancement restores FIPS functionality for deployments that require compliance with security standards and enables organizations to continue using Impact in regulated environments following the migration to Java 17.

  For additional information about configuring FIPS mode, refer to the IBM Tivoli Netcool/Impact product documentation:
  https://www.ibm.com/docs/tivoli-netcoolimpact/7.1.0?topic=communication-enabling-disabling-fips
   

• Technology Preview: Policy REST API v2

  Starting with Impact Fix Pack 7.1.0.39, a new version of the Policy REST API is available as a Technology Preview.

  Enhancements include simplified version control management, additional policy metadata, enhanced error handling, and support for automation use cases. This is an initial Technology Preview release, and additional capabilities are planned for future fix packs.
  
  For more information, see:
  https://www.ibm.com/support/pages/node/7286533
  
  Note: Technology Preview features are provided for evaluation purposes and may be changed in a future release.
   

Additional Information

• nci_trigger now enforces user role requirements
   

  Starting with Netcool/Impact Fix Pack 7.1.0.39, the nci_trigger utility enforces role-based authorization when triggering policies. Only users assigned the impactAdminUser, impactFullAccessUser, or Administrator role can execute policies. Users without one of these roles receive an authorization error and the policy is not executed.

  For example:
  User 'username' is not authorized to trigger policies.
  User must have one of the following roles:
  impactAdminUser, impactFullAccessUser, Administrator
  
  For more information, see: 
  https://www.ibm.com/docs/tivoli-netcoolimpact/7.1.0?topic=tools-nci-trigger
   

• Improved Netcool/OMNIbus Connection Handling with ObjectServer Authentication Enabled (DT464676)
  Impact 7.1.0.39 introduces enhancements to improve connection resiliency when Netcool/OMNIbus ObjectServer Authentication is enabled.
  In previous releases, intermittent network communication issues affecting the ObjectServer connection could cause the Impact GUI to become unresponsive and generate the message:
  
     Unable to reach the nameserver.
  
  These conditions could occur even when the ObjectServer remained available, making connectivity issues difficult to identify and diagnose.
  The following improvements have been implemented:

  •  TCP keep-alive support is now enabled for ObjectServer connections through the connectionProperties="SO_KEEPALIVE=true" setting in the objectServerRegistry configuration. This helps prevent idle connections from being closed by network infrastructure such as firewalls.
  • ObjectServer Heartbeat Monitoring has been added through a new objectServerHeartbeat configuration element. The heartbeat monitor actively validates ObjectServer connectivity at a configurable interval (default: 60 seconds) and uses a configurable socket timeout (default: 10 seconds) to detect communication failures more reliably.
  • The confAuth4OMNIbus-enable.sh and confAuth4OMNIbus-disable.sh scripts have been enhanced to automatically configure and remove the required objectServerRegistry and objectServerHeartbeat settings when ObjectServer Authentication is enabled or disabled.

  
  These enhancements provide more reliable detection of ObjectServer connectivity issues and improve the overall stability and predictability of Impact when network interruptions occur.
  
  For information about configuring Netcool/OMNIbus ObjectServer Authentication, see Configuring Netcool/OMNIbus ObjectServer user authentication in the IBM Documentation.
  https://www.ibm.com/docs/tivoli-netcoolimpact/7.1.0?topic=servers-configuring-netcoolomnibus-objectserver-user-authentication#taskimag_objectserver_user_authentication__example__1

• JSON Payload Limit

  Starting with Netcool/Impact Fix Pack 7.1.0.39, a new configuration option is available to control the maximum JSON payload size processed by the UI Data Provider.

  WebSphere Liberty's JSON4J parser enforces a maximum string length on JSON payloads it processes. Starting in Fix Pack 7.1.0.39, Impact sets this limit to 20,000,000 characters by default, replacing the Liberty default of 1,048,576 characters.

  Impact sets this limit to 20,000,000 characters by default, replacing the Liberty default value of 1,048,576 characters.·

  This limit applies to payloads delivered to Dashboards accessing Impact's UI Data Provider (CURI/NOI UI Provider).

  For further information on how to adjust this limit, see:
  https://www.ibm.com/docs/tivoli-netcoolimpact/7.1.0?topic=issues-configuring-ui-data-provider-json-size-limit