After you install the PingDirectory server, you can install and set up the PingDirectoryProxy server.
Click the following tabs to see instructions for the type of installation you want to perform.
Installing the server in interactive mode
The setup command provides an interactive text-based interface to install a PingDirectoryProxy server instance.
Installing the first server
Installing additional servers
The setup command provides an interactive text-based interface to install a PingDirectoryProxy server instance that clones a previously installed PingDirectoryProxy server instance.
Installing the server in non-interactive mode
You can run the setup command in non-interactive mode to automate the installation process using a script or to run the command directly from the command line.
The following sections describe how to install the first PingDirectoryProxy server, how to install additional servers, and how to install the server with a truststore.
Installing the first server
The setup command automatically chooses the maximum heap size. You can manually tune the maximum amount of memory devoted to the server’s process heap using the --maxHeapSize option. The --maxHeapSize option is only valid if the --entryBalancing option is also present.
If you are using entry balancing, tune the amount of memory devoted to the PingDirectoryProxy server using the --entryBalancing option as follows.
--entryBalancing --maxHeapSize 1g
The amount of memory allowed when using the --entryBalancing option is calculated and depends on the amount of system memory available.
If you already configured a truststore, you can run the setup command to enable security. The following example enables both SSL and StartTLS security. It also specifies a Java Keystore (JKS) and Truststore that define the server certificate and trusted CA. The passwords for the keystore files are defined in the corresponding .pin files, where the password is written on the first line of the file. The values in the .pin files are copied to the <server-root>/config directory in the keystore.pin file.
$ env JAVA_HOME=/ds/java ./setup \
--no-prompt --rootUserDN "cn=Directory Manager" \
--rootUserPassword "password" --ldapPort 389 \
--enableStartTLS --ldapsPort 636 \
--useJavaKeystore /path/to/devkeystore.jks \
--keyStorePasswordFile /path/to/devkeystore.pin \
--certNickName server-cert \
--useJavaTrustStore /path/to/devtruststore.jks \
--trustStorePasswordFile /path/to/devtruststore.pin \
--acceptLicense
The password to the private key within the keystore is expected to be the same as the password to the keystore. If this is not the case, you can define the private key password within the administrative console or using the dsconfig command by editing the Trust Manager Provider standard configuration object.
Installing additional servers
Installing the server with a truststore
If you've already configured a trust store, you can use the setup command to enable security. The following example enables SSL security and specifies a Java KeyStore (JKS) and truststore that define the server certificate and trusted certificate authority (CA). The passwords for the keystore files are defined in the corresponding .pin files, where the password displays on the first line of the file. The values in the .pin files are copied to the server-root/config directory in the keystore.pin and truststore.pin files.