IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 2 (6.1.1-TIV-NCI-FP0002)

Download Description

======================================================================
Readme file for: IBM Tivoli Netcool/Impact
Product/Component Release: 6.1.1
Update name: Fix Pack 2
Fix ID: 6.1.1-TIV-NCI-FP0002
IBM Corp.
Publication date: December 10, 2014
Last modified date: December 8, 2014

======================================================================


Contents:

1.0 Files included in this Fix Pack
2.0 Hardware and software requirements
3.0 Installation information
3.1 Dependencies
3.2 Prerequisites
3.3 Special considerations
3.4 Superceded Fixes
3.5 Extracting Fix Pack files
3.6 Installation in a Cluster Environment
3.7 Installation of the Fix Pack
3.8 Uninstalling the Fix Pack
3.9 Recovering from a failed Fix Pack installation
3.10 Policies overwritten by this Fix Pack
3.11 Discovery Library Toolkit
4.0 Additional information
5.0 List of APARs
5.1 Fixes (APARs) Included In this Fix Pack.
6.0 New support and features
6.1 Additional Browser Support with Fix Pack 2
6.2 Additional Browser Support with Fix Pack 1
6.3 Additional Platform support with Fix Pack 2
6.4 Additional Platform support with Fix Pack 1
6.5 eWAS Fixes and Upgrades
6.6 Enhancements in Fix Pack 2
6.7 Enhancements in Fix Pack 1
6.8 Deprecated features in Fix Pack 2
6.9 Deprecated features in Fix Pack 1
6.10 MSN support in Fix Pack 1
7.0 Known Issues in Fix Pack 2
7.1 Auto saved Policies not cleaned up
7.2 Unable to save ObjectServer DataType when the
Impact server name is long
7.3 WEBSERVICES SECURITY NOT FUCTIONAL
7.4 If using WEBSERVICES SECURITY (WSS) user authentication
7.5 Microsoft Internet Explorer 11
8.0 Copyright and trademark information


===================================
1.0 Files included in this Fix Pack
===================================

Fix Pack 2 addresses the problems that have been reported in IBM Tivoli
Netcool/Impact version 6.1.1. The following table contains a list of
files included in this Fix Pack and operating systems associated with
these files:

Platform File
AIX * 6.1.1-TIV-NCI-FP0002-aix.tar
Linux * 6.1.1-TIV-NCI-FP0002-linux.tar
Solaris * 6.1.1-TIV-NCI-FP0002-solaris.tar
Windows * 6.1.1-TIV-NCI-FP0002-windows.zip
Linux for * 6.1.1-TIV-NCI-FP0002-zLinux.tar
System z

all platforms * 6.1.1-TIV-NCI-FP0002.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:
* Linux
* Solaris
* AIX
* zLinux


======================================
2.0 Hardware and software requirements
======================================

For information about supported operating systems and software, see
System requirements or see Planning, Setting up a deployment,
System requirements in the Netcool/Impact Administration Guide PDF.

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcoolimpact.doc_6.1.1.1/common/dita/imp_hardware_requirements.html

============================
3.0 Installation information
============================

3.1 Dependencies

IBM Tivoli Netcool/Impact version 6.1.1

This Fix Pack is applied to Tivoli Netcool/Impact 6.1.1 Server and 6.1.1 GUI
Server.

3.2 Prerequisites

Tivoli Integrated Portal 2.2.0.11 (TIP Fix Pack 2.2.0.11). This has been
installed as part of Impact 6.1.1 GA.

However,IBM strongly recommends updating to TIP Fix Pack 2.2.0.13 or 2.2.0.15.
If support is required for Firefox ESR 24 and Internet Explorer 10,
TIP 2.2.0.13 is the minimum requirement. For Firefox ESR 31 and Internet
Explorer 11, as well as, Java JRE 8, the required TIP version is TIP 2.2.0.15.

If the Impact server and GUI server are installed on different systems, the
TIP Fix Pack needs to be installed only on the GUI server. If TIP Fix Pack
is installed on the GUI Server, which is on a separate system, the eWAS on
the Impact Server system must be upgraded to eWAS 7.0 Fix Pack 35 (or higher).
The instructions to apply the eWAS Fix Pack are in section 6.5 below.

If the Impact Server and TIP are on the same system, the TIP Server
and the Impact server must be stopped prior to installing the TIP Fix Pack.
The TIP Fix Pack will automatically upgrade eWAS and the WASSDK, on the server
where it is run.

Netcool/Impact 6.1.1 Fix Pack 2 is certified for TIP FP 2.2.0.15.

To download TIP FP 2.2.0.15 go to:

http://www-933.ibm.com/support/fixcentral/swg/selectFixes?
parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal
&release=2.2.0.15&platform=All&function=all

3.3 Special considerations

To apply this Fix Pack you will need 1700 Mb of free disk space.

1. Backup the current server using the command:
nci_export <serverInstanceName> <absolute path directory>

