Technical data

Specifying a Security Realm
Administration Guide 14-7
Note: Also make a backup copy of the SerializedSystemIni.dat file for the File
realm. For more information about the
SerializedSystemIni.dat file, see
Protecting Passwords.
If, instead of the File realm, you want to use one of the alternate security realms
provided by WebLogic Server or a custom security realm, set the attributes for the
desired realm and reboot WebLogic Server.
Caution: If you use one of the alternate security realms, you must configure and
enable the Caching realm; otherwise the alternate security realm will not
work.
For more information about security realms in WebLogic Server, see Security Realms.
Configuring the Caching Realm
The Caching realm works with the File realm, alternate security realms, or custom
security realms to fulfill client requests with the proper authentication and
authorization. The Caching realm stores the results of both successful and unsuccessful
realm lookups. It manages separate caches for Users, Groups, permissions, ACLs, and
authentication requests. The Caching realm improves the performance of WebLogic
Server by caching lookups, thereby reducing the number of calls into other security
realms. For more information about security realms in WebLogic Server, see Security
Realms.
The Caching realm is installed automatically when you install WebLogic Server: the
cache is set up to delegate to the other security realms however caching is not enabled.
You have to enable caching through the Administration Console.
Caution: If you use one of the alternate security realms, you must configure and
enable the Caching realm; otherwise the alternate security realm will not
work.
When you enable caching, the Caching realm saves the results of a realm lookup in its
cache. Lookup results remain in the cache until either the specified number of seconds
defined for the time-to-live (TTL) attributes has passed (the lookup result has expired)
or the cache has filled. When the cache is full, new lookup results replace the oldest
cached results. The TTL attributes determine how long a cached object is valid. The
higher you set these attributes, the less often the Caching realm calls the secondary