By default, the data source cache layer is enabled. It supports both public and private feed caching:
- Public feed caching: A public feed does not depend on the user who requested the feed.
- Private feed caching: A private feed depends on the user who requested the feed.
Data source cache expiration
By default, the expiration time of a DataSource
cache entry is determined by the expiration date that is specified by IBM
Connections in the HTTP response headers for a feed. This expiration time is based on either of the following settings:
- The max-age directive in the cache-control header field
- The Expires header field.
Connections specifies no expiration date, social rendering uses the value of the connections.feeds.datasource.cache.lifetime
custom property. This property is defined in the WP Connections Integration Service resource environment provider in the WebSphere
® Integrated Solutions Console. Its value specifies the cache entry expiration time in seconds. It is valid for all cache entries. The default value is 900
seconds; this value is equivalent to 15 minutes. For information about how to modify this setting, see the topic about Setting service configuration properties
in the WebSphere
Portal product documentation.
Social rendering uses this cache expiration setting as a fallback if IBM
Connections does not provide an expiration date. You can also configure this setting to take priority over the settings that are specified in IBM
Connections. To do this, set the connections.feeds.datasource.cache.lifetime.overrules
custom property in the WP Connections Integration Service resource environment provider to true
Parent topic: Performance tuning for social lists
Setting service configuration properties