Runtime Client-Server Domains (Reference): Understanding the client-server architecture and domain separation in FrameworX runtime execution.
FrameworX uses a client-server architecture that clearly separates server-side processes (data acquisition, alarms, historian) from client-side processes (displays, local scripts). This separation enables:
- Distributed application deployment
- Optimized performance through appropriate process allocation
- Secure data access with proper isolation
- Flexible scaling of client connections
On this page:
Using Reports from Server and Client Processes
The Report Module follows a logic similar to Datasets that are accessible from both the Server and Client processes, which resolve the tag values according to where they were activated and have an asynchronous operation that always runs on the server side.
When calling a method, such as the SaveCommand(), the method is executed by the entity that calls it. Therefore, if the call is from a Display or ScriptTask of the Client type, it will be executed and evaluated on the client side. If it is from a Script-Server, it will be evaluated on the server computer.
Saving files will always occur on the server computer, and the filename path will always be resolved on the server side, even if the command to save was initiated from the client computer.
The Report module also allows a command to be executed asynchronously on the server computer. Asynchronous calls are always executed on the server computer. In order to start an asynchronous action, you need to toggle (change) the value of the property. Here are the two options compared:
@Report.Report1.SaveCommand(): Will run synchronously, on the server or client domain, using the tags according to where they were called.
@Report.Report1.Save += 1: Will run asynchronously, always on the server computer.
You can start an asynchronous call to save a report using the SaveTrigger column and mapping it to a tag.
When configuring the Report module: If you use local tags or symbols mapping to local tags, you must call the queries from the CLIENT process using the synchronous method so the system will be able to do the proper evaluations of those tags.
In this section...