HP UX Identity Security Software manual 101

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

objectclass: nsDirectoryServerTask

cn: example import

nsFilename: /home/files/example.ldif

nsInstance: userRoot

As the import 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 import operation, similar to the options for the ldif2db and ldif2db.pl scripts:

•“nsIncludeSuffix”, which is analogous to the -soption to specify the suffix to import

•“nsExcludeSuffix”, analogous to the -xoption to specify a suffix or subtree to exclude from the import

•“nsImportChunkSize”, analogous to the -coption to override starting a new pass during the import and merge the chunks

•“nsImportIndexAttrs”, which sets whether to import attribute indexes (with no corollary in the script options)

•“nsUniqueIdGenerator”, analogous to the -goption to generate unique ID numbers for the entries

•“nsUniqueIdGeneratorNamespace”, analogous to the -Goption to generate a unique, name-based ID for the entries

nsFilename The nsFilename attribute contains the path and file names of the LDIF files to import into the Directory Server instance. To import multiple files, add multiple instances of this attribute. For example:

nsFilename: file1.ldif

nsFilename: file2.ldif

Parameter	Description
Entry DN	cn=task_name, cn=import, cn=tasks, cn=config
Valid Values	Any string
Default Value
Syntax	Case-exact string, multi-valued
Example	nsFilename: /home/jsmith/example.ldif

nsInstance This attribute supplies the name of the database instance into which to import the files, such as NetscapeRoot or slapd-example

Parameter	Description
Entry DN	cn=task_name, cn=import, cn=tasks, cn=config
Valid Values	The name of a Directory Server instance (any string)
Default Value
Syntax	Case-exact string
Example	nsInstance: userRoot

2.3 Core server configuration attributes reference 101