Before you can use an LDAP repository to hold information for Micro Focus applications, its schema must be extended to support the Micro Focus objects. To do this, you create an LDIF (Lightweight Directory Interchange Format) file containing the extensions.
Use the mfds -L command line options to do this.
mfds -L [schema partition Distinguished Name] option ldif-filename
schema partition Distinguished Name | Specifies the DN of the partition in the Directory Information Tree where the schema definition is held. The schema partition holds, amongst other things, attributeSchema and classSchema objectclass instances. |
option | Specifies the target directory server type: 1 = Active
Directory (Default), 2 = OpenLDAP
Note: If you specify the ldif-filename , you must also specify a value for this parameter. |
ldif-filename | Specifies the name of the destination file.
Default: mfds_schema_[ mfds version ].ldf (e.g. mfds_schema_1.05.09.ldf) |
To create a LDIF file called mfds-schema.ldf specifically for an Active Directory using the this_machine.mycom.com AD server, issue:
mfds -L DC=mycom,DC=com 1 c:\mfds-schema.ldf
However, in practice, rather than using a specific schema partition DN value, administrators may want to have a portable LDIF file where the root DN can be specified externally. If the Windows LDFIDE tool is used to extend the repository schema, the generated LDF file could use "DC=X" as the schema partition name. This can then be replaced at import time. For example,
mfds -L DC=X 1
should be sufficient for most installations.
Related topics:
Guides
General tasks
Active Directory and ADAM tasks
OpenLDAP tasks