For example:
Non-Windows Operating System:
$NCHOME/impact/bin/nci_export NCI /tmp/exports/NCI_exports

Windows Operating System:
%NCHOME%\impact\bin\nci_export.bat NCI C:\tmp\exports\NCI_exports

2. Backup the current jar file:
Non-Windows Operating System:
cp $NCHOME/impact/lib/nci<date><current-buildlevel>.jar $NCHOME/impact/tmp/

Windows Operating System:
copy %NCHOME%\impact\lib\nci<date><current-buildlevel>.jar %NCHOME%\impact\tmp\

3. You will be prompted during the installation to specify a backup
directory name. The installer backs up DE at this location.

NOTE: Please ensure this backup directory exists with write permission before launching the installer.

4. This fix pack does not back up the entire Impact application. It only
backs up the files that it has updated or replaced. A backup copy of the
original files is located at [InstallDirectory]/tipv2/logs/impact/maintenance/backup/6.1.1.0/FP0002


3.4 Superceded Fixes

6.1.1-TIV-NCI-FP0001 is superceded by this Fix Pack.
6.1.1.1-TIV-NCI-IF0001 is superceded by this Fix Pack.

3.5 Extracting Fix Pack files

3.5.1 Extracting on Linux, Solaris, AIX and zLinux platforms
1. Copy the 6.1.1-TIV-NCI-FP0002-<ARCH>.tar file to your system.
2. Unpack the file using this command:
* tar -xvf 6.1.1-TIV-NCI-FP0002-<ARCH>.tar

3.5.2 Extracting on Windows platforms to your system
1. Copy the 6.1.1-TIV-NCI-FP0002-windows.zip
2. Extract the contents of the file to a selected directory.

3.5.3 Fix pack directories

When you extract the file, this directory is created:

Impact (this contains Impact Server and GUI server updates)


3.6 Installation in a Cluster Environment

Please follow the instructions in the Netcool/Impact 6.1.1 administration guide
for setting up a server cluster.
http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcoolimpact.doc_6.1.1.1/impact_pdflibrary_ic.html


3.7 Installation of the fix pack

[Fix Pack] Refers to the directory where you extracted the fix pack
files from the zip/tar file.

Installing without a backup:

If you prefer to backup DE with your own procedures, you can
run the install with the following parameter:

-DNO_BACKUP=true

(For Silent Install, uncomment the "NO_BACKUP=true" parm on the setupFP.rsp response file)

If you choose this method, you must backup DE
before you install. Restore the original system using
your backup or restore procedures or utilities.

Follow this procedure to install the fix pack:
1. Before installing the fix pack all Impact processes must be running.
2. Change to the [Fix Pack]/Impact directory where the you
extracted the files.
3. Run the installation using one the following commands:
* setupwin.exe - Windows.
* setup<ARCH>.bin - other operating systems.

Installation command options:

GUI mode
No options, for example:

Windows: setupwin.exe

Or

Unix: ./setup<ARCH>.bin

Console mode
Use the -i console option. For example:

Windows: setupwin.exe -i console

or

Unix: ./setup<ARCH>.bin -i console

Silent Mode
a. Copy installSilent_responseFP.txt from the Impact directory of the
extracted Fix Pack file to a location it can be edited (/tmp).
b. Update the file to match your environment
c.
c. Run:

UNIX: setup<ARCH>.bin -f /tmp/installSilent_responseFP.txt
or
Windows: setupwin.exe -f C:\tmp\installSilent_responseFP.txt
Note: The response file needs to have a fully qualified path.
Note: before you do the upgrade, please backup impact data

4. After installing the servers, run the script checkEarWarUpdate.ant
which can be found on the servers under <installDir>/impact/bin.
This script will verify if there were any issues with upgrade
and deployment.
On Windows:

nc_ant.bat -f checkEarWarUpdate.ant

On Linux/Unix:

./nc_ant -f checkEarWarUpdate.ant

If no issues are detected, it will display a message
'No issues were detected!.' If there were issues, it will display
the file where it found the issue.
If the installation completed successfully but errors were
detected when running this script, please contact IBM Support
for commands that can be run post-install to fix the issue.

3.8 Uninstalling the Fix Pack

Before uninstalling the Fix Pack all Impact processes must be
running.

Attention: Uninstall the Fix Pack with the same user that was used to
install Impact 6.1.1 GA. Note that on Windows, if running the uninstall
from the IMPACTInstall611_FP2 directory, this directory file itself
cannot be deleted although its contents are.

Follow this procedure to uninstall the Fix Pack:
1. Change to the directory:
<installDir>/impact/_uninst/IMPACTInstall611_FP2
2. Run the uninstallation using one the following commands:
* uninstall.exe - Windows.
* uninstall - other operating systems.

Uninstallation command options:

GUI mode
No options, for example:

Windows: uninstall.exe

Or

Unix: ./uninstall

Console mode
Use the -i console option. For example:

Windows: uninstall.exe -i console

or

Unix: ./uninstall -i console

