Setting Up the Synergy OpenNET Server
If the SQL Server database is on a different server than the replicator process then you will need to start and configure the Synergy OpenNET Server on the Windows system that hosts the SQL Server database. This requires you to install Synergy/DE "Core Components" and "Connectivity" on the database server. Assuming the server is running 64-bit Windows you should install 64-bit Synergy. In the unlikely event that your server is running 32-bit Windows, install 32-bit Synergy.
In this scenario the Windows server will need permanent access to two Synergy licenses:
1.A SQL Connection for SQL Server license (SCSQ10) to allow the remote replicator process to connect to the SQL Server database via the Synergy OpenNET server.
2.A Synergy runtime license (RUN10) to allow you to run the FileService server to support bulk uploads (more later).
Declaring the OpenNET protocol to Windows
After installing Synergy, start a copy of notepad as administrator, then edit the following file:
C:\WINDOWS\SYSTEM32\drivers\etc\services
Add the following line to the file:
vtxnet 1958/tcp #Synergy/DE OpenNET Server
Close and save the file.
Registering and Starting the OpenNET Server
You can register and start the Synergy OpenNET server as a Windows service by using the Synergy Configuration Program, which you can access from the windows control panel.
1.Run the windows control panel (control.exe)
2.Search for the word Synergy, then click on the Synergy Control Panel icon to start the utility.
3.Click on the link for the Synergy Configuration program (64-bit).
4.In the Synergy Configuration Program, go to the Connectivity Series tab.
5.Click on the Add Service button to register the OpenNET server as a Windows Service.
6.Click on the Start Service button to start the service.
In the future the service will start automatically when Windows starts.
Verifying Access to the OpenNET Server
It is a good idea to verify that you can access the OpenNET service from the system that you intend to run the replicator process from. You can do this using the VTXPING utility. For example:
C:\> vtxping -p1958 SISQL2017
VORTEXping - Network Checker.
Version 4.0.0.17 - Production.
Copyright ⌐ 1989-2016, Trifox, Inc., California, USA.
All Rights Reserved Worldwide.
Pinging 'SISQL2017'.
vtxnetd is alive and kicking (1st attempt).
Host process ID : 3808
Requires byte flipping: No
Requires SSL : No
Character set - Client: ASCII
Host : ASCII
Check that you see the "alive and kicking" message.