Configure Comos for CUI

The interfacing of data depends on 3 Parts

• the possible representation of data from Comos
• the transfer media, like *.xml file or REST API Interface
• the processing of the given information in UBIK^®

To hand over the primary needed information from Comos to UBIK^® there are only *.xml files to use, cause the Comos side is writing a the data to a fixed *.xml scheme witch UBIK^® is able to read in. This is called Metadata transfer, and hands over data about CDevices, Attributes, StandardTables, PhysicalUnits, and DocumentTypes form Comos to a .xml file. When UBIK^® SmartStudio is importing this, it will generate ComosMetaProxy's with Traget MetaClasse's, ComosMetaProxyProperty's with Target MetaProperty's, SelectiveLists and SelectiveItems, SIUnits and UnitItems, and some ComosDocumentTypeProxy's. For detailed information's about the UBIK^® Metaclasses please see

• MetaProxy
• MetaClass
• SELECTIVELIST
• SELECTIVEITEM
• UNIT

For connection between Comos® and UBIK® via REST API please make sure that Comos-WEB is installed and the License called “COMOS_Mobile_Worker_Server” is available on Comos®.

Comos-WEB will need The ComosEvents, ComosGatewayServices and the ComosWebStartPage.

In the Comos® project settings in the section: "Mobile Solutions" you have to care about that URL to you ComosWebStartPage (including port) is set and also the Comos-Web database key is set.

NOTE: on One Domain the database key has to be Unique!

Also in the project settings in the section: "COMOS Mobile Worker Interface" you will find the setting and the values for the active "Comos Project" and if the "Workinglayer" key is empty the released area is connected if not one Workinglayer per project can be connected to UBIK®.

Set Up CUI Rest API