To display a live CitectSCADA project in an Internet browser, you need to combine the content of the project pages and the current data these pages present using standard, Web-based communication protocols. To understand the communication architecture for the CitectSCADA Web Client, it's easiest to consider the role each of the following components play in achieving this outcome:
The following diagram shows how these components interact.
CitectSCADA Web Client communications architecture.
Once the Web Client has connected to the Runtime servers, steps 2 and 3 become an ongoing process, with the necessary content being called upon as the user navigates the project pages.
The citect.ini file settings used by a Web Client are taken from the citect.ini file on the Web Server at the time of connection.
This diagram has the system components set up on different computers purely for the sake of explaining the communications model. In reality, the flexibility of the architecture allows these components to be distributed in any necessary arrangement; they can even share a common location.