nsUniqueIdGenerator This sets whether to generate a unique ID for the imported entries. By default, this attribute generates time-based IDs.

Parameter

Description

Entry DN

cn=task_name, cn=import, cn=tasks, cn=config

 

 

Valid Values

none (no unique ID)

 

empty (time-based ID)

 

deterministic namespace (name-based ID)

 

 

Default Value

empty

 

 

Syntax

Case-insensitive string

 

 

Example

nsUniqueIdGenerator:

 

 

nsUniqueIdGeneratorNamespace This attributes defines how to generate name-based IDs; the attribute sets the namespace to use to generate the IDs. This option is useful to import the same LDIF file into two Directory Server instances when the entries need to have the same IDs.

Parameter

Description

Entry DN

cn=task_name, cn=import, cn=tasks, cn=config

 

 

Valid Values

Any string

 

 

Default Value

 

 

 

Syntax

Case-insensitive string

 

 

Example

nsUniqueIdGeneratorNamespace: example

 

 

2.3.14.3 cn=export,cn=tasks,cn=config

A database or multiple databases can be exported through the command line by creating a special task entry which defines the parameters of the task and initiates the task. As soon as the task is complete, the task entry it removed from the directory.

The cn=export entry is a container entry for export task operations. The cn=export entry itself has no attributes, but each of the task entries within this entry, such as cn=task_ID, cn=export, cn=tasks, cn=config, uses the following attributes to define the export task.

An export task entry under cn=export must contain the name of the database to export (in the “nsInstance” attribute) and the name of the LDIF file to write the output to (in the “nsFilename” attribute). Additionally, it must contain a unique cn to identify the task. For example:

dn: cn=example export, cn=export, cn=tasks, cn=config

objectclass: nsDirectoryServerTask

cn: example export

nsInstance: userRoot

nsFilename: /home/files/example.ldif

As the export operation runs, the task entry will contain all the server-generated task attributes listed in “Task invocation attributes for entries under cn=tasks”.

There are some optional attributes which can be used to refine the export operation, similar to the options for the db2ldif and db2ldif.pl scripts:

•“nsIncludeSuffix”, analagous to the -soption, to specify the suffixes to include in the exported LDIF files

•“nsExcludeSuffix”, analagous to the -xoption, to exclude the specified suffixes from the exported LDIF files

•“nsUseOneFile”, analagous to the -Moption, to break up the exported suffixes into individual LDIF files

2.3 Core server configuration attributes reference 103