IBM Relationship Resolution, Version 4.2

EAS FP2 HotFix Rollup #2 Readme

EAS 4.2.0.532 (EAS_FP2_hotfix_rollup#2 - Build #532)

January 2010

Contents:

0. IMPORTANT PREREQUISITES & INSTRUCTIONS

SECTION 1 - HOTFIX ROLLUP#1 (Build #527)

1. Problems/issues addressed in this hotfix

2. Prerequisites and permissions

3. Required SQL scripts

4. Required files

5. Implementation steps

SECTION 2 - HOTFIX ROLLUP#2 (Build #532)

6. Problems/issues addressed in this hotfix

7. Prerequisites and permissions

8. Required SQL scripts

9. Required files

10. Implementation steps

IMPORTANT PREREQUISITES & INSTRUCTIONS

There are two (2) prerequisites for this Hotfix Rollup #2 (Build #532):

If you HAVE already applied 'Hotfix Rollup #1' (Build #527), please go to SECTION 2 of these instructions.

If you HAVE NOT applied 'Hotfix Rollup #1' (Build #527), please continue with SECTION 1 of these instructions below.

SECTION 1 - HOTFIX ROLLUP #1 (Build #527)

1. Problems/issues addressed in this Hotfix Rollup #1:

[ 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 CWUAA0003E". 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, EntityResolver.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 HTTPS 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 dsrc 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.

2. Prerequisites and permissions - Hotfix Rollup #1

4.2.0.2 (4.2.0 Fixpack 2) must be installed.

Permissions:

The following permissions need to be granted to the userid that will be running the 4.2 FP2 hotfix Rollup#1 SQL scripts:

 'execute any procedure'

 'drop sequence'

 'create sequence'

 'alter procedure'

 'create procedure'

 'drop procedure'

 'drop function'

 'create function'

 'drop index'

 'create index'

 'drop view'

 'create view'

 'create type'

 'insert'

 'update'

 'delete'

 'create session'

 'alter session'

 'create synonym'

DB2 users:

The following additional permissions are required (in addition to the list above):

 call sysproc.admin_cmd

 'create table'

 'rename table'

Note: If you have installed RR 4.2 into a specific schema, please issue the following commands before running the SQL-scripts via DB2 CLP: 

db2 set current path <schema name>

db2 set current schema <schema name>

db2 set current sqlid <schema name>

Note: DB2 users - execution of SQL scripts:

When running the following 2x scripts via DB2 CLP, use the following command:

db2 -td@ -f <filename>

Script names:

hotfix_57450.db2.sql

hotfix_59418.db2.sql

When running the following 2x scripts via DB2 Control Center, you need to change the "Statement Termination Character" from ';' to '@'

Script names:

hotfix_57450.db2.sql

hotfix_59418.db2.sql

MSSQL users:

The following additional permissions are required (in addition to the list above):

 'drop table'

 'create table'

 'alter table'

Oracle users:

Grant permissions listed above directly to the userid, and DO NOT assign them via Roles. One of the scripts in this hotfix uses a Function. Oracle *ignores* privileges assigned to a user via Roles when executing functions. Assigning privileges via a role will cause this function to fail to execute successfully.

3. Required SQL scripts - Hotfix Rollup #1:

DB2 v8.2:

change_circaDateAttrScoring_version.sql, hotfix_57450.db2.sql, hotfix_57720.db2.sql, hotfix_59418.db2.sql, hotfix_58845.db2v82, nameAttrScoring.sql    

DB2 v9.1:

change_circaDateAttrScoring_version.sql, hotfix_57450.db2.sql, hotfix_57720.db2.sql,hotfix_59418.db2.sql, hotfix_58845.db2v91.sql, nameAttrScoring.sql

MSSQL:

change_circaDateAttrScoring_version.sql, hotfix_57720.mssql.sql, hotfix_59418.mssql.sql, nameAttrScoring_msq.sql, hotfix_rollup_1_msq.sql

Oracle:

change_circaDateAttrScoring_version.sql, hotfix_rollup_1_ora.sql, hotfix_57720.oracle.sql, hotfix_59418.ora.sql, nameAttrScoring.sql

4. Required Files - Hotfix Rollup #1:

AIX / Solaris / Linux

pipeline

ibm-db2-eas-visualizer.ear

ibm-eas-console.ear

ibm-eas-web-service.ear

NMMGR:

libNameManager.so

Plug ins:

libdateAttrScoring.so

libnameAttrScoring.so

libdefaultAttributeScoring.so

libcircaDateAttrScoring.so

libbinaryAttributeScoring.so

libhttpCalloutScoring.so

HP / SuSe9 on zOS

pipeline

ibm-db2-eas-visualizer.ear

ibm-eas-console.ear

ibm-eas-web-service.ear

NMMGR:

libNameManager.so

Plug ins:

libdateAttrScoring.so

libnameAttrScoring.so

libdefaultAttributeScoring.so

libcircaDateAttrScoring.so

libbinaryAttributeScoring.so

libhttpCalloutScoring.so

Windows

pipeline.exe

ibm-db2-eas-visualizer.ear

ibm-eas-console.ear

ibm-eas-web-service.ear

NMMGR:

nameManager.dll

Plug ins:

dateAttrScoring.dll

defaultAttributeScoring.dll

circaDateAttrScoring.dll

nameAttrScoring.dll

binaryAttributeScoring.dll

httpCalloutScoring.dll

5.  Implementation steps - Hotfix Rollup #1

To apply the hotfix, please do the following:

  1. Copy the required files to your hard drive.

  2. Stop the pipelines.

  3. Back up your pipeline, NameManager and the Plug-in files (listed above).

  4. Replace the pipeline by copying the new version into  <RR_INSTALL>/bin.

  5. Replace the NameManager and the plug-in files by copying the new versions into:
    For Windows:  <RR_INSTALL>/bin
    Other platforms:  <RR_INSTALL>/lib

  6. Run the required SQL scripts against your EAS database.
    Note: Refer to the Database-Specific instructions above before running the scripts.

  7. Launch the Config Utility from the "/InstallDir/installer/util":
    a. Type eacfg to see the help file for the command.
    b. You can launch the tool using "eacfg -i -l ../logs"
    c. Make sure you are on Patches and Hotfixes section, which is the very first screen of the tool:
  8. 1) Confirm that the box next to "Console Application" is checked.
    2) Browse to the "ibm-eas-console.ear" from your hard drive.
    3) Confirm that the box next to "Visualizer Application" is checked.
    4) Browse to the "ibm-db2-eas-visualizer.ear" from your hard drive.
    5) Confirm that the box next to "Web Services Application" is checked.
    6) Browse to the "ibm-eas-web-service.ear" from your hard drive.
    7) Click on Apply.
    8) You can choose to restart WebSphere Application Server after reconfiguration is complete.

  9. If you did not choose to restart Websphere Application Server after reconfiguration on step 7, do the following:
    a. Stop WebSphere Application Server.
    b. Start WebSphere Application Server.

  10. Start the pipelines.

SECTION 2 - HOTFIX ROLLUP #2 (Build #532)

6. Problems/issues addressed in this Hotfix Rollup #2:

[ 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.

[ APAR # PJ37006 ] Performance Issue - Webservices.

[ APAR #PJ36999 ] gnrNameHasher Variant-limiting enhancement. This enhancement provides additional tuning parameters to the gnrNameHasher feature.

[ APAR #PJ36708 ] Event Processing enhancement - Display only the events that participated in the event alert.

[ CQ # ipsdb00063017 ] Unnecessary internal copying of message caused pipeline to crash.

[ CQ # ipsdb00061006 ] Pipeline repeatedly reports a deadlock condition with retries until it shuts down.

[ CQ # ipsdb00063015 ] In Visualizer, the Event Details list displays all the events for the entity. This list is not filtered to display only the events that participated in the event alert.

[ CQ # ipsdb00065221 ] We do not have a way to "audit" the particular user executing the Find by Attribute query from visualizer.

[ CQ # ipsdb00066722 ] Performance enhancments.

[ CQ # ipsdb00066709 ] NameHasher limiting fix.

7. Prerequisites and permissions - Hotfix Rollup #2

There are Two (2) prerequisites for this 'Hotfix Rollup #2' (Build #532):

(A) 4.2.0.2 - (4.2.0 Fixpack 2) must be installed prior to applying this 4.2 FP2 Hotfix Rollup#2.

(B) 4.2.0.527_EAS_FP2_hotfix_rollup#1 ('Hotfix Rollup #1' - Build#527 ) must be installed prior to applying 4.2 FP2 'Hotfix Rollup #2'. (See SECTION 1 above.)

Permissions:

The following permissions need to be granted to the userid that will be running the 4.2 FP2 hotfix#2 SQL scripts:

 'create table'

 'create index'

DB2 users:

Note: If you installed RR 4.2 into a specific schema, please issue the following commands before running the SQL-scripts via DB2 CLP:

db2 set current path <schema name>

db2 set current schema <schema name>

db2 set current sqlid <schema name>


8. Required SQL scripts - Hotfix Rollup #2

DB2

hotfix_63015.sql

MSSQL:

hotfix_63015.mssql.sql

Oracle:

hotfix_63015.ora.sql


9.  Required Files - Hotfix Rollup #2:

Windows

pipeline.exe

ibm-db2-eas-visualizer.ear

ibm-eas-console.ear

ibm-eas-web-service.ear

ibm-eas-gnrnamehasher.ear

NMMGR:

nameManager.dll

Plug ins:

dateAttrScoring.dll

defaultAttributeScoring.dll

circaDateAttrScoring.dll

nameAttrScoring.dll

binaryAttributeScoring.dll

httpCalloutScoring.dll

gnrNameHasher:

namehasher.properties

AIX / Solaris / Linux

pipeline

ibm-db2-eas-visualizer.ear

ibm-eas-console.ear

ibm-eas-web-service.ear

ibm-eas-gnrnamehasher.ear

NMMGR:

libNameManager.so

Plug ins:

libdateAttrScoring.so

libnameAttrScoring.so

libdefaultAttributeScoring.so

libcircaDateAttrScoring.so

libbinaryAttributeScoring.so

libhttpCalloutScoring.so

gnrNameHasher:

namehasher.properties

HP / SuSe9 on zOS

pipeline

ibm-db2-eas-visualizer.ear

ibm-eas-console.ear

ibm-eas-web-service.ear

ibm-eas-gnrnamehasher.ear

NMMGR:

libNameManager.so

Plug ins:

libdateAttrScoring.so

libnameAttrScoring.so

libdefaultAttributeScoring.so

libcircaDateAttrScoring.so

libbinaryAttributeScoring.so

libhttpCalloutScoring.so

gnrNameHasher:

namehasher.properties


10.  Implementation steps - Hotfix Rollup #2

To apply the hotfix, please do the following:

  1. Copy the required files to your hard drive.

  2. Stop the pipelines.

  3. Back up your pipeline, NameManager, and the Plug-in files (listed above).

  4. Replace the pipeline by copying the new version into  <RR_INSTALL>/bin.

  5. Replace the NameManager and the plug-in files by copying the new versions into:

    AIX/Solaris/Linux/HPUX:  <RR_INSTALL>/lib

    Windows platforms:  <RR_INSTALL>/bin


  6. Run the required SQL scripts against your EAS database.

    Note: Refer to the Database-Specific instructions above before running the scripts.

  7. Please launch the Config Utility from the "/InstallDir/installer/util".

    a. Type eacfg to see the help file for the command.

    b. You can launch the tool using "eacfg -i -l ../logs".

    c. Make sure you are on the Patches and Hotfixes section, which is the very first screen of the tool.

    d. Confirm that the box next to "Console Application" is checked.

    e. Browse to the "ibm-eas-console.ear" from your hard drive.

    f. Confirm that the box next to "Visualizer Application" is checked.

    g. Browse to the "ibm-db2-eas-visualizer.ear" from your hard drive.

    h. Confirm that the box next to "GNR NameHasher" is checked.

    i. Browse to the "ibm-eas-gnrnamehasher.ear" from your hard drive.

    j. Confirm that the box next to "Web Services Application" is checked.

    k. Browse to the "ibm-eas-web-service.ear" from your hard drive.

    l. Click on Apply.

    m. You can choose to restart the WebSphere after reconfiguration is complete.

  8. (gnrNameHasher Variant-Limiting change) In your <RR_INSTALL>/srd-home directory, create a new subdirectory named 'namehasher'. (Note: lower-case is important.)


  9. (gnrNameHasher Variant-Limiting change) Copy the supplied 'namehasher.properties' file into this new <RR_INSTALL>/srd-home/namehasher subdirectory.

    Examine the contents of this file, and uncomment/comment-out the appropriate values in this file.

    For Existing 4.2 customers, the default values supplied in this file will work identically to the existing settings.

    Additionally, a set of recommended values, matching those that have been implemented in the latest version of the Relationship Resolution product (IBM InfoSphere Identity Insight v8.0) are also listed, commented out, in this file.

    UPGRADING - NOTE: Customers that apply this 4.2 Hotfix Rollup #2 will have to manually replicate their chosen 'maxVariants' and 'variantScoreThresold' entries **within the URI-string of the DQM660 Rule** when they upgrade to IBM InfoSphere Identity Insight v8.0. Version 8.0 does not utilize this namehasher.properties file. Please refer to the Information Center provided with IBM InfoSphere Identity Insight v8.0 for further information.


  10. (Event Processor Enhancement) If required, make sure the event processing is enabled. Go to EAS-Console:

    a. Click on Setup.

    b. Click on System Parameters.

    c. Click on the drop down next to parameter group.

    d. Pick EVENT Processing.

    e. Make sure "ENABLE_EVENT_PROCESSING" Current Value is set to '1'

    f. Ensure that the "EVENT_PROCESSOR_URI" value is set to:
    http://<hostname>:<WAS port#>/console/gem_processor

  11. To use the new feature in CEP you must modify your rules to push the new data to the pipeline.

    a. You must create an new Situation Attribute inside CEP called: EVENTS of type Integer, which contains the Event_ids used in the rule.

    b. You also need to add the dimension of "[ ]".

    Example:
    The entry that the CEP Authoring Tool (available in <RR_INSTALL>/cep) generates for the <eventType> definition in the cep.xml file should look like this:

    <attributeType dimension="[]" name="EVENTS" xsi:type="integer"/>

  12. Restart the WAS_EE.


  13. Start the pipelines.