This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
concepts:01-architecture [2019/11/12 07:20] tjotov [ADUCID architecture] |
concepts:01-architecture [2020/03/25 22:30] (current) mpospisek ↷ Page name changed from concepts:architecture to concepts:01-architecture |
||
---|---|---|---|
Line 5: | Line 5: | ||
This chapter describes internal functionality of ADUCID. | This chapter describes internal functionality of ADUCID. | ||
- | ===== Target application ===== | + | === Server part of ADUCID |
- | + | ||
- | 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® ===== | + | |
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: | ||
- | The server side consists | + | === PEIG - Client part of ADUCID === |
+ | 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. | ||
- | ===== PEIG - Client part of ADUCID ===== | + | With [[nocode:start|No-Code Integration]] all applications are insulated behind AAA Proxy. |
- | + | ||
- | see [[:documentation: | + | |
- | + | ||
===== Interfaces ===== | ===== Interfaces ===== | ||
- | ADUCID uses 4 basic interfaces: | + | ADUCID uses four basic interfaces: |
==== R1 ==== | ==== R1 ==== | ||
Line 63: | 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. | ||
Line 83: | Line 76: | ||
PEIG finishes its activity by using a return URI. Then, depending on scenario, final action is executed (AJAX reload, page refresh, redirect). | PEIG finishes its activity by using a return URI. Then, depending on scenario, final action is executed (AJAX reload, page refresh, redirect). | ||
+ | [<> |