This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
concepts:01-architecture [2019/11/12 07:21] tjotov [ADUCID architecture] |
concepts:01-architecture [2020/02/29 11:18] mpospisek [Communication between components] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ==== ADUCID architecture ==== | + | ====== ADUCID architecture |
{{: | {{: | ||
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, | ||
- | |||
- | 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: | ||
=== 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: | See [[components: | ||
- | |||
- | |||
=== PEIG - Client part of ADUCID === | === PEIG - Client part of ADUCID === | ||
Line 24: | Line 14: | ||
See [[components: | See [[components: | ||
+ | === 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, | ||
+ | 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: | ||
===== Interfaces ===== | ===== Interfaces ===== | ||
- | ADUCID uses 4 basic interfaces: | + | ADUCID uses four basic interfaces: |
==== R1 ==== | ==== R1 ==== | ||
Line 61: | Line 56: | ||
{{: | {{: | ||
- | == Communications diagram | + | **Communications diagram** |
The server part of the target application first requests the required operation via the R4 control interface and specifies its AIM parameters. | The server part of the target application first requests the required operation via the R4 control interface and specifies its AIM parameters. |