Netscape logo Configuration, Command, and File Reference
Netscape Directory Server                                                                                                                                  
Previous
 Contents
 Index
 DocHome Next


Appendix   Using the ns-slapd and slapd.exe Command-Line Utilities



In chapter 8, "Command-Line Scripts," we looked at the scripts for performing routine administration tasks on the Netscape Directory Server (Directory Server). In this appendix, we will look at the ns-slapd and slapd command-line utilities that can also be used to perform the same tasks.

This chapter contains the following sections:


Overview of ns-slapd and slapd.exe Commands

The ns-slapd and slapd.exe command-line utilities all perform server administration tasks, and, while it can be argued that they allow a greater degree of flexibility for users, we still recommend that you use the command-line scripts presented in chapter 8, "Command-Line Scripts."


ns-slapd (UNIX)

ns-slapd is used on a Unix operating system to start the Directory Server process, to build a directory database from an LDIF file, or to convert an existing database to an LDIF file. For more information on starting and stopping the Directory Server, importing from LDIF using the command-line, and exporting to LDIF using the command-line, see chapter 4, "Populating Directory Databases," in the Netscape Directory Server Administrator's Guide.


slapd.exe (Windows)

slapd.exe is the Windows equivalent of ns-slapd.

Note 

You must stop the server before running the ns-slapd and slapd.exe command-line utilities.


Finding and Executing the ns-slapd and slapd.exe Command-Line Utilities

The ns-slapd command-line utilities are stored under:

serverRoot/bin/slapd/server/ns-slapd

The slapd.exe command-line utilities are stored under:

serverRoot\bin\slapd\server\slapd.exe

Do not mistake ns-slapd.exe, the slapd process watchdog, for slapd.exe on Windows.

Caution 

In order to execute the command-line utilities, you must change directories to the directory where the command-line utilities are stored. Although it is possible to set command-path and library-path variables to execute the utilities, this is not recommended procedure because you run the risk, particularly when you have more than one server version installed, not only of disrupting the correct execution of other utilities, but also of compromising the security of the system.


ns-slapd and slapd.exe Command-Line Utilities for Exporting Databases

db2ldif

Exports the contents of the database to LDIF.

Syntax

Shell script (UNIX):

ns-slapd db2ldif -D configDir -a outputFile [-d debugLevel] [-n backendInstance] [ -r] [-s includeSuffix] [-x excludeSuffix] [-N] [-u] -[U]

Batch file (Windows):

slapd.exe db2ldif -D configDir -a outputFile [-d debugLevel] [-n backendInstance] [-r] [-s includeSuffix] [-x excludeSuffix] [-N] [-u] [-U]

For slapd-serverID, the location of your server configuration directory, enter the full path. You must also specify either the -n or the -s option.


Options

Option

Parameter

Description

-a

outputFile

Defines the output file in which the server saves the exported LDIF. This file is stored by default in the directory where the command-line utility resides.

-d

debugLevel

Specifies the debug level to use during the db2ldif runtime. For further information, see nsslapd-errorlog-level (Error Log Level).

-D

configDir

Specifies the location of the server configuration directory that contains the configuration information for the export process. You must specify the full path to the slapd-serverID directory.

-N

 

Specifies that entry IDs are not to be included in the LDIF output. The entry IDs are necessary only if the db2ldif output is to be used as input to db2index.

-r

 

Causes the server to include the copiedFrom attribute and its contents in the LDIF output when importing the LDIF file to a consumer server. This information is required by the server by the replication process.

If you use the -r option, you also need to specify the suffix you want to export by using the -s option. You must shut down the server before exporting using this option.

-s

includeSuffix

Specifies the suffix or suffixes to include in the export. You may use multiple -s arguments. If you do not specify -s or -x, the server exports all suffixes within the database. If you use both -x and -s arguments with the same suffix, the -x operation takes precedence. Exclusion always takes precedence over inclusion.

If you exclude one or more suffixes from the exported LDIF file and you intend to import the LDIF file into your configuration directory, do not exclude o=NetscapeRoot. If you use -s to specify a suffix to include and you intend to import the LDIF file into your configuration directory, make sure that you also use -s to include o=NetscapeRoot.

-u

 

Specifies that the uniqueID will not be included in the LDIF output. By default, the server includes the uniqueID for all entries with a uniqueID in the exported LDIF file.

Only use this option if you intend to use the exported LDIF to initialize a 4.x consumer server.; otherwise, this option does not cause the server to create a uniqueID for entries but simply takes what already exists in the database.

-U

 

Outputs the contents of the database without wrapping lines.

-x

excludeSuffix

Specifies a suffix or suffixes to exclude in the export. You may use multiple -x arguments. If you do not specify -s or -x, the server exports all suffixes within the database. If you use both -x and -s options with the same suffix, the -x operation takes precedence. Exclusion always takes precedence over inclusion. If you intend to import the LDIF file into your configuration directory, do not exclude o=NetscapeRoot.

-n

backendInstance

Specifies the name of the backend instance to be exported.


ns-slapd and slapd.exe Command-Line Utilities for Restoring and Backing up Databases

ldif2db

Imports LDIF files to the database.

Syntax

Shell script (UNIX):

ns-slapd ldif2db -D configDir -i ldifFile [-d debugLevel] [-g string] [-n backendInstance] -O [-s includeSuffix] [-x excludeSuffix]

Batch file (Windows):

slapd ldif2db -D configDir -i ldifFile [-d debugLevel] [-g string] [-n backendInstance] [-O] [-s includeSuffix] [-x excludeSuffix]

For configDir, which is the location of your server configuration directory, enter the full path. ldifFile is the name of the file containing the LDIF to be imported. You can find a demo LDIF file under the serverRoot/slapd-serverID/ldif directory. You must also specify either the -n or the -s option.


