Jump to: navigation, search

Difference between revisions of "Configure Comos for CUI"


 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
To run or extend the Comos – {{UBIK}} – Interface => CUI you have to do some settings on {{Comos}} side or at least get some Data for Configuration from {{Comos}}.
+
[[File:Wiki_Under_Construction_Start.PNG|1000px]]<noinclude>
 +
 
 +
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 6: 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 is depending on 3 Parts
+
The interfacing of data depends on 3 Parts
  
 
* the possible representation of data from {{Comos}}
 
* the possible representation of data from {{Comos}}
 
* the transfer media, like *.xml file or REST API Interface
 
* the transfer media, like *.xml file or REST API Interface
* 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 Data to a fixed *.xml scheme witch {{UBIK}} is able to read in.
+
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 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
+
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}} Classes please see
+
For detailed information's about the {{UBIK}} Metaclasses please see
  
 
* [[MetaProxy]]
 
* [[MetaProxy]]
Line 26: Line 28:
 
<!-- 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 -->
  
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 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.
+
Comos-WEB will need The ComosEvents, ComosGatewayServices and the ComosWebStartPage.
  
 
[[File:Screenshot 2026-08-13 091304.png]]
 
[[File:Screenshot 2026-08-13 091304.png]]
  
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.
+
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.
  
 
[[File:Screenshot 2026-08-13 093803.png]]
 
[[File:Screenshot 2026-08-13 093803.png]]
Line 38: Line 40:
 
NOTE: on One Domain the database key has to be Unique!
 
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®.
+
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®.
  
 
[[File:Screenshot 2026-08-13 094922.png|1000px]]
 
[[File:Screenshot 2026-08-13 094922.png|1000px]]
Line 52: Line 54:
 
<!-- 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 -->
  
For more detailed Information please check you Comos® Documentation for "Guide COMOS Mobile Worker"
+
For more detailed information please check you Comos® documentation for "Guide COMOS Mobile Worker"
  
Or ask Siemens: [https://www.siemens.com/en-us/products/comos/mobile-worker/ comos-mobile-worker]
+
or ask Siemens: [https://www.siemens.com/en-us/products/comos/mobile-worker/ comos-mobile-worker]

Latest revision as of 09:04, 20 August 2026

Wiki Under Construction Start.PNG

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.


[edit]

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® 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

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®.

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

Screenshot 2026-08-13 091304.png

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.

Screenshot 2026-08-13 093803.png

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®.

Screenshot 2026-08-13 094922.png

See also

For more detailed information please check you Comos® documentation for "Guide COMOS Mobile Worker"

or ask Siemens: comos-mobile-worker