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

Download Description

************************************************************************************************************
* A change introduced by this Fix Pack might negatively  affect existing product function.
* Please refer to APAR IJ18856 for a description of the problem(s) and corrective action(s).
* Please refer to APAR IJ10655 for a description of the problem and corrective action
* Please refer to APAR IJ07401 for a description of the problem and corrective action.
* Please refer to APAR IJ07083 for a description of the  problem and corrective action.
* Please refer to APAR IJ23080 for a description of the problem produced by APAR IJ00620 and the corrective action.
* Please refer to APAR IJ24991 for a description of the problem and corrective action.
* Please refer to APAR IJ28513 for a description of the problem and corrective action.

* https://www.ibm.com/support/home/

 * More information about IJ07083 Clustering and synchronization

 ***********************************************************************************************************
Before installing or upgrading IBM Tivoli Netcool/Impact 7.1.0.13, refer to the Following documentation:

• https://www.ibm.com/support/knowledgecenter/SSSHYH_7.1.0.13/com.ibm.netcoolimpact.doc/welcome_kc.html
• Download attached package to review readme file or click this link to review list of enhancements, pre-req, installation instruction, and known issues in IBM Tivoli Netcool/Impact 7.1.0 Fixpacks.
• Review Known Issues section in Fix Pack 13 dcf.

-----------------------------------------------------------------------------------------------------------------------------------------

 For details of an individual APAR, go to https://www.ibm.com/support/home/ then enter the APAR name/# in "Search Support" then select search.

The following Netcool/Impact APARs are delivered with Fix Pack 13:

IJ00345: ON SOLARIS SOCKETS FROM IMPACTUI TO SERVER PERSIST AS CLOSE_WAIT
IJ00668: NEED AN OPTION TO IGNORE NULL ROWS RETURNED BY DIRECTSQL
IJ01140: OLD APACHE DRIVERS CAUSING IMPACT CPU TO RUN HIGH WHEN CUSTOMER USES COMMANDRESPONSE() FUNCTION
IJ01915: IMPACT ORDERING OF STATUS VALUES
IJ02155: RBA: ERROR IN RBA_EXECUTIONSTATUSTRACKER POLICY
IJ02410: ORDER BY CLAUSE IS EXCLUDED FROM THE SORT QUERY
IJ02475: RBA: UPDATE TO THE RBA ADD ON WITH CORRECTION TO THE RBA DERBY DATASOURCE
IJ02599: NULLPOINTEREXCEPTION FROM POLICYUIRESOURCE.FORMAT SOAPORGNODEMEMENTO
IJ03378: RBA: Runbook does not open with right click when there are two or more parameters set in the Runbook
IJ03394: RBA: NETCOOL/IMPACT 7.1.0 UPDATE METHOD OF GETTING RBA CONNECTION PARAMETERS
IJ03805: IMPACT 7.1.X ONLY START CLUSTER MEMBER IF DERBY DB STARTS SUCCESSFULLY
IJ03809: IMPACT 7 WINDOWS START SCRIPTS PARSE LOGFILE INCORRECTLY TO SEE WHETHER SERVER STARTS
IJ03864: RBA: FULLY AUTOMATED RUNBOOK FAILS TO BE INVOKED WHEN AN INTEGER VALUE IS PASSED AS A RUNBOOK PARAMETER
IJ03997: DAY OF WEEK SEASONALITY RULES NOT WORKING WITH != OPERATOR: NOI: Time conditions like "Day Of Week" != "Tuesday" are ignored for Seasonal Event Analytics Rule
IJ04121: FIXPACK CHANGE TO JVM.PROPERTIES MISSING IN ONE-HIT INSTALL
IJ04144: DASHBOARD WIDGETS CANNOT CONNECT TO SQL BASED DATASETS IN IMPACT 7.1.0.12
IJ04149: RE-RUNNING SE CONFIGURATIONS MAKES SE RULES NOT VISIBLE IF DOUBLE QUOTES EXISTS IN IDVALUE FIELD
IJ04543: NOI_ORACLEQUERY.JS ISSUE DUE TO AND OWNER='" QUERY
IJ04643: SE RULE ISSUE IF 24 IS "HOUR OF DAY""
IJ04653: NOI: SEASONAL RULES FAIL TO CAPTURE THE RETURN OF EVENT
IJ04960: SEASONALITY RULES IGNORE EVENTIDENTITY AND PROCESS RULES BASED ON IDVALUE
IJ05622: PATTERNACTION NOT CREATED WHEN DERBY USER HAS CUSTOM PASSWORD
IV90293: SENDEMAIL() FUNCTION EMAIL HEADER DETAILS HAVE CHANGED WITH APPLYING FP4
IV93391: USERNAME WITH BACKSLASH FAILED AT IMPACT LOGIN
IV94301: ADD ARGUMENT TO NCI_COLLECT_LOGS TO ASSIGN LOG FILES LOCATION
IV94558: UNABLE TO REMOVE FILE LOCKS USING THE IMPACT UI
IV96354: FILTER SYNTAX OUTPUT
IV97338: MWM DAYLIGHT SAVINGS NOT APPLIED WHEN USING GMT
IV97713: CREATED WIDGET INTO MWM DOES NOT WORK ON FIRST ATTEMPT UNLESS OPENED VIA CONSOLE INTEGRATION FIRST UNTIL IMPACT RESTARTED
IV98716: LDAP/SSL CONFIGURATION ISSUES
IV98915: EXITPOLICYEXCEPTION WHEN EXIT CALLED FROM SYNCHRONIZED BLOCK
IV99283: SINGLE ESCAPED QUOTATION MARK IN STRING FORWARDED BY DASH HANDLED INCORRECTLY BY IMPACT
IV99577: BIND DN PASSWORD NOT BEING TRANSLATED BY LDAP AUTHENTICATION SCRIPT
IV99578: COMMANDRESPONSE UNABLE TO HANDLE MULTIBYTE CHARACTER

