Release notes - IBM Relationship Resolution version 4.2 fix pack 2

Contents

• About IBM Relationship Resolution
• New functions in IBM Relationship Resolution version 4.2 fix pack 2
• Installing and configuring IBM Relationship Resolution version 4.2 fix pack 2
• Starting the IBM Relationship Resolution version 4.2 fix pack 2 installation program
• Navigating the installation in command line mode
• Navigating the installer in GUI mode
• Completing the IBM Relationship Resolution version 4.2 fix pack 2 installation
• Running the post-installation database specific SQL scripts for FP2
• IBM Relationship Resolution version 4.2 fix pack 2 maintenance items
• System requirements
• Announcements
• Known problems and issues
• Notices

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:

Installing and configuring IBM Relationship Resolution version 4.2 fix pack 2

1. Start the IBM Relationship Resolution version 4.2 fix pack 2 installation program.
2. Complete the IBM Relationship Resolution version 4.2 fix pack 2 installation.
3. Run the post-installation database specific SQL scripts.

Starting the IBM Relationship Resolution version 4.2 fix pack 2 installation program

Before you begin:

Manually stop all running pipelines on the IBM Relationship Resolution installation that you are upgrading.

If you are installing the program on Microsoft Windows, you must copy the product installer executable to a local drive. The product installer will not run from either the CD/DVD or from a network drive.

1. Obtain the IBM Relationship Resolution version 4.2 fix pack 2 download package.
2. Uncompress the download package to a temporary directory.
3. Browse to the temporary directory.
4. Do one of the following steps:
   • To start the installer in GUI mode from a GUI, double-click the appropriate executable for your operating system.
   • To start the installer in GUI mode from a command line, run the appropriate executable for your operating system.
   • To start the installer in command line mode, run the appropriate executable for your operating system with the -console option.

Navigating the installation in command line mode

• To navigate to the next install panel, type 1 and press the Enter key.
• To navigate to the previous install panel, type 2 and press the Enter key.
• To redisplay the current install panel, type 4 and press the Enter key.
• To cancel the current installation process and exit the installer, type 3 and press the Enter key.

Navigating the installer in GUI mode

• To navigate to the next install panel, click the Next button
• To navigate to the previous install panel, click the Back button
• To cancel the current installation process and exit the installer, click the Cancel button

Completing the IBM Relationship Resolution version 4.2 fix pack 2 installation

1. On the Welcome panel, review the screen.
2. On the Install Directory panel, type or browse to the directory (fully qualified path) in which to install the IBM Relationship Resolution version 4.2 fix pack 2. This directory must be the directory which contains your existing IBM Relationship Resolution version 4.2 installation. If browsing to an installation directory, you must click the Browse button, then browse to the directory one level above the install directory (create the new directory if needed). Then select the install directory and click the Open button.
   Note:
   On Microsoft Windows, the install path length must not exceed 45 characters due to WebSphere restrictions.
3. On the Product features panel, review the product features that will be installed.
4. On the Summary Information panel, review the summary (click back if any changes are needed), and then click the Next button to complete the installation.
5. On the Installation Complete Summary Information panel, review the summary, and then click the Finish button to exit the installation. When installing on Solaris systems, you might see the No such file or directory message on the final window. You can safely ignore this warning message.

Running the post-installation database specific SQL scripts for FP2

The following scripts update the schema of your IBM Relationship Resolution installation database.

1. Determine the installed components (PRODUCT) and their level (VERSION) by running the following SQL command: SELECT * from SRD_PRODUCT_VERSIONS;

   If the result for VERSION is:	Then do the following:
   < 4.2.0	Do not continue. The current installation is for a version of IBM Relationship Resolution that is earlier than version 4.2. Make sure that version 4.2 is installed correctly and then install the fix pack.
   = 4.2.0	Continue to step 2.
   = 4.2.1	Continue to step 2.
   = 4.2.2	Stop. IBM Relationship Resolution version 4.2 fix pack 2 is installed and the SQL scripts for the fix pack were run correctly.

2. Browse to the IBM Relationship Resolution installation directory and subdirectory containing post installation SQL scripts.
   1. Browse to the /sql subdirectory.
   2. Browse to the subdirectory for your specific database installation.
