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

Note:

If you're not using persistent storage, set up a new server and skip step 3. If you are using persistent storage, start on step 3.

For more information about server profiles, see Server profiles.

  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 manage-topology export.

  2. To install and configure a server instance, run the manage-profile command with the setup option. 
    manage-profile setup \
  --profile /path/to/server-profile \
  --profileVariablesFile /path/to/instance-specific-variables.properties
  3. If you're using persistent storage, replace the current server profile. Otherwise, proceed to step 4. To replace the current profile, run the manage-profile replace-profile command from a second, extracted server install package on the same host as the existing server. 
    manage-profile replace-profile \
  --profile /path/to/server-profile \
  --profileVariablesFile /path/to/instance-specific-variables.properties
  --serverRoot /path/to/existing/server
  4. To enable replication within the topology, run dsreplication with the enable option. 
    dsreplication enable \
  --topologyFilePath /path/to/topology.json \
  --retryTimeoutSeconds 120
  5. To initialize the replication data, run dsreplication with the initialize option. 
    dsreplication initialize \
  --topologyFilePath /path/to/topology.json