IM InfoSphere Identity Insight, Version 8.0

IBM InfoSphere Identity Insight Version 8 - release information

For information about known issues with IBM® InfoSphere Identity Insight Version 8, and for recent corrections and updates to released versions and documentation, see the IBM InfoSphere Identity Insight Version 8 - Release Notes.

The Release Notes as of the product release date are available as an HTML file on the product installation DVDs. The latest version is available from the IBM InfoSphere Identity Insight Support Web page: http://www-01.ibm.com/software/data/db2/eas/relationship/support.html.

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 who") 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.

This product was formerly titled IBM Relationship Resolution.

Corrections and additions for installation and upgrade

Pipeline installation and configuration selections
The following values are recommended during installation and configuration to minimize problems and enable support and troubleshooting.
  • Log all UMF exceptions (Y/N): Y
  • Stop the pipeline on UMF exceptions (Y/N): N
Before starting the upgrade
Before starting the upgrade, make sure that you check your database and ensure that you have create sequence permissions. If not, use administrator authority to grant a command similar to the following:
"grant create sequence to <username>" 
For Oracle databases this must be assigned directly to the userid (not via a role).
Name Manager - upgrading from IBM Relationship Resolution 4.n
If you enabled Name Manager in IBM Relationship Resolution version 4.n you must remove the old [Name_Manager] section from your pipeline.ini files.

If you are upgrading from IBM Relationship Resolution version 4.n, but did not have Name Manager installed, you must disable the SYSTEM_PARAM 'NAMEMANAGER'. 'ENABLED' setting in the Database (set CURRENT_VALUE=0). Alternatively, you can validate that the Name Manager scoring thresholds in your match merge rules are appropriate. A basic approach is to use .9 as a tight match, .8 as a close match, and .7 as a weak match. The information center has more detailed information.

IBM DB2 - post upgrade task if using DB2 for your database
If you use IBM DB2, you must manually reorg a table after the upgrade is completed. From a DB2 command line, issue the following command:
db2 reorg table <your schema name>.UMF_SUM_DOCUMENT 
Visualizer download and launch
Be aware that the amount of time to download the Visualizer client via the Java Webstart launch link may take several minutes on a LAN connection and longer on a WAN. The file size has increased and it may take twice as much or more time as it did with version 4.2.

The Visualizer requires Sun JRE 6 with update 10, 14, or 15. Do not use update 16 as it will not work. Additionally, there is a known issue with the Sun JRE, in which the Visualizer will not launch on the first attempt. You may see a "Cannot launch" error. In this situation, please retry the Visualizer launch link, and the application should launch successfully from then onwards.

Changes to the schema table LAS_COMP_PARMS_CONFIG
This table is being changed with version 8.0. Any values you had set with the previous version of the product will be reset. You should check the new the table and adjust the values to align with your previous settings. For example:
  • Set NoNameScore, NameUnknownScore to .40 if the previous setting was greater than .40
  • Set InitialOnTokenScore to .60 if the previous setting was greater than .60.

Other corrections and additions

Hardware and software requirements
The topic "System requirements when running on Microsoft Windows Server x86_64" the supported message queuing software is IBM WebSphere® 64-bit MQ 7.0 Client.
UMF Builder Keywords DATE and DATETIME problem
In UMF_OUTPUT_RULE the keywords DATE and DATETIME can be placed in the SOURCE field to insert the current date, or current date/time respectively, when the SOURCE_TYPE is 0 (zero). In previous releases, the keywords were transposed. For example, when DATE was used, date and time were included. This has been corrected so that DATE inserts the current date and DATETIME inserts the current date and time.
Others
  • Group1 Client-Server (G1CS) support, plus the associated Geocoding function, has been deprecated in this release.
  • Automatic-Addition of unknown Attribute-Types have been disabled by default for New Installs. (DQM Rule #190 'Correctable' flag for ATTR_TYPE has been set to 'No'). Customers must define all required ATTR_TYPE values in the Console prior to loading data. Any undefined ATTR_TYPES will not be loaded by default.

Problems and issues included from previous hot fixes:

The following APARs and other issues have been corrected since version 4.2 fix pack 2 and are included in version 8.0:
  • [ APAR # PJ35546 ] Pipeline exits with database deadlock error. This was due to related error handling from the DB.
  • [ APAR # PJ35934 ] Circa-DOB fixes.
  • [ APAR # PJ35908 ] getRoleAlerts / Latin1 character pipeline issue.
  • [ APAR # PJ36073 ] "Error using summary by user id on the SEP conflict table CWU AA0003E". Error occurred when trying to do a 'show all alerts'.
  • [ APAR # PJ36269 ] New entity incorrectly shows no alerts history.
  • [ APAR # PJ35794 ] XML '&' SOAP - Returned booleans are incorrect Case, EntityRe solver.wsdl - include installed hostname.
  • [ APAR # PJ36504 ] Visualizer crashes due to referential integrity caused by force-deleting an acct or attribute used in an alert.
  • [ APAR # PJ36476 ] CEP does not return situations on deferred alerts.
  • [ CQ # ipsdb00059418 ] DQM Sequence# fix - Default assigned sequence #s overwrite customer space.
  • [ CQ # ipsdb00057450 / 56984 ] CEP-Datestamp (Month vs Minute).
  • [ CQ # ipsdb00057720 ] SOA: getRoleAlertsByEntity call returning incorrect values.
  • [ CQ # ipsdb00058844 ] Visualizer links in attributes show error in opening HTTP S link.
  • [ CQ # ipsdb00059779 ] Entity ID can not be copied/pasted from either the entity resume or entity graph.
  • [ CQ # ipsdb00055492 ] Source Create Date Change - added date flexibility for DS RC date display.
  • [ CQ # ipsdb00060508 ] Circa DOB thresholding should be inclusive of both ends.
  • [ CQ # ipsdb00060229 ] Enhancement - Customize Name Attribute Scoring Plug-in implementation.
  • [ CQ # ipsdb00056991 ] G1UNC data-repeat returns incorrect address.
  • [ APAR # PJ36710 ] Pipeline Core dump due to large UMF_OUTPUT_MESSAGE.
  • [ APAR # PJ36713 ] Pipeline will repeatedly report a deadlock condition with retries until it shuts down even though there database records no such issue.

To see the latest information about 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 have been deprecated from this version of IBM InfoSphere Identity Insight. 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).

System requirements updates

For the latest 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.

Announcements

You can search for the IBM InfoSphere Identity Insight version 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


Feedback

Last updated: 2011