Silent Mode
a. If silent mode was used for the installation, the uninstallation
defaults to a silent uninstallation and you must supply a response
file or the uninstallation fails.
b. Copy the uninstallSilent_responseFP.rsp
file from the Fix Pack image to the directory:

<installDir>/impact/_uninst/IMPACTInstall611_FP2

c. Update the file to match your environment
d. Run:

UNIX: ./uninstall -f uninstallSilent_responseFP.rsp
or
Windows: uninstall.exe -f uninstallSilent_responseFP.rsp


3.9 Recovering from a failed Fix Pack installation

If the installation fails, attempt an uninstallion in which case, it reverts to the
previous version. If there is no uninstallation file in the _uninst/IMPACTInstall611_FP2 directory,
nothing is installed and you can delete the IMPACTInstall611_FP2 directory and
reinstall.

3.10 Policies overwritten by this Fix Pack

When applying Test Fixes and Interim Fixes/Fix Packs to an existing system, the policies
provided by IBM 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.

In this Fix Pack, the following policies have been overwritten:
EIC_utils.ipl
EIC_IsolateAndCorrelate.ipl
Import.ipl
Opview_EIC_confSubmit.ipl
Opview_EIC_requestHandler.ipl
MWM.ipl
Opview_Add1TWin.ipl
Opview_onetwins.ipl
Opview_openwins.ipl

Backups of the original files can be found under
[InstallDirectory]/tipv2/logs/impact/maintenance/backup/6.1.1.0/FP0002/policy.

3.11 Discovery Library Toolkit
===================================================

1. Navigate to the [Fix Pack]/launchpad/<ARCH> directory.

2. To install Fixpack 2,

If you are on a Windows operating system, run the following
command from a prompt:

setup-dltoolkit-windows_64.exe

If you are on a Unix operating system, run the following
command from a prompt:

setup-dltoolkit-<unixplatform>_64.bin

For console mode, specify "-i console".

Note: If the installer cannot find the TBSM 6.1.1 Discovery
Library Toolkit, verify that the toolkit is installed and
that it was installed by the user that the fixpack is being
installed with. If these are both okay, then set the environment
variable TBSM_TOOLKIT_BASE to the location of the toolkit and
restart the toolkit installer. For example:
Windows:
set TBSM_TOOLKIT_BASE=C:\Program Files\IBM\tivoli\tbsm\XMLtoolkit
UNIX:
export TBSM_TOOLKIT_BASE=/opt/IBM/tivoli/tbsm/XMLtoolkit

3. The toolkit installer requires access to the database.


4. Notes and Post-Install Considerations:

a) After installation is complete, you may remove
[Fix Pack] to save space.

5. Restart the toolkit.

==========================
4.0 Additional information
==========================

Please refer to Tivoli Netcool/Impact 6.1.1 Documentation for additional information

There is no new additional information with this Fix Pack

=================
5.0 List of APARs
=================

5.1 Fixes (APARs) Included In this Fix Pack.

The following IMPACT APARs are delivered with Fix Pack 2:

IV18554: 511:EVAL FUNCTIONALITY HAS CHANGED FROM 4.1 TO 5.1.1
IV23315: UPGRADE FROM IMPACT 5.1.1 TO IMPACT 6.x DISTRIBUTED [611]
IV64152: SECONDARY NODE CAN'T BIND TO THE NAME SERVER
IV61089: INSTALL FAILS AT STARTWAS STEP
IV63137: IMPACT 6.1.1 REPLICATION FROM PRI TO SEC NOT WORKING
IV62792: 1.2 GB WAS BEING FILLED BY BLANKS FROM LOGGER FUNCTION
IV61956: DATA MODEL NOT SORTED IN ALPHABETICAL ORDER
IV61746: IMPACT 611 FP1 INSTALL FAILS WHEN INSTALLING ON GA 611, WHICH HAS BEEN FIRST UPGRADED FROM IMPACT
IV61399: NULL VALUE ON FIELD, DASH WIDGET SPINS TO MANY TIME MAKING DATA VEIW VERY SLOW TO VIEW.
IV60005: DATA TYPE NOT SAVED CORRECTLY IF FEILD DELETED AND REMAINDER RE-ORDERED.
IV60253: TEPS UIDP NOT CLEARING CACHE, CAUSING MEMORY LEAKS.
IV58616: DIRECTSQL EXECUTE CAUSES EXCEPTION IN POLICY EXECUTION
IV58511: EMAIL READER SERVICE DOES NOT HANDLE EMAILS THAT USE A NON-STANDARD CHARACTER SET
IV53717: JMS MESSAGE LISTENER SERVICE NOT STOPPING PROPERLY
IV56745: IMPACT IS UNABLE TO HANDLE EXCEPTIONS FROM A WEBSERVICES CALL
IV56068: IMPACT THREADS INCREASING WHEN WEBSERVICES SECURITY IS ENABLED
IV55989: HIDDEN/DELETED FIELDS NOT BEING REMOVED FORM OPERATOR VIEW
IV50329: WEBSERVICES SECURITY NOT FUCTIONAL
IV56541: CONFVMM4NCOS SCRIPT IN IMPACT 6.1 IS NOT WORKING AS EXPECTED
IV47748: CAN'T LOAD WEBSERVICE LIBRARIES THAT HAVE JAVA OR JAVAX PACKAGES IN THEM
IV55464: UNABLE TO CREATE A BUTTON ON JAZZ AFTER JAZZ FP2
IV60923: USING THE DIRECTSQL APPROACH AND HAS IDENTIFIED THE NON-REFRESH OF THE SCHEMA ON USERNAME UPDATE IN THE DSA AS SECURITY RISK

