Table of Contents
Advertisement
entry
len
Since the text of the entry is passed in as an argument, you can modify the entry
before it gets saved to disk and modify the entry after it is read from disk.
NOTE
Registering Entry Store/Fetch Functions
Unlike most other types of plug-in functions, you do not register an entry store or
entry fetch plug-in function by setting the function name in the parameter block.
Instead, you specify the function name directly in the server configuration file.
In Directory Server 6.x, shut down the server, add the plug-in parameters to the
dse.ldif
example, your plug-in entry might look like this:
dn: cn=Test entry,cn=plugins,cn=config
objectClass: top
objectClass: nsSlapdPlugin
objectClass: extensibleObject
cn: Test entry
nsslapd-pluginPath: /usr/netscape/servers/plugins/slapd/slapi/
nsslapd-pluginInitfunc: testentry_init
nsslapd-pluginType: ldbmentryfetchstore
nsslapd-pluginEnabled: on
nsslapd-pluginId: test-entry
For example plug-in functions that implement entry store and entry fetch
operations, take a look at this source file:
<server_root>/plugins/slapd/slapi/examples/testentry.c
In Directory Server 4.x, add a directive, to the
following form to specify the name and location of your plug-in function:
Pointer to a string specifying the entry in LDIF format; for
details on this format, see "slapi_filter_free()" on page 309.
Pointer to the length of the entry string.
For example entry store and entry fetch plug-in functions, check
this source file in your installation:
<server_root>/plugins/slapd/slapi/examples/testentry.c
file, and restart the server (see Chapter 3, "Configuring Plug-Ins"). For
examples/libtest-plugin.so
Registering Entry Store/Fetch Functions
slapd.ldbm.conf
Chapter 9
Writing Entry Store/Fetch Plug-Ins
file, in the
115
Advertisement
Table of Contents
