Install Standalone Servers

Standalone replication servers have no application data backends. They store only changes to directory data. They are dedicated to transmitting replication messages, and to maintaining a replication change log.

Standalone directory servers store replicated copies of application data. These replicas send updates to and receive updates from replication servers. They connect to one replication server at a time, and do not maintain a replication change log.

Each replication server in a deployment connects to all other replication servers. The total number of replication connections, Totalconn, increases like the square of the number of replication servers. Large deployments that span WAN links can therefore benefit from having fewer replication servers.

Totalconn = (NRS * (NRS-1))/2 + NDS

Here, NRS is the number of replication servers (standalone or running in a directory server), and NDS is the number of standalone directory servers.

A deployment with only a few standalone replication servers and many standalone directory servers, significantly limits the number of WAN connections for replication:

Deployment For Multiple Data Centers
Dedicated servers are suited to WAN deployments with many replicas.

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

Set Up Standalone Replication Servers

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

  2. Set up a server as a standalone replication server: 

    $ /path/to/opendj/setup \
 --deploymentKey $DEPLOYMENT_KEY \
 --deploymentKeyPassword password \
 --rootUserDN uid=admin \
 --rootUserPassword password \
 --hostname rs-only.example.com \
 --adminConnectorPort 4444 \
 --replicationPort 8989 \
 --bootstrapReplicationServer rs-only.example.com:8989 \
 --bootstrapReplicationServer rs-only2.example.com:8989 \
 --acceptLicense

    The standalone replication server has no application data.

    It does have LDAP schema and changelog data. If you plan to add any additional schema to the replicas as part of the setup process, also add the schema to this server before starting it.

  3. Start the server: 

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

  4. Repeat the previous steps on additional systems until you have sufficient replication servers to meet your availability requirements.

    To ensure availability, add at least one additional replication server per location. The following example adds a second standalone replication server: 

    $ /path/to/opendj/setup \
 --deploymentKey $DEPLOYMENT_KEY \
 --deploymentKeyPassword password \
 --rootUserDN uid=admin \
 --rootUserPassword password \
 --hostname rs-only2.example.com \
 --adminConnectorPort 4444 \
 --replicationPort 8989 \
 --bootstrapReplicationServer rs-only.example.com:8989 \
 --bootstrapReplicationServer rs-only2.example.com:8989 \
 --acceptLicense

    The standalone replication servers use each other as bootstrap servers to discover other servers in the deployment.

Set Up Standalone Directory Servers

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

  2. Set up the server as a directory server.

    Notice that the --bootstrapReplicationServer references the replication servers set up according to the steps in "Set Up Standalone Replication Servers". The --replicationPort option is not used, because this is a standalone directory server: 

    $ /path/to/opendj/setup \
 --serverId evaluation-only \
 --deploymentKey $DEPLOYMENT_KEY \
 --deploymentKeyPassword password \
 --rootUserDN uid=admin \
 --rootUserPassword password \
 --adminConnectorPort 4444 \
 --hostname ds-only.example.com \
 --ldapPort 1389 \
 --enableStartTls \
 --ldapsPort 1636 \
 --httpsPort 8443 \
 --bootstrapReplicationServer rs-only.example.com:8989 \
 --bootstrapReplicationServer rs-only2.example.com:8989 \
 --profile ds-evaluation \
 --acceptLicense

  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

  5. Repeat the previous steps on additional systems until you have sufficient directory servers to meet your availability and performance requirements.

    To ensure availability, add at least one additional directory server per location.

Read a different version of :