Before you can use an LDAP repository to hold information for Enterprise Developer applications, its schema must be extended to support the Enterprise Developer objects. To do this, you create an LDIF (Lightweight Directory Interchange Format) file containing the extensions.
Use themfds -L command line options to do this.
mfds -L [schema partition Distinguished Name] option ldif-filename [schema-version-1] [schema-version-2]
| Parameter | Description |
|---|---|
| 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:
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 (for example, mfds_schema_1.05.09.ldf) |
| schema-version-1 | Specifies the version of the schema extensions to be generated:
|
| schema-version-2 | This option is used for upgrading from a previous schema. If schema-version-2 is specified and is less than the schema-version-1,
the output file is a delta between the schema-version-1 and schema-version-2.
If schema-version-2 is greater than or equal to schema-version-1, this option is ignored. |
To create a LDIF file called mfds-schema.ldf specifically for an Active Directory using the this_machine.mycom.com AD server, issue the following command:
mfds -L DC=mycom,DC=com 1 c:\mfds-schema.ldf
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 LDIFDE tool is used to extend the repository schema, the generated LDIF 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.