Understand best practices for remote eDNA access

While the eDNA to PI Migration Utility must be installed on the same machine as the destination Data Archive, there is no requirement that the eDNA Server also be on the same node. The eDNA to PI Migration Utility supports reading eDNA data from a remote system, as long as the PI and eDNA machines reside on the same network and some simple configuration guidelines are followed.

To allow for remote connections between the Data Archive/Migration Utility machine and the eDNA Server, follow these best practices:

• Ensure that Enterprise Data Management services are running on the eDNA machine.

• Install eDNA Client on the Data Archive machine. During this installation, be sure to perform the following tasks:

  • Accept all default settings, except when configuring Service Directory. For this entry, supply the IP address of the remote eDNA machine.

  • If you have modified the SvcDir port on your eDNA server, modify the PORT entry under [SVCDIR] in the DNASYS.INI file on your Data Archive machine to match this value.

• Ensure that the DnaServices, SVCDIR and HISTORY services are running on the remote eDNA machine.

• In general, the configuration of the machine running the eDNA to PI Migration Utility should match the same configuration as other eDNA Client to eDNA server connections in your environment, with regards to the DNASYS.INI file and firewall rules.

• Follow the instructions in List of port settings for remote eDNA access.