Sun OpenSSO Enterprise 8.0 Developer's Guide

Cache Update Properties

When caching is enabled, OpenSSO Enterprise has three options that can be used to invalidate dirty cache entries. The first is to set up a URL with which the OpenSSO Enterprise server can send session change notifications to clients on remote web containers. This works for web and standalone applications that can listen for HTTP(s) traffic. The second method (which works ONLY if notification is disabled) is polling. In this case, the client periodically checks the OpenSSO Enterprise server for session changes. The third method is referred to as Time-to-Live (TTL) and enforces a limit on the period of time dirty data remains in the cache before it is discarded. See the following sections for more information.

Caution – Caution –

The notification method could cause a constant flood of notification changes that might overwhelm the client so be sure to choose the optimal method for your deployment.

Additional cache properties are in Policy Logging and Caching Properties.

Notification Properties

See Sending Notifications to the Client SDK Cache for more information on the Notification Service.

Polling Properties

Notification must be disabled.

TTL Properties

The following properties relate to the cache Time To Live (TTL). TTL is a limit on the period of time before data in the cache should be discarded. These TTL properties are not included in by default but can be added as needed. These are the Service Management TTL properties.

These are the Identity Repository TTL properties.

For backwards compatibility, these are the properties to configure the TTL feature for the classes.