This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
en:architecture [24.09.2015 11:38] ph@cesnet.cz |
en:architecture [09.11.2016 15:48] ph@cesnet.cz fixed banner url |
||
---|---|---|---|
Line 4: | Line 4: | ||
Each entity/network that wishes to feed data into the WARDEN system should have a so called //**sending client**//. Each entity/network that wishes to receive data from the WARDEN system should have a so called //**receiving**// client. The server (the centre) ensures the data reception and storage as well as the interface for the access to data stored. Data which the clients send into the centre will be referred to as //**events**//. Events are sent by the clients after authentication; the access to the centre is also authenticated. X.509 is used for the authentication. | Each entity/network that wishes to feed data into the WARDEN system should have a so called //**sending client**//. Each entity/network that wishes to receive data from the WARDEN system should have a so called //**receiving**// client. The server (the centre) ensures the data reception and storage as well as the interface for the access to data stored. Data which the clients send into the centre will be referred to as //**events**//. Events are sent by the clients after authentication; the access to the centre is also authenticated. X.509 is used for the authentication. | ||
+ | |||
+ | ===== System architecture ===== | ||
+ | |||
+ | {{:cs:warden-l.png?nolink&800|Architektura systému Warden}} | ||
+ | |||
+ | |||
+ | ===== Server status ===== | ||
+ | |||
+ | {{https://warden-ra.cesnet.cz/banner/banner-en.svg?680x540}} | ||
===== Sending events ===== | ===== Sending events ===== |