concepts:01-architecture
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Next revision Both sides next revision | ||
|
concepts:01-architecture [2019/08/01 09:39] tjotov created |
concepts:01-architecture [2019/11/12 07:21] tjotov [ADUCID architecture] |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| {{: | {{: | ||
| - | This chapter describes internal functionality of ADUCID. | + | This chapter describes internal functionality of ADUCID. |
| ===== Target application ===== | ===== Target application ===== | ||
| Line 11: | Line 11: | ||
| 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. | 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 [[integration:start|No-code integration]] all applications are insulated behind AAA Proxy. | + | With [[nocode:start|No-Code Integration]] all applications are insulated behind AAA Proxy. |
| - | ===== Server part of ADUCID® ===== | + | === 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 of these parts: | ||
| - | ==== AIM ==== | ||
| - | ADUCID< | ||
| - | AIM is controlled by the target application using the R4 interface. Using this interface, it also provides services for working with user data. | + | === PEIG - Client part of ADUCID === |
| - | Using the R3 interface, it communicates with the client part of ADUCID< | + | See [[components:client|PEIG - Client |
| - | + | ||
| - | + | ||
| - | ==== SQL database ==== | + | |
| - | SQL database is used to store ADUCID identites, events and licensing logs. The default SQL DB is PostgreSQL but can be replaced with any JPA compatible DB. | + | |
| - | + | ||
| - | ==== Admin applications ==== | + | |
| - | + | ||
| - | See [[documentation:admin-applications|Admin applications]] | + | |
| - | + | ||
| - | + | ||
| - | ==== Proofing applications ==== | + | |
| - | + | ||
| - | See [[documentation: | + | |
| - | + | ||
| - | + | ||
| - | ===== PEIG - Client | + | |
| - | + | ||
| - | see [[: | + | |
concepts/01-architecture.txt · Last modified: 2020/03/25 22:30 by mpospisek
Page Tools
