---
title: Configure PingDataSync in standard mode
description: The create-sync-pipe-config tool is used to configure Sync Pipes and Sync Classes. For bidirectional deployments, configure two Sync Pipes, one for each directional path.
component: pingdirectory
version: 11.0
page_id: pingdirectory:pingdatasync_server_administration_guide:pd_sync_config_pds_standard_mode
canonical_url: https://docs.pingidentity.com/pingdirectory/11.0/pingdatasync_server_administration_guide/pd_sync_config_pds_standard_mode.html
revdate: September 13, 2023
---

# Configure PingDataSync in standard mode

The `create-sync-pipe-config` tool is used to configure Sync Pipes and Sync Classes. For bidirectional deployments, configure two Sync Pipes, one for each directional path.

```
xref:pd_sync_use_create_sync_pipe_tool.adoc[] illustrates a bidirectional synchronization deployment in standard mode. The example assumes that two replicated topologies are configured:
```

* The first endpoint topology consists of two Sun LDAP servers: the main server and one failover. Both servers have Retro change logs enabled and contain the full DIT that will be synchronized to the second endpoint.

* The second endpoint topology consists of two PingDirectory servers: the main server and one failover. Both servers have change logs enabled and contain entries similar to the first endpoint servers, except that they use a `mail` attribute, instead of an `email` attribute.

A specific `mail` to `email` mapping must also be created to exclude the source attribute on the Sync Pipe going the other direction.

|   |                                                                                                                                                                                                                |
| - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | If the source attribute is not excluded, PingDataSync will attempt to create an `email` attribute on the second endpoint, which could fail if the attribute is not present in the destination server's schema. |

Then, two Sync Classes are defined:

* One to handle the customized `email` to `mail` attribute mapping *(tooltip: \<div class="paragraph">
  \<p>Matching corresponding attributes between an IdP and an SP to identify federated users or add supplemental user information.\</p>
  \</div>)*.

* Another to handle all other cases (the default Sync Class).

The `dsconfig` command is used to create the specific attribute mappings. The `resync` command is used to test the mappings. Synchronization can start using the `realtime-sync` command.