Document update APARs

IJ00152: UI DATA PROVIDER FAILS WHEN FLATFILE DSA HAS COLUMN NAME #COUNT

IJ00333: DOC IS NEEDED FOR Users Using A CUSTOMIZE CERTIFICATE when configure the SSL in Impact
IJ00892: WSS SECURITY ENABLED, ACQUIRING ELEMENTS IN WSDL
IJ01033: STATUS 0 TO 6 ARE RESERVED AND STATIC
IJ02290: JMS DSA POLICIES - MSGPROPS.DELIVERYMODE IMCORRECT
IJ02521: DOC: JMS DSA REMOVE REPLYTO PROPERTY IN POLICY CODE EXAMPLE
IJ02522: UPDATE TO INCLUDE WHAT IS REPLICATED IN A CLUSTER
IJ03394: RBA: NETCOOL/IMPACT 7.1.0 UPDATE METHOD OF GETTING RBA CONNECTION PARAMETERS
IJ03993: NOI: CUSTOMIZED COLUMN FOR EVENT ANALYTICS, NEW COLUMNS SHOW DUMMY IN RELATED EVENT SELECTION OF CREATE RULE IN SEASONAL EVENTS
IJ04017: GLOBAL VARIABLE USAGE AND VALUES ANOMALIES IN .IPL
IV93442: OPTION TO ALLOW DERBY TO BIND TO A HOST DIFFERENT TO SYSTEM HOSTNAME
IV94301: ADD ARGUMENT TO NCI_COLLECT_LOGS TO ASSIGN LOG FILES LOCATION
IV94558: UNABLE TO REMOVE FILE LOCKS USING THE IMPACT UI
IV96354: FILTER SYNTAX OUTPUT
IV97338: MWM DAYLIGHT SAVINGS NOT APPLIED WHEN USING GMT
IV98371: IN POLICY WITHOUT SETTING KEY FIELD IN POLIY FOR UI PROVIDER OUTPUT DATA SCHEMA DEFINITION CAUSE INCORRECT DATA IN DASH
IV98716: TROUBLESHOOTING LDAP/SSL CONFIGURATION ISSUES
IV98933: UPDATE TO WSINVOKEDL FUNCTION PARAMETERS
IV99283: SINGLE ESCAPED QUOTATION MARK IN STRING FORWARDED BY DASH HANDLED INCORRECTLY BY IMPACT
IV99577: BIND DN PASSWORD NOT BEING TRANSLATED BY LDAP AUTHENTICATION SCRIPT
IV99578: COMMANDRESPONSE UNABLE TO HANDLE MULTIBYTE CHARACTER

To check the APARs that were part of the previous FixPack (7.1.0.12), please check this link:

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli Netcool Impact/page/Impact 7.1.0.12 README

2.0 New support and features

2.1 Browser Support with Fix Pack 13

Impact 7.1.0.13 supports:

