The table below provides a quick reference, primarily for user data cache settings.
Notice that many properties for configuration data cache have
sm (for Service Management) in their names, whereas those
for user data have idm (for Identity Management) in their
names.
Table 18.8. OpenAM Cache Properties
| Property | Description | Default | Applies To |
|---|---|---|---|
|
|
Maximum number of user entries cached |
10000 |
Server & SDK |
|
|
Whether to enable caching for both configuration data and also for user data. If If |
|
Server & SDK |
|
|
How often in minutes the SDK client such as a policy agent should poll OpenAM for modified user data entries. The SDK also uses this value to determine the age of the oldest changes requested. The oldest changes requested are 2 minutes older than this setting. In other words, by default the SDK polls for entries changed in the last 3 minutes. Set this to 0 or a negative integer to disable polling. |
1 (minute) |
SDK |
|
|
How long OpenAM stores a given change to a cached entry, so that clients polling for changes do not miss the change. |
30 (minutes) |
Server only |
|
|
If Otherwise, set this to |
|
Server & SDK |
|
|
How many minutes to store a user data entry in the global user data cache |
30 (minutes) |
Server & SDK |
|
|
Whether user data entries in the global user data cache should expire over time |
|
Server & SDK |
|
|
Whether the SDK client such as a policy agent should register a notification listener for user data changes with the OpenAM server. The SDK client uses the URL specified by
If notifications cannot be enabled for some reason, then the SDK client falls back to polling for changes. |
|
SDK |
|
|
If Otherwise, set this to |
|
Server & SDK |

