Replicator Wizard

The Replicator Wizard supports you when connecting a data source to the estos ProCall.

In principle, the configuration is carried out in the following steps:

1. Select data source type
   estos ProCall supports the importing of contact data:
   • from the Active Directory®
   • from a csv/txt file
   • via Microsoft® Exchange Webservic (EWS)
   • Replicator for the Microsoft® Graph interface


2. Define the login information with which it is possible to access the data source.
   • Applications can be started either in a user context or a system context. With the rights of the application comes access to the database. Therefore, it is important that the system or the corresponding user can access the data sources.

     Make sure you know under which user context the source database can be accessed or whether this is possible from a system context.

     	Connected network drives are not known in a system and user context. If you wish to access files on another computer, you must use fully qualified UNC paths (\\Server\Share\File). Keep in mind that the user or the system requires access rights to this sharing and the corresponding files. In the case of an ODBC access, you must enter the UNC path manually in the ODBC Connect String.
     	It should be noted that the configuration of the replicator always occurs in a user context. The Administrator starts with your user rights, thus the Replicator Wizard also starts with your rights. As a result, the source database is accessed with your rights. If the Replicator is running with other user rights or in a system context, the Replicator may NOT be able to access the data source.
     	If you can configure the replicator, but the replicator does not function properly, check in the log file whether the source database can be opened. If there are errors here, make sure you know which user rights can be used to open the data source.



3. Settings for the data source (selection of the server, data structure to be imported, etc.)
• The settings for the data source are strongly tied to the respective data source. Depending on the replicator, you must provide different information about the location of the source data.


4. Field allocation – which source fields are being copied to which LDAP fields
• The field allocation is the central part of the replicator connection. Depending on the replicator, you can allocate which source fields should be copied to which LDAP fields. Some replicators have a fixed field allocation stored.
  
  On the left side you see the source fields. Along with the field names, the content of the first found data record is depicted. Use the arrow keys to scroll through the data records below the source.
  
  On the right side you see the LDAP target fields. Along with the field names, the assigned fields are depicted.
  If you can define the field assignment yourself, the buttons for deleting the entire assignment and, if available, for setting the default field assignment are located below the target list.
  Both lists illustrate the field assignments with small icons:
  • Field not used
  • Field used once
  • Field used multiple times
  
  The buttons for loading and storing field allocations are located in the lower left corner of the dialog. Information about field allocation:
  • The primary key must be assigned and unique for every source data record.
  • Each source database normally has a corresponding primary key. Use this key.

    When the source database does not offer a primary key, use database fields which can be unambiguously allocated to an entry. If necessary, concatenate the fields in order to obtain a unique primary key. If several data records should have identical primary keys, all data records will be lost after the first replication. You can use e-mail addresses, for example, as alternative primary keys.

  • In the "Displayed Name" field the replicator will always attempt to make an assignment. If the field could not be filled from the predefined source fields, the replicator will attempt to generate content from the last name, first name and company or email address.
  • Fields can be concatenated. If it is a telephone number field, the source data are directly linked to one another. In all other cases, a space is placed between.



5. Defining replication schedule
• Define when replication begins and the interval in which it should be carried out.