Firefox ESR 52
Internet Explorer 11

JazzSM 1.1.3.0 DASH 3.1.3.0 CP6

2.2 Component Updates

Java has been updated to version 1.7.0 SR10 FP20
WebSphere Application Server Liberty has been updated to version 18.0.0.1

2.3 Enhancements in Fix Pack 13

Fix Pack includes the following enhancements:

• Accessing datasource configurations remotely using the REST API


• This functionality allows customers to edit existing datasources from outside the Impact JVM. This is an alternative way to edit configurations compared to the Impact UI. This functionality is limited to editing already configured datasource configurations and allows you to edit any parameter value of the configuration.
  Refer to topic “Accessing datasource configurations remotely using the REST API”, under Chapter 7 of the Netcool/Impact Administration Guide, for complete details.
• Enhancement to the RBA Add-ons: RBA: Runbook does not open with right click when there are two or more parameters set in the Runbook


• Currently there are restrictions on the characters of the runbook parameters that can be used within launch-in-context from OMNIbus events to the associated runbook. For example, all variants of launch-in-context do not support the “=”, “&”, and “%” characters within the runbook parameter values.
  To address the encoding issue, the following action needs to be taken:
  • 1. Add an extra column field, "RunbookParametersB64", to the OMNIbus alerts.status table
    FOR EXAMPLE:
    [netcool@omnibus bin]$ ./nco_sql -username root -password ""
    1> alter table alerts.status add RunbookParametersB64 varchar(2048);
    2> go
    2. The RBA_Status datatype needs to be refreshed in the GUI to pull in the
    new field that was added to the object server in Step 1, above.
    3. Restart Impact
    4. The RBA release must be at 1.10.x (or above)

• Provide pre-validation of the LDAP parameters when running the confAuth4LDAP script, by querying the LDAP server before making any config changes.
• Update to configuration of LDAP Authentication

There is an update to the arguments supplied to the script that enables LDAP authentication.
The LDAP Bind user password is no longer to be supplied on the command line. The LDAP Bind user password needs to be added to the impactdap.properties before the confAuth4LDAP script is executed.
The LDAPBindPass value will be deleted from impactdap.properties following the execution of LDAP authentication scripts.
Please see update to Impact Documentation:
https://www.ibm.com/support/knowledgecenter/en/SSSHYH_7.1.0.13/com.ibm.netcoolimpact.doc/admin/imag_ldap_impactdap_props.html

• RESTful DSA - Update Validation Model to Handle Basic Authentication. A windows msg is now displayed, requiring user name; when authentication is 'Basic'

• NOI: Provide process and functions to update NOI Data and Source Type for the new Configuration UI to refresh information


• • A new UI Data Type function is now available to update data type from within a policy.
  • A new Data Source Resource API is now available, to update data source from within a policy using a new function.
  • New Function and Process to Dynamically Add Rollups and view them in DASH
  • Make NOI configuration actions less manual

• Migration of rollups in Netcool/Impact v7.1.0.13
• Fix pack v7.1.0.13 uses a new format for the creation of rollups that is different to previous versions of Netcool/Impact. Refer to the following link for additional information and to take additional actions:
  Migration of rollups in Netcool/Impact v7.1.0.13

Please also refer to the topic “Updating Rollup Configuration” in the following link: Updating Rollup Configuration

In addition, review the “Event Analytics Configuration” page: Event Analytics Configuration

UI data provider refresh rate:

• You can configure how often the UI data provider is refreshed. This interval is set to 20 seconds. To change this setting, add the following statement to the <servername>_server.props file (for example NCI_server.props) that is in the $IMPACT_HOME/etc/ folder:
  impact.uidataprovider.refreshrate=<refresh_rate_in_miliseconds>

• [NOI Audit] Provide Report History with details information about each run

A new CSV style log is now available, which provides a view historical report with information about each report including , number of events, report type and findings such as # of seasonal events, re groups, re events, number of matchind re count in seasonality, filter, report span. This new log is can be found under: $IMPACT_HOME/logs/NCI_NOI_Report_History.log

• The nci_collect_logs script now accepts new parameters

Usage: ./bin/nci_collect_logs [ NO ARGUMENT | -DexcludePolicyEtcFiles=true | -Dlogfilelocation | -help ]

• Refer to the topic “Collecting log files for debugging” in the Tivoli Netcool/Impact 7.1 Trobuleshooting General Issues Wiki Page for more details:
  Troubleshooting Netcool Impact 7.1 >‎ General issues

