System overview: xfNetLink .NET
Figure 1 shows the primary components of a distributed application that accesses Synergy code from a .NET client. The diagram describes two machines:
- A client machine running xfNetLink .NET, the .NET Framework, and an application that uses a Synergy assembly. If you’re developing a two‑tier system with a Windows client application, the client is the end‑user’s machine. If you’re developing a three‑tier system with a web client application, the client is the web server machine.
- A Synergy server running xfServerPlus, which handles the remote execution of Synergy routines. The routines are made available for remote execution by including them in an ELB or shared image and defining them in the Synergy Method Catalog (SMC), also located on the server machine. You can populate the SMC with routine information by entering it manually through the Method Definition Utility or by attributing your code, running dbl2xml to create an XML file, and then loading that file into the SMC. You may use multiple servers; each machine requires an xfServerPlus license.
1. Accessing Synergy from .NET.
xfNetLink .NET enables you to use your existing Synergy code without rewriting it, provided that the code is already written in the form of an external subroutine or function. If any of the routines require input from or send messages to the user, or if they might generate untrapped errors, they must be adjusted to work as server‑level logic.