Install DS for User Data

If you have user data in an LDIF format file, consider using this profile. To import generated sample user data instead, see Install DS for Evaluation.

This profile includes indexes that are appropriate for inetOrgPerson entries:

1. Before proceeding, install the server files as described in Unpack Files.

2. Run the setup command with the --profile ds-user-data option:

   $ /path/to/opendj/setup \
    --deploymentKey $DEPLOYMENT_KEY \
    --deploymentKeyPassword password \
    --rootUserDN uid=admin \
    --rootUserPassword str0ngAdm1nPa55word \
    --monitorUserPassword str0ngMon1torPa55word \
    --hostname ds.example.com \
    --adminConnectorPort 4444 \
    --ldapPort 1389 \
    --enableStartTls \
    --ldapsPort 1636 \
    --httpsPort 8443 \
    --replicationPort 8989 \
    --bootstrapReplicationServer rs1.example.com:8989 \
    --bootstrapReplicationServer rs2.example.com:8989 \
    --profile ds-user-data \
    --set ds-user-data/baseDn:dc=example,dc=com \
    --set ds-user-data/ldifFile:/tmp/user-data.ldif \
    --acceptLicense

   In this example, the /tmp/user-data.ldif contains the user data entries to import. This is just a placeholder. When you run the command, replace it with your LDIF file containing your own user data.

   • The deployment key for installing the server is stored in the environment variable DEPLOYMENT_KEY. Install all servers in the same deployment with the same deployment key and deployment key password. For details, read "Key Management".

   • The data is stored in the userData backend.

   For the full list of profiles and parameters, see "Default Setup Profiles".

3. (Optional) Finish configuring the server before you start it.

   For a list of optional steps at this stage, see Install DS for Custom Cases.

4. Start the server:

   $ /path/to/opendj/bin/start-ds