IM Relationship Resolution Information Center, Version 4.2

Release notes - IBM Relationship Resolution version 4.2 fix pack 2

Fix pack 2 for IBM® Relationship Resolution version 4.2 is available and includes new product capability in addition to maintenance.

Contents

About IBM Relationship Resolution

IBM Relationship Resolution 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 who") among customers, employees, vendors, and other external forces. IBM Relationship Resolution provides immediate and actionable information to help prevent threat, fraud, abuse, and collusion in all industries.

New functions in IBM Relationship Resolution version 4.2 fix pack 2

Several new functions and enhancements are included in this fix pack:

Attribute and scoring customization
IBM Relationship Resolution provides functional enhancements for configuring attribute data and integrating scoring algorithms. These changes expand the size and types of identity data that can be compared and scored and enable the addition of new scoring algorithms in the entity resolution process. These capabilities are added with fix pack 2 and are generally referred to as attribute and scoring customization. For example, you could add identity data derived from fingerprints, retina scans, or DNA tests and compare and score them using a scoring plugin that includes an appropriate comparison algorithm.
Expanded Service API
The Expanded Service API updates IBM Relationship Resolution Web services by providing an object-rich SOAP API and corresponding UMF API of Web services operations. It also includes pipeline load balancing functionality for IBM Relationship Resolution Web services, which allows for pipeline redundancy and enhanced performance.
Visualizer usability enhancements
The user interface for the Visualizer has been enhanced to make tasks easier and provide a more intuitive and logical user experience.
Note: All Visualizer users must clear their browser cache before launching the Visualizer after the IBM Relationship Resolution 4.2 fix pack 2 installation. This allows the users to download the updated Visualizer files from the server.
IBM Event Manager updates
Fix pack 2 includes updates to the Event Manager additions provided in fix pack 1. Event Alert history is now on the Entity Resume. The Entity Events screen shows all event data associated with an entity, whether or not the event triggered an alert. The All Events report is added to reflect Entity Events.
Note: This fix pack and included documentation is provided in English. If you install the IBM Relationship Resolution version 4.2 fix pack 2, you will only see the fix pack function information when English is selected in your browser settings.

IBM Relationship Resolution version 4.2 fix pack 2 maintenance items

Note: If you are upgrading an 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.
This fix pack includes the following maintenance items:
ipsdb00028684
Pipeline fails because clause is too large.
ipsdb00028704
Name scoring is done differently in the candidate building than in scoring section of the code.
ipsdb00028734
Pipeline pulls in all data attached to a disclosed relationship account.
ipsdb00027965
Scoring issue with Individual Culture Entities vs. Companies.
ipsdb00028777
Need a way to sequence output messages from entity resolution.
ipsdb00018874
Role Alert Detail report is missing details.
ipsdb00027904
Entity Relationship graph for an entity involved in an Event Alert properties pane shows duplicate information.
ipsdb00028394
Missing XML files.
ipsdb00018965
Issue with Disclosed Relations after 4.1 upgrade.
ipsdb00018496
Console entity-type value-checking.
ipsdb00018311
Console - field height.
ipsdb00017451
Console - Attribute Denial text change.
ipsdb00018265
SUIT - Index file.
ipsdb00028060
Duplicate disclosed relations with different descriptions.
ipsdb00030805
Visualizer file-load has missing Name record and Alert.
ipsdb00036154/28132
Empty NAME_GEN tags not handled properly in GNRNameHasher.
ipsdb00029256
Number matching produces unexpected relationships when hash_length is changed.
ipsdb0027529
"Passive Load - Num_DENIAL does not work correctly with Name Manager turned on.
ipsdb00030764
APAR PJ33242 GNR scoring issue fix.
ipsdb00045535
Confirm weight is not logged for attribute denial.
ipsdb00032540
Accented characters (French language) are displayed as question marks in the console.
ipsdb00028772
Child resolution data is missing from the master document.
ipsdb00028773
Pipeline does not publish deleted relationships.
ipsdb00051350 (ipsdb00029131)
Child ER Session does not publish UMF_MATCH.
ipsdb00045096
(APAR PJ34650) Relationships exist in EAS but not in EDW. UMF_ENTITY. Docs put through with a DSRC_ACTION of 'X' generate unexpected output messages and SEP_RELATION score changes.
ipsdb00045072
(APAR PJ34650) New Name Key solution.
ipsdb00050938
(APAR PJ34739) Performance issues for NC2 vs NM.
ipsdb00050820
(APAR PJ34725) Number uniqueness did not take into account NUM_LOCATION when stored in the entity structure. This is a problem when NUM_LOCATION confirmation is used. The entity structure only keeps the first number of matching type and hash, so when the same number from different accounts with a differing or missing NUM_LOCATION is used, inconsistent NUM_LOCATION confirmations result. In cases where this makes the difference between a 100 Like score and a lower score, this can cause un-resolve re-resolve loops.
ipsdb00050817
(APAR PJ34723) When using LAS only, the 'determine resolvability' function still decides which name comparator to use from the system_param table. In this case no name comparator should be used at all. This causes resolution rules to ignore LAS name scores when satisfying match merge rules and log 0,0,0 for LAS.
ipsdb00050821
(APAR PJ34725) Pipeline gets fatal error loading a record.
ipsdb000018188
IBM Relationship Resolution V4.2 Visualizer - Role Alert/Entity Graph - 'Hide Attribute' option is not available in Linux.
ipsdb00052245
Users need to be able to reload CEP rules while the system is running. A reload button has been added.
ipsdb00028031
Characteristic data in the Find By Attribute search-results list is displayed incorrectly when the gnrNameHasher feature is enabled.
ipsdb00052068
Cannot delete disclose relationship from Visualizer.
ipsdb00031104
A query in Pipeline Code is incorrect.
ipsdb00017527
Function 610 does not allow a single value.
ipsdb00017733
Pipeline should validate that DQM parameter indexes are sequential on startup.
ipsdb00016926
Validate MM configuration ID at startup.
ipsdb00031791
AP_RULE table is different between 4.2.1 Install and upgrade from 4.2.0.
ipsdb00018715
Errors with Console number-types, range checking, and validations.
ipsdb00018999
Errors in Visualizer - Hide Search entities.
ipsdb00053744
The pipeline mistakenly increments the number of location neutrals when other data (NAME, ADDRESS, etc.) is ingested and combined with other Event Reporting criteria.
ipsdb00051815
Missing entries in SEP_CONFLICT for DR.
ipsdb00052099
Cannot load a UMF file with blank lines through the Visualizer.

Maintenance items included from previous hot fixes:

The Degrees of Separation function

Console

Pipelines

The Passive Load feature

Visualizer

Search features

The SEP_RELATIONS table

Name Manager functions

Data display

Miscellaneous

System requirements

For information about hardware and software compatibility, see the detailed system requirements document at http://www-306.ibm.com/software/data/db2/eas/relationship/requirements.html or see the IBM Relationship Resolution Installation and Configuration Guide that is available on the Quick Start CD.

Announcements

You can search for the IBM Relationship Resolution 4.2 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.

Note: Several components will not be supported or developed further in future versions of IBM Relationship Resolution. It is recommended that all future development be done without using the following:
  • UMF file conversion utility - also referred to as acquisition file processor (AFP)
  • UMF database conversion utility - also referred to as general data acquisition (GDA)
  • net change utility - also referred to as net change engine (NCE).


Feedback

Last updated: 2009