Difference between revisions of "Configure Comos for CUI"
| Line 1: | Line 1: | ||
[[File:Wiki_Under_Construction_Start.PNG|1000px]]<noinclude> | [[File:Wiki_Under_Construction_Start.PNG|1000px]]<noinclude> | ||
| − | To run or extend the Comos – {{UBIK}} – Interface => CUI you | + | To run or extend the Comos – {{UBIK}} – Interface => CUI you must do some settings on {{Comos}} side or at least get some Data for Configuration from {{Comos}}. |
Because {{Comos}} is not a Product from Augmensys, please request all {{Comos}} changes or adaptions at your local Siemens or Siemens Partner. | Because {{Comos}} is not a Product from Augmensys, please request all {{Comos}} changes or adaptions at your local Siemens or Siemens Partner. | ||
| Line 8: | Line 8: | ||
= Idea and Concept = | = Idea and Concept = | ||
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --> | <!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --> | ||
| − | The Interfacing of Data | + | The Interfacing of Data depends on 3 Parts |
* the possible representation of data from {{Comos}} | * the possible representation of data from {{Comos}} | ||
| Line 14: | Line 14: | ||
* the processing of the given Information in {{UBIK}} | * 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 | + | 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. | This is called Metadata transfer, and hands over data about CDevices, Attributes, StandardTables, PhysicalUnits, and DocumentTypes form Comos to a .xml file. | ||
| − | When {{UBIK}} Smart Studio is | + | When {{UBIK}} Smart Studio is importing this, it will generate ComosMetaProxy's with Traget MetaClasse's, ComosMetaProxyProperty's with Target MetaProperty's, Selective Lists and Items, SI Units and Unit Items, and some ComosDocumentTypeProxy's. |
For detailed Information's about the {{UBIK}} Classes please see | For detailed Information's about the {{UBIK}} Classes please see | ||
Revision as of 08:58, 20 August 2026
To run or extend the Comos – UBIK® – Interface => CUI you must do some settings on Comos side or at least get some Data for Configuration from Comos. Because Comos is not a Product from Augmensys, please request all Comos changes or adaptions at your local Siemens or Siemens Partner.
Idea and Concept
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® Smart Studio is importing this, it will generate ComosMetaProxy's with Traget MetaClasse's, ComosMetaProxyProperty's with Target MetaProperty's, Selective Lists and Items, SI Units and Unit Items, and some ComosDocumentTypeProxy's. For detailed Information's about the UBIK® Classes please see
Comos
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®.
For Interfacing we 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®.
UBIK
See also
For more detailed Information please check you Comos® Documentation for "Guide COMOS Mobile Worker"
Or ask Siemens: comos-mobile-worker
