From this page you can also:
- Edit the configurable settings of an implementation package.
- Add a new implementation package.
- Specify the name of the new package, up to 255 characters. You cannot include angle brackets (<>) or ampersands (&) in the
- Check this to set the package to available.
- Package Module
- Specify the name of the library that contains the new package. You need to specify this only if the program is in a library
that has a different name than the package name. Include the extension; library files have the extension
.dll on Windows,
.so on UNIX,
.sl on HP-UX PA-RISC.
- Package Path
- Specify the path or paths where the executable program or programs are located. Separate paths with semicolons on Windows,
and with colons on UNIX. If you do not specify this, the Directory Server looks for the file first in the path included in
the interface definition table, and then in the paths specified by the COBDIR environment variable.
- Specify the pathname of the Interface Definition Table (IDT) for the package.
- IDT Resident
- Check this if you want the IDT to be loaded into the shared memory area while the service is running. This can help performance
if the service is frequently used and there are no constraints on shared memory.
- Custom Configuration
- This field is not used.
- An optional field that is used to specify a description of the package, for example, its purpose and owner.