The presence of the file server.uuid in the server’s config directory indicates whether the server is being set up initially or being updated.

  1. Create or obtain the topology.json file either manually or by using external automation. When promoting from a dev/test environment to a stage/prod environment, you can obtain a topology.json file using the manage-topology export subcommand.
  2. The server instance is installed and configured with a server profile, as follows:
    manage-profile setup \
      --profile /path/to/server-profile \
      --profileVariablesFile /path/to/
  3. If you are not using persistent storage, remove the previous self from the topology:
    remove-defunct-server \
      --serverInstanceName \
      --bindDN dn \
      --bindPassword password \
      --retryTimeoutSeconds 120

    If you are using persistent storage, proceed directly to the next step.

  4. Use the following command to enable replication within the topology:
    dsreplication enable \
      --topologyFilePath /path/to/topology.json \
      --retryTimeoutSeconds 120

    For the sake of simplicity, other dsreplication options are not shown.

  5. Initialize the replication data, as follows:
    dsreplication initialize \
      --topologyFilePath /path/to/topology.json
For more information about server profiles, see Server profiles.