mfds [/d|/dn network-address|/n network-address] [/j journal-path] [/r] [/p port-number]
mfds [/p port-number] -s option [username password]
mfds /e root-DN user-partition-DN group-partition-DN resource-partition-DN schema-format ldif-filename sec-path
mfds /l [schema partition Distinguished Name] option ldif-filename [schema-version-1] [schema-version-2]
mfds -x [repository type] [repository address] [server name] <options> <user id> <password>
"mfds -x 1 c:\myrepository *"
"mfds -x 1 c:\myrepository * S"
"mfds -x 1 c:\myrepository * O"
"mfds /x 1 c:\myrepository * SO"
"mfds /x 1 c:\myrepository ESDEMO"
"mfds /x 1 c:\myrepository ESDEMO D myid mypwd"
mfds /t output-filename input-filename
If output-filename is not specified, a default file of journal.txt will be created in the same directory as the input-filename
If input-filename is not specified, the default journal.dat file as specified by the default MFDS options file (mfdsacfg.dat) will be used.
This option can only convert journal.dat files to text if they have originated on the same hardware and software platform; it is not guaranteed that journal files imported from UNIX can be read by Windows and visa versa.
Use this startup option to block anonymous read access to the MFDS ES configuration data. If this option is specified, applications that connect to the MFDS process to query ES configuration information (for example mdump and other utilities) will be required to specify valid credentials based on the current MFDS security configuration, otherwise the connection will be rejected.
mfds /g [repository type] [repository address] <opts> <user id> <password>
The application partition to which all of the exported entries will be assigned.
The name of the container within the application partition to which the exprted users will be assigned.
The container within the application partition to which the exported groups will be assigned.
The container within the application partition to which the exported resource definitions will be assigned.
Values: 1 = Active Directory (Default).
The location of the MF Directory Server repository.
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.
Specifies the target directory server type: 0 = Microsoft Active Directory Application Mode (ADAM), 1 = Active Directory (Default), 2 = OpenLDAP, 3 = Sun Directory
If you specify the ldif-filename , you must also specify a value for this parameter.
Specifies the name of the destination file.
Default: mfds_schema_[ mfds version ].ldf (e.g. mfds_schema_1.05.09.ldf)
Specifies the version of the schema extensions to be generated: 0 = current schema version (Default). Numbers greater than 0 specify older schema versions.
This option is used for upgrading from a previous schema. If schema-version-2 is specified and is less 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.
Many programs depend on Directory Server using the default port (86). Therefore, if you use an alternative port, you may experience interoperability problems.
You should also consider carefully before using this option to run more than one Directory Server on the same machine. By default, both would use the same options file and repository, and might therefore encounter conflicts.
Username and password: These must be supplied if the Directory Server is running with Restrict administration access checked.
On UNIX you should use a dash (-) before a parameter as an alternative to a forward slash (/).