Difference between revisions of "Configure Comos for CUI"
| (One intermediate revision by the same user not shown) | |||
| 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 | + | To run or extend the COMOS®-UBIK® Interface (CUI), you must configure certain settings on the {{COMOS}} side or, at a minimum, obtain configuration data from {{COMOS}}. |
As {{COMOS}} is not an Augmensys product, please contact your local Siemens representative or Siemens partner for any {{COMOS}} changes or adaptations. | As {{COMOS}} is not an Augmensys product, please contact your local Siemens representative or Siemens partner for any {{COMOS}} changes or adaptations. | ||
| Line 9: | Line 9: | ||
= 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 | + | The integration of {{COMOS}} and {{UBIK}} depends on three key aspects: |
| − | * The | + | * The data structures available in {{COMOS}} |
| − | * The | + | * The mechanism used to exchange data between {{COMOS}} and {{UBIK}}, for example through XML files or a REST API |
| − | * | + | * How the 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. | 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. | ||
| Line 19: | Line 19: | ||
This process is called metadata transfer. It transfers information about CDevices, Attributes, StandardTables, PhysicalUnits, and DocumentTypes from {{COMOS}} to an *.xml file. | This process is called metadata transfer. It transfers information about CDevices, Attributes, StandardTables, PhysicalUnits, and DocumentTypes from {{COMOS}} to an *.xml file. | ||
| − | When {{UBIK}} SmartStudio | + | When imported into {{UBIK}} SmartStudio, the metadata is converted into the corresponding {{UBIK}} structures. These include: |
| + | * ComosMetaProxies and their corresponding MetaClasses | ||
| + | * ComosMetaProxyProperties and their corresponding MetaProperties | ||
| + | * SelectiveLists and SelectiveItems | ||
| + | * SIUnits and UnitItems | ||
| + | * ComosDocumentTypeProxies | ||
For detailed information about the {{UBIK}} MetaClass, please see: | For detailed information about the {{UBIK}} MetaClass, please see: | ||
| Line 33: | Line 38: | ||
<!-- 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 --> | ||
| − | + | Using or extending the COMOS®-UBIK® Interface (CUI) requires specific configuration information from COMOS®. This information must either be configured on the COMOS® side or made available by the COMOS® administrator. | |
COMOS Web requires the following web services: | COMOS Web requires the following web services: | ||
Latest revision as of 14:31, 7 September 2026
To run or extend the COMOS®-UBIK® Interface (CUI), you must configure certain settings on the COMOS® side or, at a minimum, obtain configuration data from COMOS®.
As COMOS® is not an Augmensys product, please contact your local Siemens representative or Siemens partner for any COMOS® changes or adaptations.
Idea and Concept
The integration of COMOS® and UBIK® depends on three key aspects:
- The data structures available in COMOS®
- The mechanism used to exchange data between COMOS® and UBIK®, for example through XML files or a REST API
- How the 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, the metadata is converted into the corresponding UBIK® structures. These include:
- ComosMetaProxies and their corresponding MetaClasses
- ComosMetaProxyProperties and their corresponding MetaProperties
- SelectiveLists and SelectiveItems
- SIUnits and UnitItems
- ComosDocumentTypeProxies
For detailed information about the UBIK® MetaClass, please see:
Comos
Using or extending the COMOS®-UBIK® Interface (CUI) requires specific configuration information from COMOS®. This information must either be configured on the COMOS® side or made available by the COMOS® administrator.
COMOS Web requires the following web services:
- ComosEvents
- ComosGatewayServices
- ComosWebStartPage
In the COMOS® project settings, under the "Mobile Solutions" section, ensure that the URL of your ComosWebStartPage (including the port number) is configured correctly. Also, make sure that the COMOS Web database key is configured.
Note: Within a single domain, the database key must be unique.
In the "COMOS Mobile Worker Interface" section of the project settings, you will find the configuration values for the active COMOS project. If the WorkingLayer key is empty, the released area is connected. Otherwise, a specific WorkingLayer can be connected to UBIK® for each project.
UBIK
See also
For more detailed information please check your COMOS® documentation for "Guide COMOS Mobile Worker"
or ask Siemens: comos-mobile-worker
