Creating and Deleting a Directory Server Instance

This section shows how to create and delete a Directory Server instance.

To Create a Directory Server Instance

Before you can administer data, you must create a Directory Server instance by using command-line tools or the browser interface Directory Service Control Center (DSCC). In DSCC, a Directory Server instance is often referred to simply as a “Directory Server”.

When you create a Directory Server instance, the files and directories required for your Directory Server are created in the instance-path that you specify.

You can use DSCC to perform this task. For information, see Directory Service Control Center Interface and the DSCC online help.

If you use DSCC to create a new server instance, you can choose to copy some or all server configuration settings from an existing server.

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).

1. Create a new Directory Server instance and set the instance path.

   $ dsadm create instance-path

   You are prompted to set a password for the Directory Manager for this server.

   To specify a non-default port number for the server instance, or any other parameter, see the dsadm(1M) man page.

   For example, to create a new instance in the directory /local/dsInst, use this command:

   $ dsadm create /local/dsInst
   Choose the Directory Manager password:
   Confirm the Directory Manager password:
   Use 'dsadm start /local/dsInst' to start the instance 

   The instance is created in a directory on the local file system and not a network file system.

2. Check that the server instance has been created correctly.

   $ dsadm info instance-path

   For example:

   $ dsadm info /local/dsInst
   Instance Path:         /local/dsInst
   Owner:                 user1(group1)
   Non-secure port:       1389
   Secure port:           1636
   Bit format:            64-bit
   State:                 Running
   Server PID:            22555
   DSCC url:              -
   SMF application name:  -
   Instance version:      D-A00

3. (Optional) If your operating system provides a service management solution, you can enable the server to be managed as a service, as shown in this table.
   

   Operating System Command Solaris 10 dsadm enable-service --type SMF instance-path Solaris 9 dsadm autostart instance-path Windows dsadm enable-service --type WIN_SERVICE instance-path

4. Start Directory Server.

   $ dsadm start instance-path

   ---

   Note - The server is running but does not contain data or a suffix. Use dsconf to create a suffix.

   ---

5. (Optional) Register the server instance with Directory Service Control Center by using either of the following methods.
   • Login to DSCC, and then use the Register Existing Server action on the Servers tab of the Directory Servers tab.

     Access DSCC using http://hostname:8080/dscc7 or https://hostname:8181/dscc7 as per your application server configuration.

   • Use the command dsccreg add-server.

     $ dsccreg add-server -h hostname --description "My DS" /local/dsInst
     Enter DSCC administrator's password:
     /local/dsInst is an instance of DS
     Enter password of "cn=Directory Manager" for /local/dsInst:
     This operation will restart /local/dsInst.
     Do you want to continue ? (y/n) y
     Connecting to /local/dsInst
     Enabling DSCC access to /local/dsInst
     Restarting /local/dsInst
     Registering /local/dsInst in DSCC on hostname.

     See dsccreg(1M) for more information about the command.

6. If you want to use a password policy and your Directory Server instance is standalone, or if it belongs to a replication topology that has already been migrated to to-DS6-only password policy mode, move the instance to that mode.

   $ dsconf pwd-compat -h host -p port to-DS6-migration-mode
   
   ## Beginning password policy compatibility changes .
   ## Password policy compatibility changes finished.
   
   Task completed (slapd exit code: 0).
   $ dsconf pwd-compat -h host -p port to-DS6-mode
   
   ## Beginning password policy compatibility changes .
   ## Password policy compatibility changes finished.
   
   Task completed (slapd exit code: 0).

   The above action should be performed in the specified sequence.

   For more information about password policies compatibilities, see Password Policy in Oracle Directory Server Enterprise Edition Upgrade and Migration Guide.

To Delete a Directory Server Instance

Before you delete the server instance, you must prepare the instance for deletion. Refer to the following procedure to delete a server instance successfully:

You can use DSCC to perform this task. For information, see Directory Service Control Center Interface and the DSCC online help.

1. Stop the Directory Server.

   $ dsadm stop [--force] instance-path

2. If the server was previously registered with DSCC, unregister the server using the following command:

   $ dsccreg remove-server /local/dsInst
   Enter DSCC administrator's password:
   /local/dsInst is an instance of DS
   Enter password of "cn=Directory Manager" for /local/dsInst:
   This operation will restart /local/dsInst.
   Do you want to continue ? (y/n) y
   Unregistering /local/dsInst from DSCC on localhost.
   Connecting to /local/dsInst
   Disabling DSCC access to /local/dsInst
   Restarting /local/dsInst

   For details, see the dsccreg(1M) man page.

3. (Optional) If you previously enabled the server instance in a service management solution, disable the server from being managed as a service.
   

   Operating System Command Solaris 10 dsadm disable-service --type SMF instance-path Solaris 9 dsadm autostart --off instance-path Windows dsadm disable-service --type WIN_SERVICE instance-path

4. Delete the server instance.

   $ dsadm delete instance-path

   ---

   Caution - This command removes everything, under the instance-path directory. If the instance has been enabled as a service, or if the instance is started automatically at system startup, dsadm delete requires root access.

   ---