Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
concepts:architecture [2019/11/12 07:21]
tjotov [ADUCID architecture]
concepts:architecture [2019/11/12 07:22] (current)
tjotov [Target application]
Line 4: Line 4:
  
 This chapter describes internal functionality of ADUCID. This chapter describes internal functionality of ADUCID.
- 
-===== Target application ===== 
- 
-Target application is any application that uses ADUCID® services. Examples of such applications include web applications with standard thin client (standard browser), mobile applications with server counterpart,​ classic client-server applications,​ or even universal system tools which are not normally viewed as applications,​ e.g. a VPN system for remote access, Wi-Fi connection, terminal access (e.g. X terminal), etc. 
- 
-From the system point of view, the application consists of a client part and a server part (TA Client and TA Server), which communicate with each other in their own manner via an R1 interface. 
- 
-With [[nocode:​start|No-Code Integration]] all applications are insulated behind AAA Proxy. 
  
 === Server part of ADUCID === === Server part of ADUCID ===
Line 17: Line 9:
 The entire server part along with the operating system and all third-party systems required to operate the server part of ADUCID are supplied as complete virtual appliance but can be installed as a set of components. The entire server part along with the operating system and all third-party systems required to operate the server part of ADUCID are supplied as complete virtual appliance but can be installed as a set of components.
 See [[components:​aim|AIM - ADUCID Server Side Components]] See [[components:​aim|AIM - ADUCID Server Side Components]]
- 
- 
  
 === PEIG  - Client part of ADUCID === === PEIG  - Client part of ADUCID ===
Line 24: Line 14:
 See [[components:​client|PEIG - Client software]] See [[components:​client|PEIG - Client software]]
  
 +=== Target application ===
 +Target application is any application that uses ADUCID® services. Examples of such applications include web applications with standard thin client (standard browser), mobile applications with server counterpart,​ classic client-server applications,​ or even universal system tools which are not normally viewed as applications,​ e.g. a VPN system for remote access, Wi-Fi connection, terminal access (e.g. X terminal), etc.
  
 +From the system point of view, the application consists of a client part and a server part (TA Client and TA Server), which communicate with each other in their own manner via an R1 interface.
 +
 +With [[nocode:​start|No-Code Integration]] all applications are insulated behind AAA Proxy.
 ===== Interfaces ===== ===== Interfaces =====
  
  • concepts/architecture.txt
  • Last modified: 2019/11/12 07:22
  • by tjotov