IBM InfoSphere Identity Insight, Version 8.0 ISII Generally Available HotFix #5 Build # 8.0.0.140 Readme Oct 2011 Contents: ========= 1.Problems/issues addressed in this hotfix 2.Known issues 3.Prerequisites 4.Notes 5.List of Table/Views/Index that have been altered 6.Checksum information for downloads 7.Required files 8.Implementation steps 9.Install verification *************************************************************************** 1.Problems/issues addressed in this hotfix: ==================================== [ PMR # 73027499000] Enable limits to detail logging to improve efficiency and performance. This change means that only the most related and best details are logged. For example, the scores that that hit the rule are logged, but not all names. [ APAR # PJ39217] Unique constraint violation error during load causing pipeline to fail. [ APAR # PJ39121] Fixed UMF_MERGE message FROM/TO DSRC_ACCT_ID ordering issue. [ APAR # PJ39590] Unresolve - re-resolve loops occur on large entities when a disclosed relation is added (or via an X-message against the entity). Unresolve continues as a CPU-intensive process and needless database updates are triggered. [ CQ # ipsdb00096786] DB2 Database transport lock handling improvement . [ CQ # ipsdb00096787] Long running transactions occurred due to unresolve/re-resolve looping. In ambiguously-merged accounts, the unresolve process was non-deterministic in the order it would attempt to re-assemble the examined entity. [ CQ # ipsdb00096786] Alteration to Index - add ENTITY_ID to DSRC_ACCT.IX_FORCED_RESOLVE_ID. This improves linking when doing merges. [ APAR # PJ39633] Visualizer issue with displaying a long list of numbers in the Find By Attribute Screen. [FITS # MR0916113444 "Role Alert Rule" dropdown too small; cannot see entire name of alert role on "Role Alert Status Report" page. *************************************************************************** 2. Known issues: ================= The MATCH_ID column on the SEP_CONFLICT_REL table is currently defined as a NUMBER(10). This can artificially limit the size of values that can be stored in this table, and can cause SQL insert failures and pipeline shutdown with large data-volumes. To allow larger Match-ID numbers to be stored, this column-type for the MATCH_ID column may be safely altered to be: BIGINT (DB2, MSSQL) or NUMBER(19) (Oracle) for the SEP_CONFLICT_REL table *************************************************************************** 3. Prerequisites: ================= IBM InfoSphere Identity Insight, Version 8.0 Hotfix 4 files (Build#135 8.0.0.20110518-0135 ) are required as a Prerequisite before applying Hotfix #5 files. *************************************************************************** 4.Notes: ================= When upgrading from this (or subsequent) v8.0.0 hotfixes to version 8.1.0, it is essential that you immediately upgrade one step further to version 8.1.0 Fixpack 1 (v8.1.0.1) or later. Failure to do so will result in the loss of the previous v8.0.0 hotfix new functionality and code-fixes. *************************************************************************** 5. List of Table/Views/Index that have been altered: ===================================================== The install script drops and then recreates the following existing index : DSRC_ACCT.IX_FORCED_RESOLVE_ID ***************************************************************************** 6. Checksum Information for downloads: ======================================== aix_pwr4_ISII_8.0.0.140.tar cksum: 2442887498 size: 159631360 bytes hpux_ia64_ISII_8.0.0.140.tar cksum: 2170530597 size: 116234240 bytes linux_s390x_ISII_8.0.0.140.tar cksum: 265842924 size: 66457600 bytes linux_x86_ISII_8.0.0.140.tar cksum: 268349221 size: 62330880 bytes solaris_sparcv9_ISII_8.0.0.140.tar cksum: 4042601694 size: 84008960 bytes win_x64_ISII_8.0.0.140.zip cksum: 2916255416 size: 35000649 bytes win_x86_ISII_8.0.0.140.zip cksum: 1082953873 size: 33735720 bytes ***************************************************************************** 7. Required files: ==================== Java: ibm-is-ii-visualizer.ear SQL: DB2: dsrc_acct_ix_forced_resolve_id_db2.sql soa_addr_matched_during_er.sql Oracle: dsrc_acct_ix_forced_resolve_id_ora.sql soa_addr_matched_during_er.sql MSSQL: dsrc_acct_ix_forced_resolve_id_mssql.sql soa_addr_matched_during_er_mssql.sql Binaries: pipeline.exe cmesend.exe Plug-ins: libdateAttrScoring.so libnameAttrScoring.so libdefaultAttributeScoring.so libcircaDateAttrScoring.so libbinaryAttributeScoring.so libhttpCalloutScoring.so or dateAttrScoring.dll defaultAttributeScoring.dll circaDateAttrScoring.dll nameAttrScoring.dll binaryAttributeScoring.dll httpCalloutScoring.dll ******************************************************************************** 8. 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. Run the following SQL: DB2: dsrc_acct_ix_forced_resolve_id_db2.sql soa_addr_matched_during_er.sql Oracle: dsrc_acct_ix_forced_resolve_id_ora.sql soa_addr_matched_during_er.sql MSSQL: dsrc_acct_ix_forced_resolve_id_mssql.sql soa_addr_matched_during_er_mssql.sql 7. 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 "Visualizer Application" is checked. 2) Browse to the "iibm-is-ii-visualizer.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. 6. If you did not choose to restart Websphere Application Server after reconfiguration on step 4, do the following: a) Stop WebSphere Application Server. b) Start WebSphere Application Server. 7.Start the pipelines. ************************************************************************ 9. Install verification ======================= Execute the pipeline without options and confirm that the output shows: ** pipeline v8.0.0.140