PI27550: ADDITION OF DEVICECLASS KEY IN WCM ADVANCED CACHE

APAR status

• Closed as new function.

Error description

• Advanced caching based on device type was not possible
  

Local fix

• A workaround is to configure WCM to include the User-Agent
  header in the cache-key (see
  setting below) however this will result a very unique cache key
  and hence the Device-Class
  option is far superior
  
  connect.moduleconfig.ajpe.contentcache.additionalcachekeys
  .requestheaders=User-Agent
  

Problem summary

• Advanced caching based on device type was not possible
  

Problem conclusion

• SOLUTION: Addition of "DeviceClass" key to the WCM Advanced
  Cache
  
  CONFIGURATION:
  Additional cache-keys can be configured for the WCM Advanced
  Cache in the WCM ConfigService by setting the
  "connect.moduleconfig.ajpe.contentcache.additionalcachekeys
  .requestattributes" property.
  
  If this property already exists, "deviceclass" can be added to
  the existing value with comma-separation. For example,
    Name: connect.moduleconfig.ajpe.contentcache
  .additionalcachekeys.requestattributes
    Value: [existing-keys],deviceclass
  
  If this property does not already exist, caching for device
  classes can be enabled by adding the property with the value
  "deviceclass". For example,
    Name: connect.moduleconfig.ajpe.contentcache
  .additionalcachekeys.requestattributes
    Value: deviceclass
  
  To add/modify this property in the WebSphere Integrated
  Solutions Console go to Resources -> Resource Environment ->
  Resource Environment Providers -> WCM WCMConfigService -> Custom
  Properties
  

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

  LOTUS WEB CONT

• Fixed component ID

  5724I2900

Applicable component levels

• R850 PSY

     UP