HP-UX Directory Server 8.1 plug-in reference

Table Of Contents
Line 10 uses the nsslapd-pluginid attribute to set the name of the plug-in. The name
that you specify here will show up in the Directory Server Console. In this example, the
plug-in identification is set to Example Preoperation Plug-in.
Line 11 sets the version number of the plug-in. This version number is also displayed in the
Directory Server Console and is used to track the version of the distributed plug-in. It does
not indicate the Directory Server compatibility; this is defined by the plug-in version number
described in “Specifying Directory Server compatibility”.
Line 12 identifies the vendor or author of the plug-in. In the following line, the vendor is
set to Example Corporation:
nsslapd-pluginvendor: Example Corporation
Finally, Line 13 sets the description of the plug-in. This is the description visible through
the Directory Server Console.
3.1.1 Plug-in dependencies
You can specify that your plug-in be dependent on one or more different plug-ins. Any specified
plug-in dependencies must start correctly before your associated plug-in will start.
There are two attributes that you can use in the plug-in configuration file to specify the
dependencies of your plug-in:
nsslapd-plugin-depends-on-named
nsslapd-plugin-depends-on-type
Each of these attributes can take multiple values, meaning that your plug-in depends on one or
more other plug-ins.
3.1.1.1 Specific plug-in dependencies
If you specify the nsslapd-plugin-depends-on-named attribute in your plug-in configuration
file, set its value to the names of one or more plug-ins. For example, in your plug-in configuration
file, you could specify the following:
nsslapd-plugin-depends-on-named: my_pluginA
nsslapd-plugin-depends-on-named: vendor_pluginB
In this example, the plug-in depends on two specifically named plug-ins: my_pluginA and
vendor_pluginB. This configuration line indicates that before your plug-in can be loaded, the
two specifically named plug-ins must be loaded. If either of these two plug-ins fails to load, the
Directory Server will exit with a -1 error code.
3.1.1.2 Plug-in type dependencies
If you specify the nsslapd-plugin-depends-on-type attribute in your plug-in configuration
file, set its value to one or more plug-in types. For example, in your plug-in configuration file,
you could specify the following:
nsslapd-plugin-depends-on-type: syntax
This configuration line indicates that your plug-in depends on any plug-in of the type syntax.
If there is a configured plug-in of type syntax, it must be successfully loaded before your plug-in
can be loaded; otherwise, the Directory Server will exit with a -1 error code.
If you specify a plug-in type dependency, the Directory Server will search for any and all plug-ins
of the types specified. If none are found, processing will continue without errors. However, the
Directory Server must load all plug-ins of the types specified before it can load your plug-in. For
a complete list of the supported plug-in types, refer to the “Summary of plug-in directives”.
38 Configuring plug-ins