• Support for MS-SQL Server DSA

This DSA supports MS-SQL Server 2008, 2012, 2014 and 2017.To use this data source adapter obtain the Microsoft SQL Server version 4.0 Type 4 JDBC Driver, from this URL:
https://www.microsoft.com/en-us/download/details.aspx?id=11774

• Support of Multi-tenant for UI Data Provider

Multi tenancy is based on adding collections per widget, so one policy could render several different data sets. Generally, the collections are managed by the UI Data provider API.

3.0 Known Issues in Fix Pack 13

• ITNMEventListener fails to start, if connecting to ITNM versions 4.2. Currently, only versions 3.8 and 3.9 are fully supported.

• On Unix (AIX,Linux,Solaris,zLinux) environment, after installing FP13, user will not able to configure new LDAP configuration in a split environment. Specifically on the Impact server side.

Windows FP13 images have been updated with the fix.
No impact to existing LDAP configuration after installing FP13.

Recommendation:
It is recommended to configure LDAP Authentication prior to installing FP 13 in split environment.

Workaround:
1. On the Impact server, locate and backup the following file:

▪ $IMPACT_HOME/install/security/cfg_scripts/confAuth4LDAP.xml

2. Edit the above listed file and locate the following line of code (at line 50):

<property name="bootstrap.properties" value="${impact.home}/wlp/usr/servers/ImpactUI/bootstrap.properties"/>

3. Delete and replace the above listed line of code and put the following in its place:

<if>

<available file="${impact.home}/install/buildimpact.properties"/>
<then>
<loadproperties srcFile="${impact.home}/install/buildimpact.properties"/>
</then>
</if>
<condition property="bootstrap.properties" value="${impact.home}/wlp/usr/servers/ImpactUI/bootstrap.properties">
<available file="${impact.home}/wlp/usr/servers/ImpactUI/bootstrap.properties"/>
</condition>

<condition property="bootstrap.properties"
value="${impact.home}/wlp/usr/servers/${user.nciServerInstanceName}/bootstrap.properties">
<available file="${impact.home}/wlp/usr/servers/${user.nciServerInstanceName}/bootstrap.properties"/>
</condition>
4. Save the changes and proceed with the LDAP configuration porocess.

• The following applies only to Netcool/Impact Clients with Netcool Operations Insight (NOI) - and only for those with Existing configurations!

After upgrading to Netcool/Impact 7.1.0 FP13, run through the Wizard; confirm, verify & save the configuration. Refer to: Event Analytics Configuration

1. It is a known issue that custom rollup changes to properties and params files are overwritten. Running through the wizard will repair these.

2. Also for seasonality View, it is advisable to run through the Wizard to make sure the right columns are displayed. Refer to the following link for appropriate actions: Migration of rollups in Netcool/Impact v7.1.0.13

• • The EventReader service for Seasonality Events is called "ProcessSeasonalityEvents" and it does not (by default) read updated or de-duplicated events. "Get updated events" is not selected (by default) in the UI for the "ProcessSeasonityEvents" Service, on the Event Mapping tab.
  
  The reason for this is due to the wide Filter for the "ProcessSeasonityEvents" Event Reader service. By default, the filter is set to "1=1". With this wide filter, if "Get updated events" was enabled, and Seasonality rules fired, this could lead to an infinite loop. i.e. Seasonality Rules updating events which in turn get read by the reader and fire the Seasonality Rules again.
  
  The solution is for the Event Mapping Filter to be set, in such a way, as to avoid already processed events. i.e. if the Seasonality rules are setting the Service field to "something" then the Event Mapping Filter could be set to restrict these.

  • NOI: Impact Event Isolation and Correlation page does not load if non-default cluster name is used (such as NCICLUSTER_Z )

  ◦ To resolve this issue, perform the following actions:

  ▪ stop the Impact GUI server $IMPACT_HOME/bin/stopGUIServer.sh

  ▪ copy or rename the file with the correct cluster name. For example:

  • cp $IMPACT_HOME/opview/displays/NCICLUSTER-EIC_configure.html $IMPACT_HOME/opview/displays/NCICLUSTER_Z-EIC_configure.html

  ▪ restart the Impact GUI server $IMPACT_HOME/bin/startGUIServer.sh

  ▪ go to the Event Isolation and Correlation page and confirm the page is displayed without the errors.