IBM Support

PM17681: NEW CLUSTER INVALIDATION STRATEGY FOR PORTAL ACCESS CONTROL (PAC) RELATED CACHES

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • This APAR introduces a new cluster invalidation strategy for
    portal access control (PAC) related caches. With this new
    strategy, cluster scalability of data invalidation events is
    increased while stale data situations under high load are
    better handled.
    To enable the new strategy, please use WAS admin console ->
    Resources -> Resource Environment Providers -> WP
    AccessControlDataManagementService -> custom properties
    to add/modify the following new setting:
    
    setting: accessControlDataManagement
    .enableCacheEventPropagation
    values:  true|false (default = false)
    
    Please save, synchronize, and restart all nodes after any
    changes.
    
    These settings control the cluster invalidation strategy of
    portal access control related caches. The setting
    enableCacheEventPropagation=true enables an event-based
    strategy, that uses a single cache
    (cacheinstance.com.ibm.wps.ac.DataEventPropagationCache) to
    notify all cluster members on changed data. Other PAC caches
    are invalidated locally through event processing to maintain
    cache data consistency.
    The default setting enableCacheEventPropagation=false maintains
    traditional PAC cache invalidation strategy where PAC data
    changes are processed and data is directly invalidated in PAC
    caches. Invalidation events are send between WAS dynacache
    instances in the cluster to maintain data consistency.
    
    Note:
    - the new functionality requires WAS APAR PM18266 (for WAS 7.x)
    or WAS APAR PM18269 (for WAS 6.1.x) to be installed. Otherwise,
    cluster nodes will not receive data changes.
    - cacheinstance.com.ibm.wps.ac.DataEventPropagationCache - this
    new cache instance will show a usage pattern in WAS statistics
    with low hitrate. This cache MUST NOT be disabled or
    reconfigured.
    

Local fix

  • NA
    

Problem summary

  • This APAR introduces a new cluster invalidation strategy for
    portal access control (PAC) related caches. With this new
    strategy, cluster scalability of data invalidation events is
    increased while stale data situations under high load are better
    handled.
    

Problem conclusion

  • To enable the new strategy, please use the WAS admin console to
    add the following custom property to the resource environment
    provider "WP AccessControlDataManagementService":
    
          accessControlDataManagement.enableCacheEventPropagation =
    [true|false] (default = false)
    
    This setting controls the cluster invalidation strategy of
    portal access control related caches. The value "true" enables
    an event-based strategy, that uses a single cache
    (cacheinstance.com.ibm.wps.ac.DataEventPropagationCache) to
    notify all cluster members on changed data. Other PAC caches are
    invalidated locally through event processing to maintain cache
    data consistency.
    The default setting "false" maintains traditional PAC cache
    invalidation strategy wheree PAC data changes are processed and
    data is directly invalidated in PAC caches. Invalidation events
    are send between WAS dynacache instances in the cluster to
    maintain data consistency.
    
    Note:
    - The new functionality requires WAS APAR PM18266 (for WAS 7.x)
    or WAS APAR PM18269 (for WAS 6.1.x) to be installed. Otherwise,
    cluster nodes will not receive data changes.
    - cacheinstance.com.ibm.wps.ac.DataEventPropagationCache - this
    new cache instance will show a usage pattern in WAS statistics
    with low hitrate. This cache MUST NOT be disabled or
    reconfigured.
    
    Failing Module(s):
       Portal Access Control
    
    Affected Users:
       All users
    
    Version Information:
       Portal Version(s): 6.1.0.3, 6.1.0.4
        Pre-Requisite(s): ---
         Co-Requisite(s): ---
    
    Manuel Steps:
       To enable the APAR functionality use the new setting
    'enableCacheEventPropagation' as described.
    
    Platform Specific:
       This fix applies to all platforms.
    
    PM17681 is part of Cumulative Fix 07 for Portal 6.1.0.3 /
    6.1.5.0:
    http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde
    r?apar=PM18585&productid=WebSphere%20Portal&brandid=5
    
    and also part of Cumulative Fix 07 for Portal 6.1.0.4 / 6.1.5.1:
    http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde
    r?apar=PM18610&productid=WebSphere%20Portal&brandid=5
    
    You may need to type or paste the complete address into your Web
    browser.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM17681

  • Reported component name

    WEBSPHERE PORTA

  • Reported component ID

    5724E7699

  • Reported release

    615

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-07-01

  • Closed date

    2010-08-30

  • Last modified date

    2012-05-03

  • 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 PORTA

  • Fixed component ID

    5724E7699

Applicable component levels

  • R615 PSY

       UP

  • R61C PSY

       UP



Document information

More support for: WebSphere Portal
General

Software version: 6.1.5

Reference #: PM17681

Modified date: 03 May 2012