A man page is intended to answer concisely the question “What does it do?” The man pages in general comprise a reference manual. Man pages are not intended to be a tutorial.
The following contains a brief description of each man page section and the information the section references.
Section 1 describes, in alphabetical order, commands available for Directory Server Enterprise Edition.
Section 1M describes, in alphabetical order, commands that are used chiefly for Directory Server Enterprise Edition maintenance and administration purposes.
Section 4 outlines the formats of files delivered with Directory Server Enterprise Edition.
Section 5dsconf describes Directory Server configuration properties. You modify these properties using the dsconf command.
Section 5dsconf also describes legacy Directory Server configuration attributes. You modify these attributes using the ldapmodify command on the entries under cn=config.
Section 5dpconf describes Directory Proxy Server configuration properties. You modify these properties using the dpconf command.
Section 5dssd describes collections of LDAP schema objects that Directory Server provides. See Intro(5dssd) for an introduction to the LDAP schema reference documentation.
Section 5dsat describes attribute types defined in the LDAP schema that Directory Server provides.
Section 5dsoc describes object classes defined in the LDAP schema that Directory Server provides.
Below is a generic format for man pages. The man pages of each manual section generally follow this order, but include only needed headings. See man(1) for more information about man pages in general.
This section gives the names of the commands or functions documented, followed by a brief description of what they do.
This section shows the syntax of commands or functions. When a command or file does not exist in the standard path, its full path name is shown. Options and arguments are alphabetized, with single letter arguments first, and options with arguments next, unless a different argument order is required.
The following special characters are used in this section:
Brackets. The option or argument enclosed in these brackets is optional. If the brackets are omitted, the argument must be specified.
Ellipses. Several values can be provided for the previous argument, or the previous argument can be specified multiple times, for example, "filename …" .
Separator. Only one of the arguments separated by this character can be specified at a time.
Braces. The options and/or arguments enclosed within braces are interdependent, such that everything enclosed must be treated as a unit.
This section defines the functionality and behavior of the service. Thus it describes concisely what the command does. It does not discuss OPTIONS or cite EXAMPLES. Interactive commands, subcommands, requests, macros, and functions are described under USAGE.
This secton lists the command options with a concise summary of what each option does. The options are listed literally and in the order they appear in the SYNOPSIS section. Possible arguments to options are discussed under the option, and where appropriate, default values are supplied.
This section lists the command operands and describes how they affect the actions of the command.
This section describes the output – standard output, standard error, or output files – generated by the command.
If the man page documents functions that return values, this section lists these values and describes the conditions under which they are returned. If a function can return only constant values, such as 0 or –1, these values are listed in tagged paragraphs. Otherwise, a single paragraph describes the return values of each function. Functions declared void do not return values, so they are not discussed in RETURN VALUES.
On failure, most functions place an error code in the global variable errno indicating why they failed. This section lists alphabetically all error codes a function can generate and describes the conditions that cause each error. When more than one condition can cause the same error, each condition is described in a separate paragraph under the error code.
This section provides examples of usage or of how to use a command or function. Wherever possible a complete example including command-line entry and machine response is shown. Whenever an example is given, the prompt is shown as $, or if the user must be superuser, #. Examples are followed by explanations, variable substitution rules, or returned values. Most examples illustrate concepts from the SYNOPSIS, DESCRIPTION, OPTIONS, and USAGE sections.
This section lists any environment variables that the command or function affects, followed by a brief description of the effect.
This section lists the values the command returns to the calling program or shell and the conditions that cause these values to be returned. Usually, zero is returned for successful completion, and values other than zero for various error conditions.
This section lists all file names referred to by the man page, files of interest, and files created or required by commands. Each is followed by a descriptive summary or explanation.
This section lists characteristics of commands, utilities, and device drivers by defining the attribute type and its corresponding value. See attributes(5) for more information.
This section lists references to other man pages, in-house documentation, and outside publications.
This section lists diagnostic messages with a brief explanation of the condition causing the error.
This section lists warnings about special conditions which could seriously affect your working conditions. This is not a list of diagnostics.
This section lists additional information that does not belong anywhere else on the page. It takes the form of an aside to the user, covering points of special interest. Critical information is never covered here.
This section describes known bugs and, wherever possible, suggests workarounds.
This documentation set explains how to use Directory Server Enterprise Edition to evaluate, design, deploy, and administer directory services. In addition, it shows how to develop client applications for Directory Server Enterprise Edition. The Directory Server Enterprise Edition documentation set is available at http://docs.sun.com/coll/1819.3.
For an introduction to Directory Server Enterprise Edition, review the following documents in the order in which they are listed.
Table P–1 Directory Server Enterprise Edition Documentation
Document Title |
Contents |
---|---|
Oracle Fusion Middleware Release Notes for Oracle Directory Server Enterprise Edition |
Contains the latest information about Directory Server Enterprise Edition, including known problems. |
Oracle Fusion Middleware Evaluation Guide for Oracle Directory Server Enterprise Edition |
Introduces the key features of this release. Demonstrates how these features work and what they offer in the context of a fictional deployment that you can implement on a single system. |
Oracle Fusion Middleware Deployment Planning Guide for Oracle Directory Server Enterprise Edition |
Explains how to plan and design highly available, highly scalable directory services based on Directory Server Enterprise Edition. Presents the basic concepts and principles of deployment planning and design. Discusses the solution life cycle, and provides high-level examples and strategies to use when planning solutions based on Directory Server Enterprise Edition. |
Oracle Fusion Middleware Installation Guide for Oracle Directory Server Enterprise Edition |
Explains how to install the Directory Server Enterprise Edition software. Shows how to configure those components after installation, and verify that the configured components function properly. |
Oracle Fusion Middleware Upgrade and Migration Guide for Oracle Directory Server Enterprise Edition |
Provides instructions for upgrading components from earlier versions of Directory Server Enterprise Edition. |
Oracle Fusion Middleware Administration Guide for Oracle Directory Server Enterprise Edition |
Provides command-line instructions for administering Directory Server Enterprise Edition. For hints and instructions on using the DSCC to administer Directory Server Enterprise Edition, see the online help provided in the DSCC. For instructions on administering Identity Synchronization for Windows, go to http://docs.sun.com/coll/isw_04Q3. |
Oracle Fusion Middleware Reference for Oracle Directory Server Enterprise Edition |
Introduces the technical and conceptual foundations of Directory Server Enterprise Edition. Describes its components, architecture, processes, and features. |
Oracle Fusion Middleware Man Page Reference for Oracle Directory Server Enterprise Edition |
Describes the command-line tools, schema objects, and other public interfaces that are available through Directory Server Enterprise Edition. Individual sections of this document can be installed as online manual pages. |
Sun Java System Identity Synchronization for Windows 6.0 Deployment Planning Guide |
Provides general guidelines and best practices for planning and deploying Identity Synchronization for Windows |
Oracle Fusion Middleware Troubleshooting Guide for Oracle Directory Server Enterprise Edition |
Provides information to define the scope of the problem, gather data, and troubleshoot the problem areas using various tools. |
Sun Java System Identity Synchronization for Windows 6.0 Installation and Configuration Guide |
Describes how to install and configure Identity Synchronization for Windows. |
Installation Instructions for Identity Synchronization for Windows 6.0 Service Pack 1 |
Provides additional installation instructions to avoid certain pitfalls associated with the Identity Synchronization for Windows installation. |
The SLAMD Distributed Load Generation Engine (SLAMD) is a Java application that is designed to stress test and analyze the performance of network-based applications. It was originally developed by Sun Microsystems, Inc. to benchmark and analyze the performance of LDAP directory servers. SLAMD is available as an open source application under the Sun Public License, an OSI-approved open source license. To obtain information about SLAMD, go to http://www.slamd.com/. SLAMD is also available as a java.net project. See https://slamd.dev.java.net/.
Java Naming and Directory Interface (JNDI) technology supports accessing the Directory Server using LDAP and DSML v2 from Java applications. For information about JNDI, see http://java.sun.com/products/jndi/. The JNDI Tutorial contains detailed descriptions and examples of how to use JNDI. this tutorial is at http://java.sun.com/products/jndi/tutorial/.
Directory Server Enterprise Edition does not provide any files that you can redistribute.
This section explains the default paths used in the documentation, and gives the locations of commands on different operating systems and deployment types.
The following table describes the default paths that are used in this book.
Table P–2 Default Paths
To know more about each of the commands, see the relevant man pages. For full descriptions of the files installed, see Chapter 1, Directory Server Enterprise Edition File Reference, in Oracle Fusion Middleware Reference for Oracle Directory Server Enterprise Edition.