Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

This page is for developers who want to go more into the details about the internal architecture of the EDMstandaloneClient.

Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'US:_i_EDMstandaloneClientDetails'.

The figure to the left shows the main modules of the EDMsdk. In the following, we will give a brief description of each module. When drawing system diagrams for EDMsix, a simplified block is used to represent the EDMstandaloneClient.

Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'US:_i_EDMstandaloneClientSymbol(200px)'.

The EDMremoteInterface is represented by the four greyed communication ports. TCP/IP, HTTP, LOCAL_DB and LOCAL_CONTEXT

  
The EDMInterface Language Bindings are implemented with the EDMinterface and EDMremoteInterface APIs. The following language bindings are available; C, C++, Java, VisualBasic and .NET
This is the EDMInterface API used for EDMstandaloneClients. 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 ezxtention module EDMvalidateModel is required to run global rule validations on data sets.
The EDMremoteInterface API is available without an EDMsdk license. EDMthinClient applications must use this API to access the TCP and HTTP communication ports. All EDMremoteInterface API functions take the Server Context input parameter to specify the information required to connect to an EDMsixServer. The two ports LOCAL_CONTEXT and LOCAL_DB are only available if you have an EDMsdk license on your system. It is these gates that make it possible to write EDMstandaloneClient applications with the EDMremoteInterface API. The two gates loop every call back to the local EDMdatabase that is opened by the EDMstandaloneClient.
This is the very core of the EDMsix platform of Express Data Manager. It contains the EDM Compilers and debuggers, The STEP and XML import/export modules, the EDMvirtualMachine with EDMmodelConverter, EDMmodelChecker and EDMqueryEngine, the memory manager, the access control system and virtually any other core feature in EDMsix. This is the core component that is included in every EDMsix product.
 

 

 

 

 

 

 

 

 

  • No labels