This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
documentation:architecture [2018/06/26 14:00] tjotov |
documentation:architecture [2018/06/26 14:03] tjotov |
||
---|---|---|---|
Line 61: | Line 61: | ||
* Integrated using PEIG API | * Integrated using PEIG API | ||
* Low level R2 is implemented as UNIX Socket or Windows Pipe | * Low level R2 is implemented as UNIX Socket or Windows Pipe | ||
+ | |||
+ | On Windows and OS X PEIG R2 can be called using auxiliary application PEIG which acceps RUI as an arguments and sends it via Unix socket / Windows pipe | ||
==== R3 ==== | ==== R3 ==== | ||
Line 70: | Line 72: | ||
R4 is interface between server application and AIM. Like R3 it uses http (or https) transport and SOAP protocol. | R4 is interface between server application and AIM. Like R3 it uses http (or https) transport and SOAP protocol. | ||
- | R4 is “a low level” layer. It is encapsulated in ADUCID WEB SDK or ADUCID | + | R4 is “a low level” layer. It is encapsulated in ADUCID WEB Platform |
- | + | ||
- | + | ||
- | + | ||
- | ==== R2 ==== | + | |
- | + | ||
- | R2 is an interface between client application and PEIG. This communication can be handled via: | + | |
- | + | ||
- | * Uri scheme on mobile phones scheme **aducid** | + | |
- | * Redirect adapter (from browser to Windows / OSX PEIG) is local port 44240 | + | |
- | * Scanning a QR code | + | |
- | * <font 11.0pt/ | + | |
- | ==== R3 ==== | + | |
- | + | ||
- | R3 is an internal interface between PEIG and AIM which uses http transport and SOAP protocol. | + | |
- | + | ||
- | ==== R4 ==== | + | |
- | + | ||
- | R4 is interface between server application and AIM. Like R3 it uses http (or https) transport and SOAP protocol. | + | |
- | R4 is “a low level” layer. It is encapsulated in ADUCID WEB SDK or ADUCID JAVA SDK for simplified integration. | ||
===== Communication between components ===== | ===== Communication between components ===== |