The following IMPACT APARs are delivered with Fix Pack 1:

IV11728: USING EVENTREADER PARSERESTRICTIONFILTER TO ALLOW THE USE OF GETDATE()
IV21717: ONE TIME MAINTENANCE WINDOWS DO NOT ADJUST FOR DST
IV22560: ANALYZE EVENT MAPPING TOOL FAILS AND HAMMERS CPU
IV33973: JMS READER DOES NOT CONVERT ACTIVEMQMAPMESSAGE DATA FOR TRANSFER TO SECONDARY CLUSTER MEMBER
IV34503: "OPTIMIZE LIST" OPTION DOESN'T REFLECT THE APPLIED CHANGES TOTHE LIST IN THE "RESTRICT FIELDS", WITHIN THE EVENTREADER
IV35827: ERROR PRODUCED IN NETCOOL.LOG WHEN USING AN EVENTREADER WITH A BLANK FILTER VALUE
IV35885: IMPACT NEEDS TO CHECK USER CREATED SERVICES, FOR WITH NAMES THAT END WITH A "_SERVER".
IV35940: RETURNEVENT() FUNCTION WITHIN DATABASEEVENTREADER ADDED UNWANTED SINGLE QUOTES TO THE IDENTIFER FIELD IN THE SQL "VIA" STATEMENT
IV36405: THE CONFVMM4LDAP COMMAND IS SHIPPED WITH IMPACT 6.1, BUT IS NOT DOCUMENTED
IV36503: MWM CALENDAR: USING FORWARD BY ONE MONTH CAN LEAD TO NON-EXISTENT DATES BEING CREATED
IV37040: USING "NCI_COLLECT_LOGS" UTILITY IN A GUI SERVER ONLY INSTALL DOES NOT WORK.
IV37369: OBJECT.PROTOTYPE.TOSTRING.CALL(OBJ) RETURNS {}
IV37717: IMPACT 6.1 FP1 OPVIEW SOAP ERROR
IV37759: INTERNAL DATATYPE STRING VALUE IS INTERPRETED AS AN INTEGER IF IT CONTAINS ONLY DIGITS
IV38045: ORACLE DSA ERROR FOR COLUMN NAMES WITH "DOUBLE-QUOTES" AND "NOT-ALL-CAPS"
IV38585: NCI_EXPORT NOT EXITING CLEANLY WHEN RUNNING ON A NON PRIMARY IMPACT
IV38961: APPLICATION AND DATA NEEDS TO BE VALIDATED.
IV39368: INCREASING CPU WHEN JABBERSERVICE
IV40158: ABILITY TO CHANGE NUMBER OF POLLING INTERVALS
IV41888: DISABLE THE HIBERNATION STORAGE
IV42715: ERROR WHEN USING # IN IMPACT FILTER FROM DATATYPE DATAITEMS GUI WINDOW
IV43030: IMPACT MISSED ENRICHING FEW EVENTS WHICH OCCURED SIMULTANIOUSLY
IV43751: EVENTPROCESSOR IN A SECONDARY SERVER IS UN-ABLE TO CONTACT PRIMARY SERVER EVENTPROCESSOR.
IV45068: ERROR TRYING TO CREATE SCHEDULE DATATYPE DATAITEM: ERROR MESSAGE: HTTP ERROR 500 INTERNAL SERVER ERROR
IV45511: NEEDED 6.1.1 MWM OPVIEW POLICIES GET OVER-WRITTEN, AFTER MIGRATION FROM EITHER IMPACT 5.X OR 6.1, CAUSING MWM ISSUES
IV45569: DOCUMENTATION NEEDED ...HOW TO HANDLE BUILD-UP OF "ORPHANED" FILES, CREATED FOR XINY DATATYPE
IV45838: OBJECTSERVER CONNECTION DOES NOT RECOVER FROM BUSY PERIOD IF SELFMONITORING (DATASOURCE MONITORING) IS ENABLED
IV46099: JMSREPLYTO WAS NOT ABLE TO SET CORRECT QUEUE.
IV46493: ATTEMPTING TO USE DATATYPE FILTERS - "SPECIAL" CHARACTERS BEING CONVERTED TO HTML ENCODING THAT BREAKS OUTGOING SQL.
IV46696: LIMITING THE NUMBER OF CONNECTIONS THAT IMPACT OPENS TO JMS
IV46729: TOPOLOGY WIDGET KEEPS THE OLD LINKS BETWEEN NODES AND DOESN'T CLEAR IT, RESULTING IN AN INCORRECT RELATIONSHIP
IV46799: FUNCTION <FUNCTIONNAME> IS NOT DEFINED BEFORE CALL
IV47058: MWM POLICY SETS SUPPRESESCL FIELD TO 6 IMMEDIATELY AFTER SETTING TO 1.
IV47799: SELECTING 2 KEY FIELDS IN DATA TYPE ON DEFAULTOBJECTSERVER DOESN'T WORK
IV47904: EIC 'TEST SQL' FAILS DUE TO UNSCAPED CHARACTERS
IV47988: SETTING THE WSSETDEFAULTPKGNAME VALUE GLOBALLY DOESN'T WORK WHEN THE WSINVOKE FUNCTION IS INSIDE A POLICY FUNCTION
IV48113: SLOW RESPONSE ON THE POLICY PAGE WHEN ATTEMPTING TO OPEN A LARGE NUMBER OF POLICIES VIA THE GUI
IV48113: SLOW RESPONSE ON THE POLICY PAGE WHEN ATTEMPTING TO OPEN A LARGE NUMBER OF POLICIES VIA THE GUI
IV50464: JMS TIMEOUT CAUSES POLICY ASSIGNED TO OPERATORVIEW EXECUTE TWICE
IV50932 MAINTENANCE WINDOW EVENT SHOWED STATUS 'NORMAL' - parent apar cancelled
IV51062: DB2 DSA FAILS TO QUERY COLUMN NAMES WITH "DOUBLE-QUOTES AND NOT-ALL-CAPS"
IV51098 WIDGET TABLE STOPPED WORKING AFTER JAZZ FIX PACK 1 INSTALLATION
IV51100 THE "VALUE STATUS GAUGE" IN JAZZ FIX PACK 1 FOR SERVICE MANAGEMENT DOES NOT WORK WITH NETCOOL IM
IV53483: CALLDBFUNCTION USAGE IN ORACLE DATABASE WITH FILTER 0=1
IV53810: I10N - TRANSLATION ISSUE
Translation issues in XinY policy and in Browse and Cancel buttons have been fixed.
IV53818: ISSUES WITH INTEGRATIONS ON 611
Web services related issues have been fixed.
IV53822: FIXES FOR HA IN 611 FP1
Issues related to Omnibus failover/failback have been fixed.
IV53824: FIXES IN IMPACT SCRIPTS FOR 611 FP1
Issues in Impact scripts nci_export, nci_import and nci_encryptpolicy have been fixed.
IV53825: THIS APAR INCLUDES FIXES FOR DATA MODEL ISSUES IN 611 FP1
IV53826: FIXES ISSUES IN 611 FP1 WITH POLICIES
IV53827: THIS APAR FIXES SERVICES RELATED ISSUES IN 611 FP1
IV53836: FIXES UI DATA PROVIDER ISSUES IN 611 FP1
IV54939: A MISSING $IMPACT_HOME/LOGS/INSTALL/ DIRECTORY WILL RESULT IN THE NCI_CONFIGURATION_UTILITY PROBLEM
IV55776: UI PROVIDER ENHANCEMENTS IN 611 FP1
This contains UI Provider enhancements where the user can show status and percentage in topology,
tree, table, and list widgets
IV55778: JABBER UPDATES IN 611 FP1
This contains Jabber Updates to use the smack library.
IV55779: ADDITIONAL POLICY FUNCTIONS IN 611 FP1
This contains additional policy functions to escape special characters and filter malicious
content in strings.
IV55780: DSA ENHANCEMENTS IN 611 FP1
DSA enhancements that alert the user when users switch between failover and
failback configuration. Improved handling of network timeouts.
IV55781: SERVICEABILITY IMPROVEMENTS IN 611 FP1
Serviceability improvements, which include improved error messages for
GetHTTP and services.



