If you run setup without any arguments, it starts in interactive mode and prompts you for all of the necessary information. After you accept the license, the next prompt asks if you want to add the server to an existing PingDirectoryProxy Server topology. If you have at least one PingDirectoryProxy Server instance that is already in the desired topology, you can enter “yes” at this prompt and it will walk you through the process of creating a new instance that is a copy of the existing instance (with all of the same configuration). You are then asked for the information needed to connect and authenticate to the existing PingDirectoryProxy Server instance. For example:

Do you accept the terms of this license agreement?  Enter 'yes' to accept,
'no' to reject, or press ENTER to display the next page of the agreement []: yes
 
Would you like to add this server to an existing Directory Proxy Server
topology? (yes / no) [no]: yes
 
Enter the host name of the peer Directory Proxy Server from which you would
like to copy configuration settings. [proxy2.example.com]: proxy1.example.com
 
Enter the LDAP port of the peer Directory Proxy Server [389]: 636
 
How would you like to connect to the peer Directory Proxy Server?
 
    1)  None
    2)  SSL
    3)  StartTLS
 
Enter option [1]: 2
 
Enter the manager account DN for the peer Directory Proxy Server [cn=Directory
Manager]: cn=Directory Manager
 
Enter the password for cn=Directory Manager:
The server presented the following certificate chain:
 
     Subject: CN=proxy1.example.com,O=Example Corp,C=US
     Valid From: Saturday, November 2, 2019 at 10:34:09 PM CDT
     Valid Until: Sunday, November 1, 2020 at 09:34:09 PM CST
     SHA-1 Fingerprint: 54:7f:6c:c1:99:73:c4:19:66:6e:da:4b:ee:a9:d5:62:24:2e:ba:41
     256-bit SHA-2 Fingerprint: 54:ce:59:c5:25:85:95:17:17:69:e0:5c:57:9e:ed:27:3d:af:9c:bd:34:51:c8:46:1e:e4:2f:31:13:18:31:ca
     -
     Issuer 1 Subject: CN=Example Certification Authority,O=Example Corp,C=US
     Valid From: Saturday, November 2, 2019 at 10:34:03 PM CDT
     Valid Until: Friday, October 28, 2039 at 10:34:03 PM CDT
     SHA-1 Fingerprint: 34:25:1f:8f:18:ff:a8:a9:ac:22:d3:d2:fc:bb:0b:4c:53:e1:8c:de
     256-bit SHA-2 Fingerprint: 51:69:1f:bb:cf:6f:1c:7a:e6:d4:6d:5a:01:c7:08:45:88:53:fc:75:f1:63:bb:ec:65:f1:1f:4e:26:f0:89:a3
 
Do you wish to trust this certificate?  Enter 'y' or 'n': y
 
 
Initializing ..... Done
Reading Peer Configuration ..... Done
Connecting to 'proxy1' ..... Done

However, cloning an existing installation isn’t possible when setting up the first PingDirectoryProxy Server instance. In this case, if you enter “no” at the prompt to join an existing PingDirectoryProxy Server topology, setup asks if you want to join a Directory Server topology instead. If you enter “yes”, the process is basically the same as joining an existing PingDirectoryProxy Server topology and you are prompted for the information needed to connect and authenticate to a Directory Server instance in the topology. The primary difference is that you have to define the PingDirectoryProxy Server configuration yourself. For example:

Do you accept the terms of this license agreement?  Enter 'yes' to accept,
'no' to reject, or press ENTER to display the next page of the agreement []: yes
 
Would you like to add this server to an existing Directory Proxy Server
topology? (yes / no) [no]: no
 
Would you like to add this server to an existing PingDirectory server topology
to enable automatic backend server discovery? (yes / no) [no]: yes
 
Enter the host name of a PingDirectory server instance in the topology to
join. [proxy1.example.com]: ds1.example.com
 
Enter the LDAP port of a PingDirectory server instance in the topology to join
[389]: 636
 
How would you like to secure communication with the PingDirectory server
 
    1)  None
    2)  SSL
    3)  StartTLS
 
Enter option [1]: 2
 
Enter the DN used to bind to a PingDirectory server instance in the topology
to join [cn=Directory Manager]: cn=Directory Manager
 
Enter the password for cn=Directory Manager:
Testing connection to the existing PingDirectory server topology
The server presented the following certificate chain:
 
     Subject: CN=ds1.example.com,O=Example Corp,C=US
     Valid From: Saturday, November 2, 2019 at 10:44:26 PM CDT
     Valid Until: Sunday, November 1, 2020 at 09:44:26 PM CST
     SHA-1 Fingerprint: e1:4a:9e:dc:55:e8:40:78:9b:e1:1b:bd:3e:4c:85:fb:60:b4:27:35
     256-bit SHA-2 Fingerprint: 6e:92:c7:d6:66:c8:3d:2d:04:4c:f2:6a:cb:cb:51:5a:bf:f8:d6:18:0a:fc:64:d9:76:f4:4e:58:eb:c0:b8:b7
     -
     Issuer 1 Subject: CN=Example Certification Authority,O=Example Corp,C=US
     Valid From: Saturday, November 2, 2019 at 10:44:23 PM CDT
     Valid Until: Friday, October 28, 2039 at 10:44:23 PM CDT
     SHA-1 Fingerprint: 9a:b7:aa:a3:33:49:ce:b8:f3:7e:60:13:e0:3c:63:4b:8f:95:7a:f3
     256-bit SHA-2 Fingerprint: 04:07:86:f2:5c:e2:c1:88:fe:08:27:c1:1e:52:b0:4b:98:6e:a8:5c:85:fc:e0:d9:25:4f:07:ae:d7:0d:43:ba
 
Do you wish to trust this certificate?  Enter 'y' or 'n': y
Successfully connected to the existing PingDirectory server topology