The manage-profile tool can be used to set up an instance of the server from information contained in a server profile. This is like an enhanced version of the setup utility in non-interactive mode because not only does it invoke setup, but it can also perform other tasks like applying configuration changes, installing schema and extensions, and adding files to the server root.

Since manage-profile setup uses the setup tool in non-interactive mode, you should use the arguments listed in the previous section, including the following:
  • --existingDSTopologyHostName {address}
  • --existingDSTopologyPort {port}
  • --existingDSTopologyUseSSL
  • --existingDSTopologyUseStartTLS
  • --existingDSTopologyUseNoSecurity
  • --existingDSTopologyUseJavaTruststore {path}
  • --existingDSTopologyUsePkcs12Truststore {path}
  • --existingDSTopologyTrustStorePassword {password}
  • --existingDSTopologyTrustStorePasswordFile {path}
  • --existingDSTopologyBindDN {path}
  • --existingDSTopologyBindPassword {password}
  • --existingDSTopologyBindPasswordFile {path}

An appropriate set of arguments should be placed in the setup-arguments.txt file in the root directory of the profile, along with all of the other arguments that should be used when invoking setup.

If you have already set up an instance of the server, you can run manage-profile generate-profile to generate a profile from the information contained in that instance. If the server was added to the topology during the setup process, the generated profile will include an appropriate set of arguments for joining the same topology.

Note that unlike the setup utility, manage-profile setup does not support cloning an existing PingDirectoryProxy Server instance, so the --peerHostName, --peerPort, and other related arguments cannot be included in the setup-arguments.txt file.