List of Impact APARs that have documentation updates or have additional information:

IV20165: E-MAIL READER DELETES E-MAILS AFTER READING THEMe
The email reader service reads incoming email, and runs policies based on the
contents of the email.
To stop the email reader from deleting emails after you read them, add the
following property to the <EmailReaderName>.props file.
<emailreadername>.deleteonread=false
Where <emailreadername> is the email reader service name. Restart the service.
This only works for IMAP email servers.

IV37369: OBJECT.PROTOTYPE.TOSTRING.CALL(OBJ) RETURNS {}
If a customer is using Object.prototype.toString.call(obj) in a javascript policy,
and wants to follow the javascript standard, he can add the following property
to NCI_server.props file -

impact.featureToStringAsSource.enabled=false

When the property is set to false, the data follows the JavaScript standard and
the data output by the Log function is not the same as in IPL. To make the
output the same in JavaScript and IPL, make the value true but this does not
follow the javascript standard.

IV38585: NCI_EXPORT NOT EXITING CLEANLY WHEN RUNNING ON A NON PRIMARY IMPACT
NCI_EXPORT restriction: nci_export will not execute on the non-primary member of a cluster.

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcoolimpact.doc_6.1.1.1/
admin/imag_tools_nci_export_c.html

IV40158: ABILITY TO CHANGE NUMBER OF POLLING INTERVALS
In order to make the readEventBuffer store the events for a longer interval, the number of
intervals can be updated. The default number is 3.

