This version of IBM® Relationship Resolution contains many new features
and product enhancements.
For the most recent information about IBM Relationship Resolution Version
4.2, go to the IBM Relationship Resolution Web site located at http://www-304.ibm.com/jct03001c/software/data/db2/eas/relationship
New features and enhancements
The following features
and enhancements have been added to IBM Relationship Resolution in Version
4.2:
- Reorganized and enhanced product documentation, which is now presented
in an information center
- Added the ability to configure entity resolution scoring, so that the
system can use the sum score of each configured confirmation and denial, rather
than scoring based on the first confirmation or denial score satisfied
- Added support for multi-threaded pipeline processing
- Added a configuration and maintenance utility (Examples of when to use
this new utility include deploying a new EAR file and changing port numbers
for SNMP agents or database connections.)
- Added the ability to handle Latin-1 character set
- Updated the IBM Entity Analytic Solutions Name Manager capabilities for
more name scoring options
- Improved alert filtering configuration capabilities
- Improved error handling and logging
- Added enhanced query capabilities
- Added the ability for users to disclose relationships, enabling conflict
detection
- Added support for custom DB2 database schemas (However,
reports in the Configuration Console and the Visualizer do not
work if a custom DB2 database schema is specified.)
- Visualizer: Added the ability to use localized date formats and sorting
features to display system dates and to sort columns according to your specific
locale
- Visualizer: Fully enabled support for new features, including enhanced
query capabilities (Find by Attribute) and disclosed relationships
- Visualizer: Redesigned entity resume and alert screens
Platform additions and deprecations
IBM Relationship
Resolution now supports the latest versions of several platforms. Other platforms
were deprecated as part of this release. For more information, see the IBM
Relationship Resolution Installation and Configuration Guide.
Product fix history
This release includes the following
version 4.1.0 hot fixes:
- EAS 4.1.0.89 Hot Fix (August 2006)
- Visualizer and Pipeline issues in version 4.1 that were corrected by this
hot fix:
- Matching details on the Visualizer Conflict screen
were not correct in some cases. (In version 4.2, the Conflict screen
has been renamed to the Role Alert screen.)
- Matching details on the Search Results screen were
not correct in some cases.
- Clicking on relationships on the Visualizer Entity Resume screen
did not highlight the correct set of related data items in some cases.
- The SEP_RELATIONS and SEP_CONFLICT_REL tables used outdated entity resolution
IDs.
- Name matches were logged in the ER_DETAIL table when the rule used did
not require name matches.
- Name confirmation occurred, but the name confirmation did not log when
IBM Entity Analytic Solutions Name Manager was disabled or not required (a
0 value is in the rule).
- The SEP_RELATIONS table did not always update during an incomplete resolution
recovery.
- Passive load returned UMF without an ENTITY_ID, which caused a Visualizer
error.
- EAS 4.1.0.0096 Hot Fix (September 2006)
- Visualizer issues in version 4.1 that were corrected by this hot fix:
- The First Name field is no longer required on the Add
Entity and New Search screens.
- The relationship count on the Search Results screen
now displays correctly.
- The Likeness Score field was added to the Search
Result screens.
- Persistent searches now display in the Inbox based
on the case number and status. (In version 4.2, persistent searches have been
renamed to attribute alerts.)
- DB2 performance issues with Visualizer graphs and the entity resume were
resolved.
- The count of relationships for conflicts in the Conflict List screen
now displays correctly.
- In the Italian language file, the translation for 'State' was corrected
to 'Provincia'.
- The count of relationships and the likeness score in the Search lists
now show "0" instead of null when there are zero relationships.
- The count of relationships on the immediate Search Results screen
now displays correctly.
- Performance of functions dealing with the names of related entities was
increased
- EAS 4.1.0.0105 Hot Fix (November 2006)
- Issues in version 4.1 that were corrected by this hot fix:
- IBM Relationship Resolution Degrees of Separation fixes:
- Sometimes IBM Relationship Resolution Degrees of Separation inserted multiple
rows in the SEP_CONFLICT_REL table with the same degree for the same conflict.
- UMF_ALERT documents that were published when using IBM Relationship Resolution
Degrees of Separation might have contained an incorrect value for the DEGREE
element.
- Sometimes, the MATCH_ID column in the SEP_CONFLICT_REL table did not properly
update.
- In the Configuration Console, users could only choose the data source
class by description. Now users can choose data source class by ID.
- The Configuration Console did not allow valid values to be entered for
the Confirm Weight of a number.
- Pipelines that accept data from Microsoft MQSeries queues no longer "hang"
on bad UMF messages.
- The ACCT_LOADED field in the DSRC_ACCT table did not properly update when
using the passive load feature.
- DQM Rule 131 incorrectly truncated the entire string instead of the specified
portion.
- The DB2 implementation of the database transport for a pipeline had locking
issues that might affect performance.
- Close matches found by the system were not properly drawn in the Visualizer
graphs.