You can use the manage-profile tool to set up an instance of the server
from information contained in a server profile. This tool invokes
setup and performs other tasks, such as applying
configuration changes, installing schema and extensions, and adding files to the
server root.
-
Place an appropriate set of arguments 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.
Because manage-profile setup uses the setup tool in
non-interactive mode, you should use the arguments listed in the previous
section, including:
- --existingDSTopologyHostName
{address}
- --existingDSTopologyPort
{port}
- --existingDSTopologyUseSSL
- --existingDSTopologyUseStartTLS
- --existingDSTopologyUseNoSecurity
- --existingDSTopologyUseJavaTruststore
{path}
- --existingDSTopologyUsePkcs12Truststore
{path}
- --existingDSTopologyTrustStorePassword
{password}
- --existingDSTopologyTrustStorePasswordFile
{path}
- --existingDSTopologyBindDN
{path}
- --existingDSTopologyBindPassword
{password}
- --existingDSTopologyBindPasswordFile
{path}
Note:
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.
-
Run manage-profile setup.
-
If you have already set up an instance of the server, 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 includes an appropriate set of arguments for joining the
same topology.