Add the following property to the <CLUSTERNAME>_<readername>.props. file (eg NCI_omnieventreader.props file)-

impact.<readername>.numreaderbuffer=4

The default value for this property is 3.

IV40179: ERROR MESSAGES FIRST APPEAR ON 6.1 AND 6.1.1 DURING STARTUP, DUE TO THE FACT THE
NAMESERVER IS NOT INITIALISED YET
When the Impact Server is started during the installation, the following message
is displayed in the netcool.log file:

Unable to login to configured name servers host , port

The message occurs because the Name Server can take time to initialize while
Netcool/Impact starts. You can ignore this message. It is normal and it
disappears when the Name Server server is initialized.

IV43157: ALL SERVERS IN A CLUSTER ARE REQUIRED TO USE THE SAME ADMIN UID AND PASSWORD
If you are configuring the Tivoli® Integrated Portal profile for a cluster
of servers, you must use the same user name and password for all the servers in
the cluster.

IV44875: SET JREXEC TO LOG TO FILE IS NOT WORKING
Documentation has been updated on JRExec server logging.

IV45481: NO DOCUMENTATION ON THE REQUIRED HTTP AUTHENTICATION FOR THE IMPACT 6.X WEBSERVICES
Documentation has been updated for Impact web services.

IV45569: DOCUMENTATION NEEDED ...HOW TO HANDLE BUILD-UP OF "ORPHANED" FILES, CREATED FOR XINY DATATYPE
A new policy has been added - XINY_DataType_PurgeData - to remove aged data items. More
information can be found in the Troubleshooting Guide.

IV46185: JAVACALL METHOD FAILS WITH JAVA.LANG.ILLEGALACCESSEXCEPTION-CANNOT ACCESS A MEMBER OF CLASS JAVA.UTIL.HASHTABLE$HASHITERATOR
Documentation has been updated for the NewJavaObject function.

IV46512: THERE'S A NEED TO DOCUMENT THE FACT THAT ONE NEEDS TO RESTART IMPACT FOR JVM TO RELEASE ANY LOADED JAR FILES FOR WEBSERVICES
Documentation has been updated to specify the procedure of what to do when a user compiles a wsdl file
using classes from a previously compiled file.

IV47057: DATA TYPE QUERY CACHING RETURNING BAD DATA
Documentation on Data caching information has been updated.

IV47454: INSTRUCTIONS ON HOW TO RUN UPGRADE PACAKAGE FOR IMPACT 6.1.1 ON CONSOLE OR SILENT MODE
Documentation on How to upgrade from Netcool/Impact 6.1 in console mode has been added.

IV50673: INCORRECT/UNCLEAR DOCUMENTATION FOR HANDLING EXCEPTIONS

IV50776: DURING UPGRADE WE WILL OVER WRITE ANY CUSTOMIZED MWM POLICIES WITH NEWER THE MWM DEFAULT POLICY'S VERSIONS

IV51431: NEED TO DOCUMENT THAT DOT NOATION CAN NOT BE USED IN THE NAMING OF POLICIES, SERVICES, DATA TYPES, DATA SOURCES, AND PROJECTS.
Documentation has been updated to note that Dot notation "." can not be used in the naming
of POLICIES, SERVICES, DATA TYPES, DATA SOURCES, AND PROJECTS.

IV52651: DATABASEREADER NOT WORKING PROPERLY WHEN USING GETUPDATES ON DATABASE TABLE'S TIMESTAMP FIELD
Database event reader service

An additional property can be added to the NCI_XXX.props file in order to match the
the date and time format of the timestamp field in the external database.
Where NCI is the name of the impact instance and XXX is the name of the database
event reader.
An example of this property is:
impact.XXX.formatpattern=dd-MMM-yy hh.mm.ss.SSS aaa

IV55778: JABBER UPDATES IN 611 FP1
An additional property can be added to the JabberReader property files if password is required to
login to a group.

impact.<jabberreader>.groupchatpassword=passwordToChatWithGroup

For e.g. if the reader is the DefaultJabberReader, then add the property shown below to the
NCI_defaultjabberreader.props file. If this property is present, it will be used while
login to the group.

impact.defaultjabberreader.groupchatpassword=passwordToChatWithGroup



============================
6.0 New support and features
============================
6.1 Additional Browser Support with Fix Pack 2

