67 lines
4.2 KiB
HTML
67 lines
4.2 KiB
HTML
|
<?xml version="1.0" encoding="utf-8"?>
|
||
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
||
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="dc.language" scheme="rfc1766" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<meta name="dc.date" scheme="iso8601" content="2005-09-06" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow"/>
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<title>Directory Server (LDAP) - Attribute cache</title>
|
||
|
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
||
|
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
|
||
|
|
<img src="delta.gif" alt="Start of change" /><img src="delta.gif" alt="Start of change" />
|
||
|
|
<a name="rzahyattcache"></a>
|
||
|
|
<h3 id="rzahyattcache">Attribute cache</h3>
|
||
|
|
<p>The attribute cache has the advantage of being able to resolve filters
|
||
|
|
in memory rather than in the database. It also has the advantage of being
|
||
|
|
updated each time an LDAP add, delete, modify, or modrdn operation is performed.</p>
|
||
|
|
<p>In deciding which attributes you want to store in memory, you need to consider:</p>
|
||
|
|
<ul>
|
||
|
|
<li>The amount of memory available to the server</li>
|
||
|
|
<li>The size of the directory</li>
|
||
|
|
<li>The types of search filters the application typically uses
|
||
|
|
<a name="wq78"></a>
|
||
|
|
<div class="notetitle" id="wq78">Note:</div>
|
||
|
|
<div class="notebody">The attribute cache manager can resolve the following types of simple filters:
|
||
|
|
exact match filters and presence filters. It can resolve complex filters that
|
||
|
|
are conjunctive or disjunctive, and the subfilters must be exact match, presence,
|
||
|
|
conjunctive, or disjunctive.</div></li></ul>
|
||
|
|
<p>Not all attributes can be added to the attribute cache. To determine whether
|
||
|
|
or not an attribute can be added to the cache, use the ldapexop command:</p>
|
||
|
|
<ul>
|
||
|
|
<li>For attributes that can be added: <tt class="xph">ldapexop -op getattributes -attrType
|
||
|
|
attribute_cache -matches true</tt></li>
|
||
|
|
<li>For attributes that cannot be added: <tt class="xph">ldapexop -op getattributes -attrType
|
||
|
|
attribute_cache -matches false</tt></li></ul>
|
||
|
|
<p>Attribute caching can be configured two ways: manually or automatically.
|
||
|
|
To manually configure attribute caching, the administrator should perform
|
||
|
|
cn=monitor searches to understand how to make attribute caching most effective.
|
||
|
|
These searches return current information listing which attributes are cached,
|
||
|
|
the amount of memory used by each attribute cache, the total amount of memory
|
||
|
|
used by attribute caching, the amount of memory configured for attribute caching,
|
||
|
|
and a list of the attributes most often used in search filters. Using this
|
||
|
|
information, an administrator can change the amount of memory that is allowed
|
||
|
|
to be used for attribute caching, as well as which attributes to cache whenever
|
||
|
|
necessary based on new cn=monitor searches.</p>
|
||
|
|
<p>Alternatively, an administrator can configure automatic attribute caching.
|
||
|
|
When automatic attribute caching is enabled, the Directory Server tracks the
|
||
|
|
combination of attributes that would be most useful to cache within the memory
|
||
|
|
limits defined by the administrator. It then updates the attribute caching
|
||
|
|
at a time and time interval configured by the administrator.</p><img src="deltaend.gif" alt="End of change" /><img src="deltaend.gif" alt="End of change" />
|
||
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
|
</body>
|
||
|
|
</html>
|