Architecture Basics The following diagram displays how CS Works
component interact with each other.
Browser Any web
browser that supports Microsoft Silverlight. The number of browser clients
connected to CS Works data web services is limited only by network
bandwidth, web server capabilities (more
about web farm) and server capabilities (more
about partitioning).
Silverlight Runtime
Microsoft Silverlight framework that runs user application. A single
browser instance can host multiple instances of Silverlight runtime
engines.
User Silverlight Application
Silverlight application created by application developer.
Silverlight Controls Standard Silverlight
controls (TextBox, Grid etc) that visualize data received from CS Works
Data Access Framework.
CS Works Controls CS
Works controls (Numeric inputs etc) that visualize data received from Data
Access Framework.
Custom Control Custom/Third
party UI elements that visualize data received from Data Access Framework
or communicate directly to CS Works web services (including custom data
services).
Server Server machine that runs CS
Works server comonents. There can be one or multiple server machines in
the deployment (more
about web farm, redundancy and partitioning).
Web
Services (LiveData + Alarms + HistoricalData) CS Works web
services that provide access to LiveData, Alarms and HistoricalData
supplied by CS Works data servers. This layer has multiplexing
capabilities and can communicate to multiple instances of underlying
servers running on multiple server machines (more about redundancy
and partitioning).
Custom Data Web Services Custom/Third party
web services that provide access to arbitrary data streams supplied by CS
Works data servers or any custom data processing modules.
Custom Data Processing Module Custom/Third
party component that processes data it gets from CS Works data servers.
CS Works Data Servers CS Works components
that process data they acquire through data source providers and provide
it as live, alarm and historical data streams.
Alarm
Server CS Works component that receives data updates from
LiveData server and implements alarm subsystem.
Historian CS Works component that receives
data updates from LiveData server for specific data points, stores it as
historical data and provides access to it.
LiveData
Server CS Works component that receives near real-time data
updates from data sources, and provides access to it.
OPC
Data Source Provider CS Works component that subscribes to
data updates from specified OPC servers.
SQL Data Source
Provider CS Works component that monitors data changes in the
specific SQL databases.
Custom Data Source
Provider Custom/Third party component that monitors data
changes in an arbitrary data source. This is one of the simplest examples of CS Works
server topology - with all server components running on the same machine.
Fortunately, running different CS Works server components on different
machines is not a problem: CS Works server components communicate to each
other using Windows Communication Foundation (WCF), which makes building a
distributed system easy. Please see Distributed
Architecture section for details. |