Jump to: navigation, search

Changes


Configure Comos for CUI

153 bytes added, 7 September
= Idea and Concept =
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED -->
The interfacing integration of data {{COMOS}} and {{UBIK}} depends on three key aspects:
* The available data representation structures available in {{COMOS}}* The transfer mechanismused to exchange data between {{COMOS}} and {{UBIK}}, such as an *.xml file for example through XML files or a REST API interface* The processing of How the provided information in transferred data is processed within {{UBIK}}
To transfer the primary information required from {{COMOS}} to {{UBIK}}, only *.xml files can be used. This is because the {{COMOS}} side writes the data to a fixed *.xml schema that {{UBIK}} can read and import.
This process is called metadata transfer. It transfers information about CDevices, Attributes, StandardTables, PhysicalUnits, and DocumentTypes from {{COMOS}} to an *.xml file.
When imported into {{UBIK}} SmartStudio imports this file, it generates the metadata is converted into the corresponding {{UBIK}} structures. These include:* ComosMetaProxies with and their corresponding target MetaClasses, * ComosMetaProxyProperties with and their corresponding target MetaProperties, * SelectiveLists and SelectiveItems, * SIUnits and UnitItems, as well as * ComosDocumentTypeProxies.
For detailed information about the {{UBIK}} MetaClass, please see:
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED -->
For Using or extending the connection between {{COMOS}} and {{UBIK}} via COMOS®-UBIK® Interface (CUI) requires specific configuration information from COMOS®. This information must either be configured on the REST API, please ensure that COMOS Web is installed and that the license "COMOS_Mobile_Worker_Server" is COMOS® side or made available in {{COMOS}}by the COMOS® administrator.
COMOS Web requires the following web services: