The comm_dssetup.pl script performs the following steps:

1. Prompts you for your deployment's Directory Server and schema information.

   For a list of the specific information this step requests, see "Information Needed to Run the comm_dssetup.pl Script".

2. Generates a shell script and LDIF file from the information that you supply that is used to modify the Directory Server LDAP.

   If you are not using Oracle Directory Server Enterprise Edition, or have customized your Directory Server, stop the process here without running the script. For more information, see "Directory Server Considerations for the comm_dssetup.pl Script".

3. Runs the generated shell script and modifies your Directory Server.

At the end of each step, the comm_dssetup.pl script prompts you to continue. No changes are made to the Directory Server LDAP until the last step.

When running the comm_dssetup.pl script, consider the following points.

• comm_dssetup.pl configures local Directory Server instances, and thus you must:

  • Install the comm_dssetup.pl script on every host on which a Directory Server instance resides.

  • Run the comm_dssetup.pl script on the same host as your Directory Server. The tool runs locally for a specific instance (specified by path of Directory Server or path of instance).

• You can run the comm_dssetup.pl script against any Directory Server instance on the local host. If you have multiple Directory Information Trees (DITs) on one host, you can maintain and update one installation of comm_dssetup.pl, and apply it to every Directory Server instance on the host.

• comm_dssetup.pl must configure every Directory Server instance for the same DIT. This assumes that:

  • A Directory Server has already been installed, configured, and is running before you launch the comm_dssetup.pl script.

  • When adding an additional Directory Server host (such as a replica), at a future date, you must run the comm_dssetup.pl script against it, too.

• If you have customized your Directory Server, the following considerations might apply:

  • If you have indexed some attributes, you might have to reindex those attributes after running the comm_dssetup.pl script.

  • If you have added other LDIF files (schema definitions), they should not be affected, so no action should be necessary. However, back up your custom schema definition files before running the comm_dssetup.pl script.

    The comm_dssetup.pl script backs up old schema files to the /var/tmp/dssetup_timestamp/save directory.

  • For all Directory Server customizations, including the first two just listed, stop the comm_dssetup.pl script after it generates the script and before it actually updates the LDAP directory. Then inspect the script to evaluate how its proposed actions affect your LDAP directory. Take whatever actions you think necessary to protect your customizations before running the script against your Directory Server.

Table A-1 describes the information about your deployment that you need to gather before running the comm_dssetup.pl script.

The comm_dssetup.pl script prompts you for both the Directory Server root path and the Directory Server instance. The script then combines these two items into an absolute path name to the Directory Server instance. For example, if your Directory Server instance resides under the /var/opt/sun/directory/slapd-varrius directory, then you specify /var/opt/sun/directory for the Directory Server root path and slapd-varrius for the Directory Server instance.

The reason for having two comm_dssetup.pl prompts to specify one absolute path is historical. Prior to Directory Server 6, Directory Server had the concept of a "server root" under which all Directory Server instances (as well as the Directory Server binaries) resided. After Directory Server 6, the concept of the "server root" was removed. Directory Server instances (as well as the Directory Server binaries) do not all have to reside under a single umbrella "server root" directory.

Messaging Server supports the following schema choices:

• LDAP Schema 2 native mode

  Corresponds to comm_dssetup.pl script schema version choice 2. This is the default for a fresh installation.

• LDAP Schema 1

  Corresponds to the comm_dssetup.pl script schema version choice 1.

• LDAP Schema 2 compatibility mode

  Corresponds to comm_dssetup.pl script schema version choice 1.5.

Attribute indexes improve the performance of search algorithms. The comm_dssetup.pl script offers you the choice to index attributes.

Table A-2 lists all the attributes for the comm_dssetup.pl script indexes, grouped by suffix category. It also lists the type of indexes created for each attribute. For more information about Directory Server indexing, see the Directory Server documentation at:

http://docs.oracle.com/cd/E20295_01/index.htm

To add additional indexes on your own, see the Directory Server documentation.

To run the comm_dssetup.pl script in silent mode:

1. On the host where Directory Server is installed, log in as or become the superuser (root).

2. Start Directory Server, if necessary.

3. Change to the directory where you installed or copied the Directory Server Setup comm_dssetup.pl script.

4. Run the script followed by the silent mode options.

   All options are required. For more information, see "Silent Mode Options".

   /usr/bin/perl comm_dssetup.pl
   -i yes|no -R yes|no -c DirectoryServerRoot -d DirectoryInstance
   -r DCTreeSuffix -u UserGroupSuffix -s yes|no -D DirectoryManagerDN
   -j DirectoryManagerPasswordFile -b yes|no 
   -t 1|1.5|2 -m yes|no [-S PathtoSchemaFiles ]
   

   The script creates the following LDIF file and shell script to update the LDAP indexes and schema:

   • /var/tmp/dssetup_timestamp/dssetup.ldif

   • /var/tmp/dssetup_timestamp/dssetup.sh

5. If you answered no to the -R and -m options, you need to manually run the dssetup.sh script that was created.

   If you answered yes to the -R and -m options, the dssetup.sh script is run automatically.

Table A-3 describes the comm_dssetup.pl silent mode options.