Impact 6.1.1 supports FF ESR 31 and IE 11 with this Fix Pack 2.
IBM strongly recommends updating to TIP 2.2.0.15 if support is
required for FF ESR 31 and IE11.

6.2 Additional Browser Support with Fix Pack 1

Impact 6.1.1 supports FF ESR 10 and FF17 with this Fix Pack 2.
IBM strongly recommends updating to TIP 2.2.0.13 if support is
required for FF ESR 24 and IE10.

This Fix pack supports Internet Explorer 9(IE9) in
"Internet Explorer 9" browser mode which is the default mode, not
in "Internet Explorer 9 Compatibility View" browser mode.
The document mode is automatically set by TIP and should remain
'IE7 standards'.

6.3 Additional Platform support with Fix Pack 2
None

6.4 Additional Platform support with Fix Pack 1

This Fix Pack 2 has been tested on Solaris 11, SuSE 11.3
and RHEL 6.5 in addition to the platforms supported
in Impact 6.1.1 GA.


6.5 eWAS Fixes and Upgrades

Please Note: When updating eWAS, any IBM product service that uses the eWAS should
be set to Manual start and the machine should be rebooted before the Update.
You must confirm that the services did not start before running the install
and ensure you backup the eWAS using the backupConfig command.

Netcool/Impact 6.1.1 Fix Pack 2 was tested and verified on
WebSphere Application Server (eWAS) 7.0 Fix Pack 33 (which is included in TIP 2.2.0.15)

Please follow the instruction if you want to perform the upgrade:

1 - If you do not have the UpdateInstaller tool for WebSphere Application
Server - download and install it from.

http://www-01.ibm.com/support/docview.wss?uid=swg21205991

2 - Install the eWAS and WASSDK packages

o Run the backupConfig command to back up configuration files.
http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tcfg_svr_conf_backup.html


o Stop all application server processes.
The product might not continue to operate successfully if you attempt to
install Fix Pack while embedded WebSphere Application Server related Java
processes are still running.

o Download the eWAS and WASSDK maintenance packages from
ftp://ftp.software.ibm.com/software/websphere/appserv/support/fixpacks/was70/cumulative/cf70035

embedded WAS AppServer: 7.0.0-WS-WASEmbeded-<osarch>-FP0000035.pak
WAS SDK: 7.0.0-WS-WASSDK-<osarch>-FP0000035.pak


Place both maintenance pack files into the update installer maintenance directory:

<updi_install_root>/maintenance, where <updi_install_root> is the installed
location of the Update installer.

o To install downloaded maintenance packages

Open a command shell window and change directories to the
<updi_install_root> install location of the Update Installer.
cd <updi_install_root>

Use the "update" command to install the maintenance package that you
downloaded into <updi_install_root>/maintenance directory.

For Windows
update.bat

For Linux or UNIX platforms:
./update.sh

The logs for update will be available in <appsrv_install_root>/logs/update
folder.

For the Product Selection Directory path, point the installer to the
Impact <installdir>/tipv2 directory.

For the Maintenance Package Directory Selection, point the installer to the
UPDI maintenance directory: <installdir>/tipv2/WebSphereUpdateInstallerV7/maintenance

Refer to the following file for detailed information on the use of the
"update" command, including silent mode installation.
<updi_install_root>/docs/readme_updateinstaller.html

3 - Verify the eWAS version after fix pack installation:

# for AIX, HP-UX, Solaris and Linux, open a login shell
cd <eWAS_install_location>/bin
./versionInfo.sh

# for Windows open a command prompt:
cd <eWAS_install_location>\bin
versionInfo.bat

4 - Proceed to restart your eWAS.


6.6 Enhancements in Fix Pack 2
None

6.7 Enhancements in Fix Pack 1

Fix Pack 1 includes the following enhancements:
- UI Provider Enhancements, you can show status and percentage in topology,
tree, table, and list widgets.
- UI Provider - Large table model support for Apache Derby and HSQLDB
databases.
- OSLC security requirements can be enabled or disabled by using a script.
- Jabber Updates to use the smack library.
- Web Documenter security enhancements. The Web Documenter can be viewed
only by a logged in user.
- Additional policy functions, Escape, and Illegal to escape special characters and
filter content from strings.
- DSA enhancements, that alert you when you switch between failover and
failback configuration. Improved handling of network timeouts.
- Serviceability improvements, which include improved error messages for
GetHTTP and services.
- Configuring Netcool/Impact to send messages to Tivoli Monitoring Universal
Message Console. Now uses the ITMLibraryFunctions.zip file that is available
for download from Netcool/Impact devWorks wiki in the Scenarios and Examples
page.
- Policy preferences updates that include the option to enable the table preference
for navigation to enhance performance.


6.8 Deprecated features in Fix Pack 2
None

6.9 Deprecated features in Fix Pack 1

The following features are being marked as deprecated in this release.
- Web Services Distributed Management (WSDM) functions.
– WSDMGetResourceProperty
– WSDMInvoke
– WSDMUpdateResourceProperty
- Web Services Notification Listener Service
- Cramer DSA
- Socket DSA
- External SVN, RCS, and ClearCase® as version control systems.

