Object Classes For Plug-In Configuration; Server Plug-In Functionality Reference - Netscape DIRECTORY SERVER 6.01 Configuration Manual

Server Plug-in Functionality Reference

dn: cn=Telephone Syntax,cn=plugins,cn=config
objectclass: top
objectclass: nsSlapdPlugin
objectclass: extensibleObject
cn: Telephone Syntax
nsslapd-pluginPath: /usr/ipalnet/servers/lib/syntax-plugin.so
nsslapd-pluginInitfunc: tel_init
nsslapd-pluginType: syntax
nsslapd-pluginEnabled: on
shows us some of the plug-in configuration attributes. Some of these attributes are
common to all plug-ins while others may be particular to a specific plug-in. You
can check which attributes are currently being used by a given plug-in by
performing an

Object Classes for Plug-in Configuration

All plug-ins are instances of the
from the
taken into account by the server both of these object classes (in addition to the
object class) must be present in the entry as shown in the following example:
dn:cn=ACL Plugin,cn=plugins,cn=config
objectclass:top
objectclass:nsSlapdPlugin
objectclass:extensibleObject
Server Plug-in Functionality Reference
The following tables provide you with a quick overview of the plug-ins provided
with Directory Server 6.x, along with their configurable options, configurable
arguments, default setting, dependencies, general performance related information
and further reading. These tables will allow you to weigh up plug-in performance
gains and costs and choose the optimal settings for your deployment. The Further
Information heading cross references further reading where this is available.
110 Netscape Directory Server Configuration, Command, and File Reference • January 2002
on the
ldapsearch
object class. For plug-in configuration attributes to be
extensibleObject
subtree.
cn=config
object class which in turn inherits
nsSlapdPlugin
top