PI53143: DOC: CONFIGURING PORTLET ENTITY CACHES FOR MULTIPLE LINES OF PRODUCTION

APAR status

• Closed as documentation error.

Error description

• AFFECTED URLs:
  
  V8.5:
  https://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5
  .0/mp/plan/db_domains_shared.dita
  
  V8:
  http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.0
  .0/config/db_plan_domains.dita?lang=en
  
  V7:
  http://www-10.lotus.com/ldd/portalwiki.nsf/xpDocViewer
  .xsp?lookupName=IBM+WebSphere+Portal+7+Product+Documentation#act
  ion=openDocument&res_title=Shared_database_domains_wp7&content=p
  dcontent
  
  Configuring portlet entity caches for multiple lines of
  production:
  
  If you plan to use multiple lines of production, you may need to
  configure Portal cache settings. That is the case if Portal
  users will customize portlets to change their personal portlet
  preferences:
  Since Portal caches portlet entities, portal preference changes
  created on a first line of production may not become visible on
  the second line of production as long as the cache is not
  refreshed.
  You can configure the lifetime of the corresponding Portal
  caches "com.ibm.wps.pe.portletentity" and
  "com.ibm.wps.pe.portletentitycounter".
  Both caches are accessed many times during Portal request
  processing. It is important that the most relevant portlet
  entities are cached. Disabling these caches will degrade Portal
  performance.
  You should therefore choose a cache lifetime which balances your
  need for data coherence between lines of production and your
  need for Portal performance.
  To define the cache lifetime, configure the following properties
  in the CacheManagerService (http://www-01.ibm
  .com/support/knowledgecenter/SSHRKX_8.0
  .0/admin/srvcfgref_cach_mgr.dita) :
  cacheinstance.com.ibm.wps.pe.portletentity.lifetime=300
  cacheinstance.com.ibm.wps.pe.portletentitycounter.lifetime=300
  This defines a cache lifetime of 300 seconds. You may choose
  another lifetime if required. The cache lifetime should be at
  least 5, to allow portlet entities to be cached for one request.
  The WebSphere Portal and Web Content Manager Performance Tuning
  Guide provides more information about caches.
  

Local fix

• Refer to the above.
  

Problem summary

• This is planned to be changed in the product documentation.
  

Problem conclusion

• This is planned to be changed in the product documentation.
  

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

Applicable component levels