3. Run one of the post installation SQL scripts for each PRODUCT installed on your system that was displayed by the SQL command above:

   PRODUCT listed by the above SQL command	SQL script
   RELRES	RELRES_4.2.0_4.2.2.sql (for 4.2.0) RELRES_4.2.1_4.2.2.sql (for 4.2.1)
   RELRES.NO_HIST	RELRES.NO_HIST_4.2.0_4.2.2.sql (for 4.2.0) RELRES.NO_HIST_4.2.1_4.2.2.sql (for 4.2.1)
   CMEAdmin	CMEAdmin_4.2.0_4.2.2.sql (for 4.2.0) CMEAdmin_4.2.1_4.2.2.sql (for 4.2.1)
   EAS-Console	EAS-Console_4.2.0_4.2.2.sql (for 4.2.0) EAS-Console_4.2.1_4.2.2.sql (for 4.2.1)

4. Validate that fix pack 2 has been installed correctly by running the SQL command again: SELECT * from SRD_PRODUCT_VERSIONS;. You should see 4.2.2 under the VERSION heading for each of the installed PRODUCTS.

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

• The Degrees of Separation function no longer inserts multiple rows in the SEP_CONFLICT_REL table with the same degree for the same conflict. [Bug 6289]
• The Degrees of Separation function now publishes UMF ALERT documents which contain consistently correct values for the DEGREE elements. [Bug 6406]
• The Degrees of Separation function now correctly updates the MATCH ID column in the SEP_CONFLICT_REL table every time. [Bug 6413]

Console

• In the Console screen, users can now choose the data source class by its description, as well as its ID. [Bug 6291]
• The Console screen now permits users to enter valid values for the Confirm Weight of a number. [Bug 6432]
• Console pages no longer error out with replication columns. [bug 7395]

Pipelines

• Pipelines that accept data from MQSeries queues no longer hang on XML error messages. [Bug 6305]
• The DB2 implementation of the database transport for a pipeline no longer locks up, which has improved performance. [Bug 6410]
• The http pipeline no longer experiences a 100ms delay. [bug 7382]
• The pipeline now scores generic values in the confirmation screen. [Bug 6714]

The Passive Load feature

• The Passive Load feature now correctly updates the ACCT_LOADED field in the DSRC_ACCT table. [Bug 6313]
• The Passive Load feature now loads only if NUM_LOCATION matches. [bug 8100]
• The Passive Load feature no longer returns XML without an ENTITY ID, eliminating a possible Visualizer error.

Visualizer

• The Visualizer now draws close matches correctly in graphs. [Bug 6368]
• Visualizer graphs and the Entity Resume function no longer affect DB2 performance.

Search features

• The Search Results screen now displays correct matching details in every case.
• The First Name field is no longer required on the Add Entity and New Search screens.
• The count of relationships in the Search Results screen now displays correctly.
• The Likeness Score field was added to the Search Result screens.
• Persistent searches are displayed in the Inbox, based on the case number and the status.
• 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.

The SEP_RELATIONS table

• The SEP_RELATIONS and SEP_CONFLICT_REL tables now use up-to-date entity resolution IDs.
• The SEP_RELATIONS table is now updated every time, even during an incomplete resolution recovery.
• Selective Passive Data Source writing record to SEP_RELATIONS table.
• The Passive Writing function now records entries in the SEP_RELATIONS table only if supporting entity data exists for at least one side of the alert. [bug 7919]

Name Manager functions

• The ER_DETAIL table no longer logs name matches, when name matches are not required.
• Name confirmation no longer occurs, when Name Manager is disabled or not required (a 0 value is in the rule).
• Functions dealing with names of related entities are now showing improved performance.

Data display

• The DQM Rule 131 now truncates only the specified portion of a string. [Bug 6298]
• The Conflict screen now displays correct matching details in every case.
• The Entity Resume screen now highlights the correct set of related data items, when users select relationships.
• The count of relationships for conflicts in the Conflict List screen now displays correctly.
• New views have been added to ensure that the number of alerts in the inbox summary table matches the number of open (unassigned) conflicts.

Miscellaneous

• In the Italian language file, the translation for 'State' was changed to "Provincia".
• The Anonymizer now outputs correctly to MQSeries. [bug 7849]
• The ADDR_ID and EMAIL_ADDR_ID fields/columns no longer permit overflow. [bug 8023]
• The system no longer permits users to choose Deleted Accts or Roles. [bug 8081]

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.

Notices

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

(C) International Business Machines Corporation (2009). Portions of this code are derived from IBM Corp. Sample Programs. (C) Copyright IBM Corp. 2009. All rights reserved.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Trademarks

IBM, the IBM logo, ibm.com, AIX, DB2, DB2 Universal Database, POWER4, POWER5, WebSphere, and z/OS are registered trademarks of International Business Machines Corporation in the United States, other countries, or both.

Adobe and Portable Document Format (PDF) are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.

Intel, Intel Centrino, Celeron, Intel Xeon, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.