IM InfoSphere Identity Insight, Version 8.0

Release notes - IBM InfoSphere Identity Insight version 8.0 fix pack 2

IBM® InfoSphere Identity Insight version 8.0 fix pack 2 is available and includes new product capability in addition to maintenance.

Contents

About IBM InfoSphere Identity Insight

IBM InfoSphere Identity Insight helps organizations solve business problems related to recognizing the true identity of someone or something ("who is who") and determining the potential value or danger of relationships ("who knows whom") among customers, employees, vendors, and other external forces. IBM InfoSphere Identity Insight provides immediate and actionable information to help prevent threat, fraud, abuse, and collusion in all industries.

IBM InfoSphere Identity Insight Version 8.0 fix pack 2 contents

This fix pack includes product maintenance and documentation updates. In addition, it provides a new option for improved address data standardization. Please see the installation topics for fix pack 2 (in the FP2 section of the information center or attached – if this is the stand-alone version of the release notes.

Note: This fix pack and included documentation is provided in English. If you install the IBM InfoSphere Identity Insight version 8.0 fix pack 2, you will only see the fix pack function and related information updates in the information center when English is selected in your browser settings.

The most current version of these release notes comes with the product as a separate Identity Insight release notes for v8.0_FP2 html file. For the latest changes or corrections to this information, see the Support Portal information below.

The following updates have been made to how the product handles name data:
Deprecated schema tables
The following tables are deprecated:
  • LAS_CONFIG
  • LAS_CULTURE_CODES
Customers can safely drop these tables manually from their IBM InfoSphere Identity Insight schema. The product installation program does not automatically remove these tables when customers upgrade to V8 fix pack 2.
Updated API component libraries
The underlying IBM Global Name Management API component libraries have been updated to Version 4.2.
Name Manager system parameter CROSSCHECKCULTURE update
Existing customers: After upgrading to V8.0 fix pack 2, enable the CROSSCHECKCULTURE setting.
IBM Global Name Recognition Name Hasher updates
The following list highlights updates to Name Hasher:
Enhanced name hashing capabilities
Expands fuzzy name matching during entity resolution or when ER-like searches run through the pipeline (
New DQM rules: 282, 610
New system parameter configured in the Configuration Console (HASHLESS_NAMES_ARE_GENERIC)
Migration from previous version of Name Hasher
No Web service - DQM 660 (previously external component that communicated with an external WebSphere servlet to generate HTTP network traffic.. Enhanced name hashing functionality is built into the pipeline as an embedded component. "New" Name Hasher must be properly configured. Use DQM 282 + DQM 610.
Additional migration information is provided if you used previous version of Name Hasher. (In the information center, see Configuring the system for data > Configuring data in the system > Configuring name data > Enhanced name hashing with the IBM Global Name Recognition Name Hasher.)
Generating alternate name parses
New DQM rule 289 - expands name parses that meet the parse threshold configured for the DQM rule + secondary parses. The ability to generate secondary name parses supports generating multiple name hashes for non-Name Hasher configurations and expands the fuzzy matching capabilities for enhanced name hashing for Name Hasher configurations.
Enhanced gender determination ability
New DQM rule 258 - provides culturally-aware gender determination. Dynamically analyzes names and created gender characteristics for the incoming identity record.
Existing DQM 255 with Gender param is OK to use as an alternate method for determining the gender of names, but it is not culturally-aware. Customers cannot use both the Gender param from DQM 255 and the new gender determination capabilities of DQM 258.
Expanded Service API enhancements
New Web services enhancements are added for configuration, alerting, relationships, and resolution:
  • getEventTypes
  • getEventAlertsByFilter
  • getEventAlertByID
  • getRelationshipBetweenEntities
  • getDirectEntityRelationships
  • getEventDetailByFilter
  • getEventDetailByID

IBM InfoSphere Identity Insight Version 8.0 fix pack 2 maintenance items

This fix pack includes maintenance item fixes and corrections.

Note: If you are upgrading from an older IBM Relationship Resolution installation that uses IBM Entity Analytic Solutions Name Manager, please look at the IBM Entity Analytic Solutions Name Manager configuration topics in the information center for updates.

Pipeline maintenance items

Unresolve and related issues
Improvements have been made to the memory-usage and CPU-usage characteristics for Entity-resolution processing.
Legacy IW*WEBSERVER (srd.wsdl)
Some EQ searches that exceeded the max record count on returns resulted in the pipeline returning a properly formatted XML message but the XSLT in the Web services corrupted it.
Insertion of SQL Comments into all SQL-calls (with enable/disable switch)
This enhancement is required to support large-scale parallelization of pipeline-inserts in PPP / threaded environments and to stop latch-contention on DB2. By adding unique identifier information to the 'header' of each SQL query, the database-engine can allocate separate space and latches for each instance of a given SQL query per pipeline thread and pipeline rather than sharing the same SQL-query-string across pipelines and threads. This increases memory-usage on the database-tier (depending on number of pipelines and number of threads per pipeline), but reduces latch-contention.

This feature is disabled by default. To enable it, set the following value in the [SQL] section of the pipeline.ini file: INSERT_COMMENTS=Y.

Infinite deadlock retries
In HTTP mode, the pipeline should not retry transactions (bidirectional messages), but should return errors to the client so the client can retry.
gnrNameHasher did not handle UTF-8 characters correctly
Client responses are now correctly encoded in UTF-8 when appropriate.
Resolved deadlocks and the error limit count
Resolved deadlocks are no longer counted in the error limit.
SOA process() function with data with an ampersand ('&') problem
You can now call the SOA process() function with data that has an ampersand ('&') in it. This applies to all SOA functions and for other characters.
UNUM_MATCH_PERCENTAGE - new pipeline.ini parameter
The Unique Number Matching percentage parameter can be set from 1 to 100. The higher the number, the more precisely an incoming Unique-number has to match in order to generate a Unique-Number-Match.

To implement: In the [MM] section of your pipeline.ini file(s), add the following entry (case-sensitive) UNUM_MATCH_PERCENTAGE=xx. The default is 75 if not specified.

Incorrect attribute denials
The system no longer denies when there is a common attribute.
Additional resolved issues and reported problems
  • Address scores severely penalized for different postal code 4-digit extensions.
  • Missing index on SEARCH table corrected.
  • SOA Identity calls did not return Last-Update, Sys-Create or Source-Create dates.
  • Updated SifterRules.ibm file.
  • Namesifter feature no longer over-categorizes names as Company-names.
  • Pipeline startup no longer hangs if QS-AVI feature is enabled without the International address-database installed.
  • Pipeline transaction rollback occurring at database server, but UMFLOG incorrectly logging that the transaction was successfully processed.
  • Additional incorrect Gender record logged during soft-delete.

Visualizer maintenance items

Missing alert on Upgrade from 8.0 to FP1
The Visualizer will now successfully obtain Match Merge rule information from a new IIv8.0 database column if it is populated, or fallback to the previous method if it is not populated.
Additional resolved issues and reported problems
  • The Visualizer would hang under certain situations where accounts were deleted from the system. The entity resume would fail to display.
  • Disclosed relations role alert graph was not displaying correctly if description left blank.
  • Entity resume was not using latest in the resume header section.

Miscellaneous maintenance items

Documentation corrections
Various topics throughout the content have been corrected or improved.
Updated CEP Rule-Builder deployment and instructions
When the Fixpack2 installer is run on the Application Server, a new zip file is provided as part of the IBM Identity Insight installation on the Application Server (<RR_INSTALL>/cep/CEP_3.0.1.1.03-J2SE.zip). This zip file contains updated files that enable you to obtain an ArrayList containing the values of the "externalId" attributes of the events which participated in the situation, for the IOutputSituation function. This new function is available when creating CEP Rules using the Client-side Eclipse-based CEP Rule-Builder (previously provided in IIv8.0 in the <RR_INSTALL>/cep/CEP_3.0.1.01.zip file). Once the fix pack 2 Installer has been run on the Application Server, you must perform the following Manual steps to install these updated files into yourr Eclipse (CEP Rule-builder) framework:
  1. Copy the new CEP zip file down to the client machine where the CEP Rule-Builder is being run.
  2. Expand the zip file.
  3. Copy the files to the following directory on the client <CEP_DEPLOY_DIRECTORY>\CEP_3.0.1.1.00\eclipse\plugins\com.ibm.amit.commonlib_3.0.1.1.
MQ 6.0.1.1 on HP (11i v3)
Use MQ 6.0.1.1 on HP (11i v3) rather than MQ 6.0.1.0.

System requirements

For information about hardware and software compatibility, see System requirements and planning.

Announcements

You can search for the IBM InfoSphere Identity Insight 8.0 announcement at http://www-306.ibm.com/common/ssi/OIX.wss. See the announcement for the following information:
  • Detailed product description, including a description of new functions
  • Product-positioning statement
  • Packaging and ordering details
  • International compatibility information

Known problems and issues

Known problems are documented in the form of individual technotes in the Support knowledge base at http://www-306.ibm.com/software/data/db2/eas/relationship/support.html:
  • Under Search Support, in the Enter terms, error code or APAR # field, enter a keyword, phrase, error code, or APAR number to search on.
  • Select Solve a problem.
  • Click the Search button.

As problems are discovered and resolved, the IBM Support team updates the knowledge base. By searching the knowledge base, you can quickly find workarounds or solutions to problems.

At time of publication, there were no known installation problems. Be sure to check the Support knowledge base for any late-breaking information.



Feedback

Last updated: 2011