PI09171: A SET OF ATTRIBUTES NEEDS TO BE PRE FETCHED FOR AN ENTITY TYPE TO PREVENT SOME ADDITIONAL JNDI CALLS.

8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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.14: WebSphere Application Server V8.5.5 Fix Pack 14
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 new function.

Error description

• Right now federated repository does not cache attributes for an
  entity type unless and until it has been asked for. When these
  attributes are queried a JNDI query needs to be fired to
  retrieve that information. To save the additional JNDI calls
  we will pre-fetch a set of attributes for an entity type when
  the first call is made for a particular entity type.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: To save query response time a default   *
  *                      set of attributes needs to be cached    *
  *                      whenever the first call for a           *
  *                      particular user or group is made        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Currently federated repository does not cache any default set
  of attributes for any user or group unless and until those
  attributes have been queried explicitly. So, if in the first
  query only the user or group is being queried, federated
  repository returns the user or group distinguised name only and
  does not cache any attributes of that user or group. Now, if
  in a subsequent query some attributes have been queried for
  the user or group that is queried in first call, federated
  repository will fire a JNDI query to the back end LDAP to
  retrieve that information. So, in such a scenario where the
  number of users and groups is large, that many JNDI calls will
  be fired by the federated repository which will take some time
  to return the requested information.
  

Problem conclusion

• Federated repository will now provide a custom property
  named preFetchData. This needs to be configured to define
  the default set of attributes that need to be retrieved and
  cached by the federated repository for a particular entity
  type whenever a query is made for a particular user or group
  for the first time.
  
  Valid values for this custom property are a string containing
  pairs of entity type name and its corresponding set of
  attributes. The value has to be defined in a particular format.
  That is,  the value should contain the pairs of entity type
  name and its corresponding set of attributes. For example:
  EntityType1:attribute1,attribute2;EntityType2:attribute1,attribu
  te2
  
  Each such pair should be separated by a semi colon (;).
  Attributes names should be separated by a comma (,). Lists of
  attributes that are specified after the entity type name
  should be preceded by a colon (:).
  
  This custom property should be configured for a particular
  LDAP repository. To set the custom property, the
  setIdMgrCustomProepty CLI should be used as follows:
  
  Syntax: $AdminTask setIdMgrCustomProperty {-id
  <ldap_repository_name> -name <property_name> -value <value>}
  
  Example:
  $AdminTask setIdMgrCustomProperty {-id LDAP -name preFetchData
  -value  PersonAccount:sn,cn;Group:cn,description}
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.2.  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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP