Refresh of Fix Pack 36 for Netcool/Impact 7.1.0

========================================================================
Impact Version Utility:  Build date: 7.1.0.36 - 202501090258
========================================================================

# Build date: 7.1.0.36 - 202502281342 #

1. DT423574: SSL Object Server connections fail in Impact/Netcool version 7.1.0.36
   This Known Issue is applicable only to systems with SSL connections to Omnibus - either for Authentication, or for Event readers, or any JDBC connection to Omnibus, over SSL.
   
   If Impact is set up to use Object Server authentication, and the connection to Object Server is over SSL, then the following property is required before attempting to upgrade Impact to Fix Pack 36.
   
   In the jvm.options for all Impact servers, add this property
   -Dobjectserver.secureprotocols=TLSv1.2
   
   The jvm.options file is in the wlp/usr/servers/<server name> directory, i.e.
   /opt/IBM/tivoli/impact/wlp/usr/servers/ImpactUI/jvm.options
   /opt/IBM/tivoli/impact/wlp/usr/servers/NCI/jvm.options
   The property is required in the GUI and Backend servers.
   
   Additionally, there is an additional property required for JDBC connections to Object Server with SSL.Set the property impact.server.objectserversecureprotocols=TLSv1.2 in
   $IMPACT_HOME/etc/NCI_server.props and restart the Impact backend server.
    
2. DT425365: Discrepancy between Java versions and nashorn libraries pose an issue for upgrading
   This Known Issue is applicable to systems with a failed Fix Pack 36 installation.
   
   Error is java.lang.UnsupportedClassVersionError: JVMCFRE199E bad major version 55.0 of class=org/openjdk/nashorn/api/scripting/NashornScriptEngineFactory, the maximum supported major version is 52.0; offset=6
   
   A detailed explanation and workaound can be found here.
3. DT423903: Impact policies, with JavaCall function may produce an exception for class java.util.HashMap
   This Known Issue is applicable to systems using java.util.Hashmap in Impact policies.
   
   The error, which can be seen in the policy log files, is:
    java.lang.IllegalAccessException: class com.micromuse.common.parser.internal.core.ParserUtils$1 cannot access a member of class java.util.HashMap$KeySet (in module java.base) with modifiers "public"
   
   Use of java.util.Hashmap does not always produce an error. But in cases where an error is seen, switching from java.util.HashMap to java.util.HashSet is a workaround for the problem.
   
   Example IPL policy using java.util.HashSet:Query = "SELECT KeyField FROM alerts.conversions WHERE Colname = 'Severity'"; Severities = DirectSQL("defaultobjectserver", Query, false); SeveritiesNum = Length(Severities); Log( "SeveritiesNum = " + SeveritiesNum ); MyHashSet = NewJavaObject("java.util.HashSet", null); Index = 0; SeveritiesNum = Length(Severities); while ( Index < SeveritiesNum ) { JavaCall(null, MyHashSet, "add", { Severities[Index].KeyField}); Index = Index+1; } MyHashSetArray = JavaCall(null, MyHashSet, "toArray", {});
4. DT425601: After upgrading to Impact 7.1.0.36, the XMLDsaMediatorDataSource stops working
   This Known Issue is applicable to systems using the XML mediator data source.
   
   Install the latest version of xercesImpl.jar into Impact.
   Download xercesImpl.jar from https://xerces.apache.org/mirrors.cgi or https://mvnrepository.com/artifact/xerces/xercesImpl/.
   Copy xercesImpl.jar to the $IMPACT_HOME/lib3p directory in the backend server. Restart the Impact backend server.
   Repeat for each secondary server.
   Note: For Full Cloud NOI on OCP, where Impact is running in a pod, the dsalib should be used instead of lib3p, as this storage preserved between restarts.
5. Issue with Thread and Sleep function:

       Change the 2 lines:

       To just one line: