PI79781: FEDERATED REPOSITORIES FAILS TO SEARCH REPOSITORY WHEN OVERLAPPING BASE DN'S EXIST.

8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• When Federated Repositories is configured with 2 different
  repositories whose base entries overlap, entities from one of
  the repositories may not be returned. An example of
  overlapping base entries is below.
  
      ou=users,dc=ibm,dc=com
               dc=ibm,dc=com
  

Local fix

• make sure each base entry is unique
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server users of   *
  *                  federated repositories                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: When two or more repositories have      *
  *                      overlapping base entries, federated     *
  *                      repositories may ignore some of the     *
  *                      repositories.                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  On initialization Federated Repositories checks participating
  base entries of the repositories agains the defined
  repositories. When doing so, it was doing a greedy search
  where the first repository whose base entry ended with the
  particpating base entry would claim that participating base
  entry. This resulted in one repository claiming the
  participating base entries that were intended to include other
  repositories.
  

Problem conclusion

• The logic for claiming repositories for each participating
  base entry was updated to find a 'best' repository match
  instead of using the first repository that only
  partcially matches.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.0.0.14, 8.5.5.12 and 9.0.0.5.  Please refer to the
  Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY

     UP

• R850 PSY

     UP

• R900 PSY

     UP