To Create a Directory Server Instance
From the Command Line

In this procedure, you create a server instance on
the local host using the dsadm command. You then create
a suffix that you populate with data using the dsconf command.

Non-root users can create server instances.

A Directory Server instance contains the configuration and data necessary
to respond to directory client applications. When you start or stop an instance,
you start or stop the server process. The server process is what serves directory
client requests corresponding to the data managed by that instance.

The dsadm command enables you to manage a Directory Server instance
and the files belonging to that instance on the local host. The command does
not let you administer servers over the network, but only directly on the
local host. The dsadm command has subcommands for each
key management task. For a complete description, see dsadm(1M).

The dsconf command is an LDAP client. The command
enables you to configure nearly all server settings on a running Directory Server instance
from the command line. You can configure settings whether the server is on
the local host or another host that is accessible across the network. The dsconf command has subcommands for each key configuration task.
For a complete description, see dsconf(1M).

Before You Begin

For example, the following command creates an instance under the existing
directory, /local/, in a new directory, /local/ds/. The new instance has default ports
389 for LDAP, 636 for LDAPS for root, and 1389 for LDAP,
1636 for LDAPS for non-root users.

At this point in the procedure, you have a working server instance.
You must further configure the server instance, however. Furthermore, the instance is
not yet registered with Directory Service Control Center.

(Optional) Use the new password policy mode, unless
the instance belongs to a topology with version 5 instances.

Your
server instance might be standalone. Alternatively, your instance might belong
to a replication topology that has already been migrated to the new password
policy mode. In either case, perform this step.