Options

Option

Parameter

Description

-d

debugLevel

Specifies the debug level to use during runtime. For further information, see nsslapd-errorlog-level (Error Log Level).

-D

configDir

Specifies the location of the server configuration directory that contains the configuration information for the import process. You must specify the full path to the slapd-serverID directory.

-g

string

Generation of a unique ID. Type none for no unique ID to be generated and deterministic for the generated unique ID to be name-based. By default, a time-based unique ID is generated.

If you use the deterministic generation to have a name-based unique ID, you can also specify the namespace you want the server to use as follows:

-g deterministic namespace_id

where namespace_id is a string of characters in the following format:

00-xxxxxxxx-xxxxxxxx-xxxxxxxx-xxxxxxxx

Use this option if you want to import the same LDIF file into two different directory servers and you want the contents of both directories to have the same set of unique IDs. If unique IDs already exist in the LDIF file you are importing, then the existing IDs are imported to the server, regardless of the options you have specified.

-i

ldifFile

Specifies the LDIF file to be imported. This option is required. You can use multiple -i arguments to import more than one LDIF file at a time. When you import multiple files, the server imports the LDIF files in the order in which you specify them from the command-line.

-n

backendInstance

Specifies the name of the backend to be imported.

-O

 

Specifies that no attribute indexes are created for the imported database. If you specify this option and you want to restore the indexes later, you will need to recreate the indexes by hand. See the Netscape Directory Server Administrator's Guide for further information.

-s

includeSuffix

Specifies the suffix or suffixes within the LDIF file you want to import. If you use -s to specify a suffix to include and you are importing the LDIF file into your configuration directory, make sure that you also use -s to include o=NetscapeRoot. You can use multiple -s arguments. If you use both -x and -s with the same suffix, -x takes precedence. Exclusion always takes precedence over inclusion. If you do not specify -x or -s, then all available suffixes will be imported from the LDIF file.

-x

excludeSuffix

Allows you to specify suffixes within the LDIF file to exclude during the import. You can use multiple -x arguments. This option lets you selectively import portions of the LDIF file. If you use both -x and -s with the same suffix, -x takes precedence. Exclusion always takes precedence over inclusion. If you do not specify -x or -s, then all available suffixes will be imported from the LDIF file. If you are importing the LDIF file into your configuration directory, do not exclude o=NetscapeRoot.

Caution 

If you are importing the LDIF file into your configuration directory, make sure the o=NetscapeRoot suffix and its contents are included in your LDIF file before you import. Do not exclude the suffix o=NetscapeRoot using -s, -x, or a combination of the two. The Netscape Administration Server uses this suffix to store information about installed Netscape servers. Failure to import o=NetscapeRoot into your configuration directory could force you to reinstall (or restore from backup) all of your Netscape servers, including the Directory Server.


archive2db

Restores database from the archives.

Syntax

Shell script (UNIX):

slapd archive2db -D configDir -a archiveDir

Batch file (Windows):

slapd archive2db -D configDir -a archiveDir



Options

Option

Parameter

Description

-D

configDir

Specifies the location of the server configuration directory that contains the configuration information for the index creation process. You must specify the full path to the slapd-serverID directory.

-a

archiveDir

Specifies the archive directory.


db2archive

Backs up all databases to the archives.

Syntax

Shell script (UNIX):

slapd db2archive -D configDir -a archiveDir

Batch file (Windows):

slapd db2archive -D configDir -a archiveDir


Options

Option

Parameter

Description

-D

configDir

Specifies the location of the server configuration directory that contains the configuration information for the index creation process. You must specify the full path to the slapd-serverID directory.

-a

archiveDir

Specifies the archive directory.


ns-slapd and slapd.exe Command-Line Utilities for Creating and Regenerating Indexes

db2index

Creates and regenerates indexes.

Syntax  

Shell script (UNIX):

slapd db2index -D configDir [-d debugLevel] -n backendName -t attributeName [:indexTypes [:matchingRules]] | [-T vlvTag]

Batch file (Windows):

slapd db2index -D configDir [-d debugLevel] -n backendName -t attributeName [:indexTypes [:matchingRules]] | [-T vlvTag]


Options

Option

Parameter

Description

-d

debugLevel

Specifies the debug level to use during index creation. For further information, see nsslapd-errorlog-level (Error Log Level).

-D

configDir

Specifies the location of the server configuration directory that contains the configuration information for the index creation process. You must specify the full path to the slapd- serverID directory.

-n

backendName

Specifies the name of the backend containing the entries to index.

-t

attributeName

Specifies the attribute to be indexed as well as the types of indexes to create and matching rules to apply (if any). If you want to specify a matching rule, you must specify an index type. You cannot use this option with option -T.

indexTypes specifies a comma-separated list of indexes to be created for the attributes.

matchingRules is an optional, comma-separated list of the OIDs for the languages in which you want the attribute to be indexed. This option is used to created international indexes. For information on supported locales and collation order OIDs, see Appendix D, "Internationalization," in the Netscape Directory Server Administrator's Guide.

-T

vlvTag

Specifies the VLV tag to use to create VLV indexes. You can use the console to specify VLV tags for each database supporting your directory tree, as described in xref. You can define additional VLV tags by creating them in LDIF and adding them in the Directory Server configuration, as described in xref. You cannot use this option with option -t.

 



Previous
 Contents
 Index
 DocHome Next
© 2001 Sun Microsystems, Inc. Portions copyright 1999, 2002-2004 Netscape Communications Corporation. All rights reserved.
Read the Full Copyright and Third-Party Acknowledgments.

 last updated November 26, 2004