---
title: Configuring additional PingDirectoryProxy server instances
description: Install and configure additional PingDirectoryProxy server using the setup tool.
component: pingdirectory
version: 11.0
page_id: pingdirectory:pingdirectoryproxy_server_administration_guide:pd_proxy_config_additional_dps_instances
canonical_url: https://docs.pingidentity.com/pingdirectory/11.0/pingdirectoryproxy_server_administration_guide/pd_proxy_config_additional_dps_instances.html
revdate: September 13, 2023
section_ids:
  about-this-task: About this task
  steps: Steps
  example: Example:
  example-2: Example:
  example-3: Example:
  example-4: Example:
  result: Result
---

# Configuring additional PingDirectoryProxy server instances

Install and configure additional PingDirectoryProxy server using the `setup` tool.

## About this task

Install and configure the second PingDirectoryProxy server by running the `setup` tool on `proxy-east-02.example.com`.

## Steps

1. Copy the key store and `.pin` files into the `config` directory for the `proxy-east-02.example.com` server.

   ### Example:

   ```
   root@proxy-east-02: cp ../Keystore config/
   root@proxy-east-02: cp ../Truststore config/
   ```

2. Install the second PingDirectoryProxy server by running the `setup` tool on `proxy-east-02.example.com`.

   ### Example:

   ```
   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 \
   --maxHeapSize 1g --localHostName proxy-east-02.example.com \
   --peerHostName proxy-east-01.example.com \
   --peerPort 389 --location east
   ```

3. Configure the third PingDirectoryProxy server, `proxy-west-01.example.com` in the same way as shown in steps 1 - 2.

   ### Example:

   ```
   root@proxy-west-01: cp ../Keystore config/
   root@proxy-west-01: cp ../Truststore config/
   ```

4. Run the `setup` tool on `proxy-west-01.example.com`.

   ### Example:

   ```
   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 \
   --maxHeapSize 1g --localHostName proxy-west-01.example.com \
   --peerHostName proxy-east-01.example.com \
   --peerPort 389 --location west
   ```

5. Repeat steps 1 - 4 to install the last PingDirectoryProxy server.

## Result

All proxies have the same Admin Data backend and have the `all-servers` group defined as their configuration-server-group in the PingDirectoryProxy Server Global Configuration object. When making a change to a PingDirectoryProxy server using the `dsconfig` command-line tool or the admin console, you have the choice to apply the changes locally only or to all proxies in the `all-servers` group.