Page created: 6 Nov 2019
|
Page updated: 25 Mar 2020
| 2 min read
8.0 Product PingDirectory PingDirectoryProxy IT Administrator Administrator Audience System Administrator Software Deployment Method Administration User task Configuration Installation Product documentation Content Type Capability Directory
-
Copy the keystore and pin files into the config directory
for the proxy-east-02.example.com server.
root@proxy-east-02: cp ../*Keystore* config/ root@proxy-east-02: cp ../*Truststore* config/
-
Install the second Directory Proxy Server by running the
setup tool on proxy-east-02.example.com as follows:
root@proxy-east-02: ./setup --no-prompt \ --listenAddress proxy-east-02.example.com \ --ldapPort 389 --enableStartTLS --ldapsPort 636 \ --useJavaKeystore config/ExampleKeystore.jks \ --keyStorePasswordFile config/ExampleKeystore.pin \ --certNickName server-cert \ --useJavaTrustStore config/ExampleTruststore.jks \ --rootUserPassword pass --acceptLicense \ --aggressiveJVMTuning --maxHeapSize 1g \ --localHostName proxy-east-02.example.com \ --peerHostName proxy-east-01.example.com \ --peerPort 389 --location east
-
Configure the third Directory Proxy Server,
proxy-west-01.example.com in the same way as shown in the previous step. First,
copy the keystore and pin files into the config
directory.
root@proxy-west-01: cp ../*Keystore* config/ root@proxy-west-01: cp ../*Truststore* config/
-
Run the setup tool on proxy-west-01.example.com as follows:
root@proxy-west-01: ./setup --no-prompt \ --listenAddress proxy-west-01.example.com \ --ldapPort 389 --enableStartTLS --ldapsPort 636 \ --useJavaKeystore config/ExampleKeystore.jks \ --keyStorePasswordFile config/ExampleKeystore.pin \ --certNickName server-cert \ --useJavaTrustStore config/ExampleTruststore.jks \ --rootUserPassword pass --acceptLicense \ --aggressiveJVMTuning --maxHeapSize 1g \ --localHostName proxy-west-01.example.com \ --peerHostName proxy-east-01.example.com \ --peerPort 389 --location west
-
Finally, repeat steps 3 and 4 to install the last Directory Proxy Server by first copying the keystore and pin
files to the config directory and then running the
setup command.
At this point, all proxies have the same Admin Data backend and have the
all-servers
group defined as their configuration-server-group in the Directory Proxy Server Global Configuration object. When making a change to a Directory Proxy Server using the dsconfig command-line tool or the Administrative Console, you will have the choice to apply the changes locally only or to all proxies in theall-servers
group.