Name: PK29259
=============
 
Summary:
   Enable resource type specific Entitlements Caches in PAC
 
Problem Description:
   
      The resource type specific entitlements caches in PAC (like e.g. the cacheinstance.com.ibm.wps.ac.ExplicitEntitlementsCache.CONTENT_NODE for pages) are not created at runtime even when they are enabled in the properties of the Cache Manager Service. This causes PAC to cache the entitlements for all users and all resource types in the default entitlements cache (cacheinstance.com.ibm.wps.ac.ExplicitEntitlementsCache). Depending on the scenario, this may have a considerable performance hit. PK29259 fixes this issue and additionally changes the separator character for using more than one resource type in a cache from "*" to "!" (so e.g. cacheinstance.com.ibm.wps.ac.ExplicitEntitlementsCache.PORTLET_APPLICATION_DEFINITION*PORTLET_DEFINITION changes to cacheinstance.com.ibm.wps.ac.ExplicitEntitlementsCache.PORTLET_APPLICATION_DEFINITION!PORTLET_DEFINITION). This way it is possible to define these properties in the Resource Environment provider named "WP CacheManagerService" in the WebSphere Application Server.
 
Problem Solution:
   Extended the CacheManagerService to provide a read-only copy of its properties. This is then read by the PAC cache initialization logic (which formerly tried to read the config file directly from /shared/app/config/services). Also changed the separation logic from using a "*" to using a "!".
 
Failing Module(s):
   Portal Access Control
 
Affected Users:
   AllUsers
 
Version Information:
    Portal Version(s): 6.0.0.0
     Pre-Requisite(s): 
      Co-Requisite(s): ---
 
Platform Specific:
   This fix applies to all platforms.
 
Installation:
   NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
          The Portal Update Installer can be downloaded from the following link:
          http://www.ibm.com/software/genservers/portal/support
 
   1. Create temporary "fix" directory to store the jar file.
   2. Copy jar file to this directory.
   3. Shutdown WebSphere Portal.
   4. Follow the fix installation instructions that are packaged with
      the Portal Update Installer on how to install the fix.
   5. Restart WebSphere Portal.
   6. The temporary directory may be removed.
 
Un-Installation:
   NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE
          A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.
          YOU MAY REAPPLY ANY REMOVED FIX.
 
   1. Shutdown WebSphere Portal.
   2. Follow the instructions that are packaged with the
      Portal Update Installer on how to uninstall the fix.
   3. Restart WebSphere Portal.