6.10 MSN support in Fix Pack 1

Messenger was retired by Microsoft in April 2013. As a result, Jabber integration
with MSN is no longer supported by Impact.

===============================
7.0 Known Issues in Fix Pack 2
===============================
7.1 Auto saved Policies not cleaned up
The auto saved copy of a policy is not removed after the recovered policy is
saved. There is no issue with leaving the auto saved copy on the Impact server.
It will be overwritten by the next auto saved copy of the policy.

However, if user wants to manually remove the auto saved copy, user needs to
log in to the Impact server and then manually remove the copy from:

<install>\impact\policy\.autoSaved\defaultWIMFileBasedRealm\<user>\

7.2 Unable to save ObjectServer DataType when the Impact server name is long
There is an issue with saving ObjectServer DataType when the Impact server name
is longer than 23 characters.

To workaround this issue, user needs to override the APPLICATIONNAME property
with a shorter string.

Workaround:
1. Log into the Impact server
2. Navigate to the <installDir>/impact/etc/ directory
Open the appropriate .ds file for the object server you want to connect to:

<serverName>_<datasourceName>.ds

e.g.

NCI_PRI-1_TEST-2_FINAL-impact_defaultobjectserver.ds

3. Add the following properties to the file:

<datasourceName>.ObjectServer.NUMDSPROPERTIES=1
<datasourceName>.ObjectServer.DSPROPERTY.1.NAME=APPLICATIONNAME
<datasourceName>.ObjectServer.DSPROPERTY.1.VALUE=NCI

e.g.

defaultobjectserver.ObjectServer.NUMDSPROPERTIES=1
defaultobjectserver.ObjectServer.DSPROPERTY.1.NAME=APPLICATIONNAME
defaultobjectserver.ObjectServer.DSPROPERTY.1.VALUE=NCI

NOTE: If user already has a datasource specific property in
the property file, then the above should be set to a number higher.
e.g
defaultobjectserver.ObjectServer.NUMDSPROPERTIES=2
defaultobjectserver.ObjectServer.DSPROPERTY.2.NAME=APPLICATIONNAME
defaultobjectserver.ObjectServer.DSPROPERTY.2.VALUE=NCI

4. Save the changes.

5. Restart the Impact server and UI server.


7.3 WEBSERVICES SECURITY NOT FUCTIONAL
If using WebService Security when making a WebService call,
(callProps.EnableWSS=true), the jar file tipv2/plugin/org.apache.axis2.jar
must be replaced by the new jar file impact/lib3p/org.apache.axis2-woden.jar

Restart is required.

7.4 If using WEBSERVICES SECURITY (WSS) user authentication, then the
impact/dsa/wsdsa/wss/conf/wscb.properties needs to be altered to only have
one entry. If there is more than one entry in the file, only the uid.1 and
pwd.1 will be read

7.5 Microsoft Internet Explorer 11.
IE11 (supported only with TIP 2.2.0.15) may cause unexpected behavior in
the Policy Editor, whereby the Policy List panel disappears when the Project
drop-down menu is selected. To circumvent this, simply click on a different
project in the Project drop-down list and then click again on the desired
project, to restore the correct layout


=======================================
8.0 Copyright and trademark information
=======================================

http://www.ibm.com/legal/copytrade.shtml

8.1 Notices

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not
apply to you.

This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the program(s)
described in this publication at any time without notice.

Microsoft, Windows, and Windows Server are trademarks of Microsoft
Corporation in the United States, other countries, or both.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino,
Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and
Pentium are trademarks or registered trademarks of Intel Corporation or
its subsidiaries in the United States and other countries.

Other company, product, or service names may be trademarks or service
marks of others.

Please read THE IBM Tivoli Netcool/Impact v5.1.1 NOTICES AND INFORMATION
in the file notices1.txt included in this Fix Pack before you proceed
with the download and installation of this Fix Pack. You can find the
additional notices file on the same webpage as this Fix Pack.

8.2 THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION

The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to certain
software code. The relevant terms and conditions, notices and other
information are provided or referenced below. Please note that any
non-English version of the licenses below is unofficial and is provided
to you for your convenience only. The English version of the licenses
below, provided as part of the English version of this file, is the
official version.

Notwithstanding the terms and conditions of any other agreement you may
have with IBM or any of its related or affiliated entities (collectively
"IBM"), the third party software code identified below are "Excluded
Components" and are subject to the following terms and conditions:

* the Excluded Components are provided on an "AS IS" basis
* IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT
NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND
THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE
* IBM will not be liable to you or indemnify you for any claims related
to the Excluded Components
* IBM will not be liable for any direct, indirect, incidental, special,
exemplary, punitive or consequential damages with respect to the
Excluded Components.

8.3 IBM obtained Smack V3.3.0 under the following current license from
Apache Software Foundation:

Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/