Unlike EDMthinClients, the EDMfatClient maintains a stateful connection with the EDMsixServer. It performs its operations with a local partial working copy of the EDMsixServer EDMdatabase.
Section |
---|
Column |
---|
| Insert excerpt |
---|
| US:_i_EDMfatClientDetails(250px) |
---|
| US:_i_EDMfatClientDetails(250px) |
---|
nopanel | true |
---|
|
|
Column |
---|
The figure to the left shows the main modules of the EDMfatClient. In the following, we will give a brief description of each module. Section |
---|
Column |
---|
| When drawing system diagrams for EDMsix, a simplified block is used to represent the EDMfatClient., Insert excerpt |
---|
| US:_i_EDMfatClientSymbol(170px) |
---|
| US:_i_EDMfatClientSymbol(170px) |
---|
nopanel | true |
---|
|
|
Column |
---|
and when connected to the EDMsixServer Insert excerpt |
---|
| US:_i_EDMfatClientServer(170px) |
---|
| US:_i_EDMfatClientServer(170px) |
---|
nopanel | true |
---|
|
|
|
|
|
...
Section |
---|
Column |
---|
|
|
Column |
---|
This is the The EDMInterface API is used for EDMfatClients. The API is written in C, and all the EDMInterface API function signatures are declared in the sdai.h header file. The EDMInterface API requires an EDMsdk license. Some of these EDMInterface API functions are only available when activated by your license key. E.g, you need to have the EDMsdk Advanced to compile EDMmethod schemas and the licensed extension module EDMmodelChecker is required to run global rule validations on data sets. The EDMInterface Language Bindings are mainly using the EDMremoteInterface API and cannot be used for writing EDMfatClients. EDMfatClients must therefore be written with the EDMinterface C/C++ API.
|
|
...
Section |
---|
Column |
---|
|
|
Column |
---|
EDMfatClients maintain a local partial copy of the EDMdatabase in its cache memory. The size of this DB cache is configurable can configured with the configuration parameter EDM_CLIENT_MEMORY_BLOCKS and may have great effect on the performance. |
|