IBM InfoSphere Identity Insight, Version 8.0 ISII Generally Available HotFix #4 Readme (GA HF4) ISII 8.0.0.135 May 2011 Contents: ========= 1. Problems/Issues addressed in this hotfix 2. Prerequisites 3. Notes 4. List of Table/Views/Index that have been altered 5. Required files 6. Implementation steps 7. Install verification *************************************************************************** 1. Problems/Issues addressed in this hotfix: ============================================ [ APAR # PJ38492 / CQ # ipsdb00087179 ] Infinite deadlock retries [ APAR # PJ38759 / CQ # ipsdb00091773 ] 2 digit year, plus timestamp, is being displayed in From and Thru dates on Visualizer Entity Resume report [ APAR # PJ38916 / CQ # ipsdb00092742 ] Web services stating record processed when it failed [ APAR # PJ38763 / CQ # ipsdb00090827 ] Pipeline crash on delete [ APAR # PJ38885 / CQ # ipsdb00092386 ] CircaDOB params cross link w/ DOB [ APAR # PJ38958 / CQ # ipsdb00092323 ] Pipelines need a delay if no data in transport table [ APAR # PJ38892 / CQ # ipsdb00038892 ] Ignoring COMPANY culture resulting in name parsed [ APAR # PJ38860 / CQ # ipsdb00038860 ] QSMNA exception for COMPANY names w/ "AND", "&" [ CQ # ipsdb00092433 ] SOA_ADDR_MATCHED_DURING_ER view not returning EXACT ADDRESS [ CQ # ipsdb00091643 ] Pipeline crashes on shutdown CEP-enabled *************************************************************************** 2. Prerequisites: ================= IBM InfoSphere Identity Insight, Version 8.0 Fixpack 2 (Build 8.0.0.130) must be installed. ******************************************************************************************* 3. Notes: ========= 1. Under certain situations, the pipelines can cause unnecessary load on the database server. This can occur if using Database Transport input source and the Database Transport database table is empty. To avoid this problem, a new 'pollingdelay' parameter has been introduced to enable the polling interval to be controlled. This value is in milliseconds. Example Hotfixed URI [pipeline] InputTransports=db2://CCadmin:passw0rd@Customers/?table=EXAMPLE_DBTRANSPORT&pollingdelay=10000 2. Under certain error-conditions, the pipeline output may display the following 'CRITICAL ERROR' message when processing records 05/17 12:41:47 [pipeline:4536] CRIT: CRITICAL ERROR: 05/17 12:41:47 [pipeline:4536] CRIT: { 05/17 12:41:47 [pipeline:4536] CRIT: Unrecognized Message Received (message) 05/17 12:41:47 [pipeline:4536] CRIT: } In these situations, please refer to the UMF_EXCEPT table for further detailed information regarding the cause of the error. You can also see the UMF Exceptions tab in the Configuration Console. 3. Name+DOB rules being incorrectly hit by Circa-DOB processing is resolved. * Known Circa Month range matching limitations will be further addressed in the future. *********************************************************************************************************************************** 4. List of Table/Views/Index that have been altered: =================================================== The script drops and then recreates the following existing view: SOA_ADDR_MATCHED_DURING_ER *************************************************** 5. Required Files: ================== Microsoft Windows ------- Java: ibm-is-ii-webservices.ear SQL: Oracle and DB2: soa_addr_matched_during_er.sql MSSQL: soa_addr_matched_during_er_mssql.sql Binaries: pipeline.exe cmesend.exe Plug-ins: dateAttrScoring.dll defaultAttributeScoring.dll circaDateAttrScoring.dll nameAttrScoring.dll binaryAttributeScoring.dll httpCalloutScoring.dll Additional files: SifterRules.ibm EntityResume.rptdesign AIX / Solaris / Linux_x86 / Linux_x64 / HP-UX / Linux on zOS -------------------------------------------- Java: ibm-is-ii-webservices.ear SQL: Oracle and DB2: soa_addr_matched_during_er.sql MSSQL: soa_addr_matched_during_er_mssql.sql Binaries: pipeline cmesend Plug-ins: libdateAttrScoring.so libnameAttrScoring.so libdefaultAttributeScoring.so libcircaDateAttrScoring.so libbinaryAttributeScoring.so libhttpCalloutScoring.so Additional files: SifterRules.ibm EntityResume.rptdesign *************************************************************************************************************************************** 6. Implementation Steps ======================= To apply the hotfix, please do the following: 1. Copy the required files to your hard drive. 2. Stop the pipelines. 3. Create a backup of the pipeline and plug-in files (listed above). 4. Replace the pipeline file by copying the new version into bin: For Windows: \bin Other platforms: /bin 5. Replace the plug-in files by copying the new versions into: For Windows: \bin Other platforms: /lib 6. Back up the SifterRules.ibm from: For Windows: \data Other platforms: /data 7. Replace the SifterRules.ibm file by copying the new versions into: For Windows: \data Other platforms: /data 8. Back up the EntityResume.rptdesign from: On the Application-Server, backup the EntityResume.rptdesign from /srd-home/ibm-eas-visreports/reports. 9. Replace the EntityResume.rptdesign file by copying the new versions into: /srd-home/ibm-eas-visreports/reports 10. Run the following SQL: For Oracle/DB2: soa_addr_matched_during_er.sql For MSSQL: soa_addr_matched_during_er_mssql.sql 11. Launch the Config Utility from the "/installer/util" directory. (For Unix/Linux: Note - the eacfg tool requires that an X-windows session is established with the Application server. Please contact IBM Support if you do not run X-windows in your environment). (For Windows: The eacfg tool can be run without requiring an X-windows session.) a) Type eacfg to see the help file for the command. b) You can launch the tool using "eacfg -i -l ../logs" c) Make sure you are on the Patches and Hotfixes section, which is the very first screen of the tool. 1) Confirm that the box next to "Web Services Application" is checked. 2) Browse to the "ibm-is-ii-webservices.ear" from your hard drive. 3) Click on Apply. 4) You can choose to restart WebSphere Application Server after reconfiguration is complete. 5) The Config Utility tool should have given you the 'Updated successfully' message. 12. If you did not choose to restart Websphere Application Server after reconfiguration on step 11, do the following: a) Stop WebSphere Application Server. b) Start WebSphere Application Server. 13. Start the pipelines. ********************************************************************************************************************************** 7. Install Verification ======================= 1. Execute the pipeline without options and confirm that the output shows: ** pipeline v8.0.0.135 2. Please open a web browser and type http://server-name:http-port#/easws/api/soap - - webservice Status page You should get the following: 8.0.0.135 - 20110518_1813 - - - - - - - - - - - - - - - - - - - - SERVICE_NAME = EntityResolver WRAPPED_DOCUMENT_LITERAL = true RESOURCE_SUBDIRECTORY = soap SERVICE_NAME = EntityResolver