UBIK Wiki / Augmensys - User contributions [en]

Configure Comos for CUI

2026-08-20T09:04:18Z

FMW:

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

{{Template:HowTo/Begin}}

= 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

* [[MetaProxy]]
* [[MetaClass]]
* [[SELECTIVELIST]]
* [[SELECTIVEITEM]]
* [[UNIT]]

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

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

[[File: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®.

[[File:Screenshot 2026-08-13 094922.png|1000px]]

= UBIK =


[[HowTo:Set_Up_CUI_Rest_API]]

{{Template:HowTo/End}}

==See also==


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]

Configure Comos for CUI

2026-08-20T08:58:57Z

FMW:

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

{{Template:HowTo/Begin}}

= 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

* [[MetaProxy]]
* [[MetaClass]]
* [[SELECTIVELIST]]
* [[SELECTIVEITEM]]
* [[UNIT]]

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

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

[[File: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®.

[[File:Screenshot 2026-08-13 094922.png|1000px]]

= UBIK =


[[HowTo:Set_Up_CUI_Rest_API]]

{{Template:HowTo/End}}

==See also==


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]

Configure Comos for CUI

2026-08-20T08:55:16Z

FMW:

[[File:Wiki_Under_Construction_Start.PNG|1000px]]<noinclude>

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}}.
Because {{Comos}} is not a Product from Augmensys, please request all {{Comos}} changes or adaptions at your local Siemens or Siemens Partner.

{{Template:HowTo/Begin}}

= Idea and Concept =

The Interfacing of Data is depending 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

* [[MetaProxy]]
* [[MetaClass]]
* [[SELECTIVELIST]]
* [[SELECTIVEITEM]]
* [[UNIT]]

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

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

[[File: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®.

[[File:Screenshot 2026-08-13 094922.png|1000px]]

= UBIK =


[[HowTo:Set_Up_CUI_Rest_API]]

{{Template:HowTo/End}}

==See also==


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]

Configure Comos for CUI

2026-08-13T09:56:59Z

FMW:

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}}.
Because {{Comos}} is not a Product from Augmensys, please request all {{Comos}} changes or adaptions at your local Siemens or Siemens Partner.

{{Template:HowTo/Begin}}

= Idea and Concept =

The Interfacing of Data is depending 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

* [[MetaProxy]]
* [[MetaClass]]
* [[SELECTIVELIST]]
* [[SELECTIVEITEM]]
* [[UNIT]]

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

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

[[File: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®.

[[File:Screenshot 2026-08-13 094922.png|1000px]]

= UBIK =


[[HowTo:Set_Up_CUI_Rest_API]]

{{Template:HowTo/End}}

==See also==


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]

Configure Enterprise Service for CUI

2026-08-13T08:11:21Z

FMW:

== '''UBIK Notification Processing System''''' ==

The UBIK Notification Processing System is a WebEndoint and configurable Enterprise service that imports Notifications into the UBIK database, and hand them over to processing. It requires specific configuration files and settings to function efficiently.

== Set up UBIK WEB Service first ==

* [[HowTo:Install UBIK Web Service|Install {{UBIK}} Web Service]]
* [[HowTo:Install Microsoft IIS]]
* [[HowTo:Configure Microsoft IIS for UBIK]]
* [[Configure_UBIK_Archon_Service]]

== Example Configuration 3 Enterprise Services : ==

1st the Enterprise Service for Notifications like defined

* [[Configure_EventNotification_Endpoint_and_Enterprise_Service_for_CUI]]

2nd the Enterprise Service for Import

* [[Configure_Enterprise_Service_for_Import]]
* [[EventNotificationScanOrchestrator]]

3rd the Enterprise Service for Export

* [[Configure_Enterprise_Service_for_Export]]
* [[BatchWriteOrchestrator]]

No requirement for HTTPS or separate ports if both the UBIK Notification Endpoint and the Comos EventService are hosted locally

[[Category:Pages with broken file links|Configure Enterprise Service for CUI]]

Setting Up UBIK for CUI

2026-08-13T08:10:27Z

FMW:

Setting uo a UBIK Database fur CUI Data exchange
{{Template:HowTo/Begin}}

= Instructions =

To set up Interfacing on UBIK Database you need Configurations \ Objects

* Comos Project
* Comos Login
* Interface Admin Comos
* Relation between Comos Project and Language

= Comos Project =


Best approach is to go to Meta Class COMOS_PROJECT and derive a new Metaclass.
Reason is to get a Meta class that is cut off from this SystemMetaClass, witch could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> COMOS_PROJECT

Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface ->COMOS_PROJECT

[[File:ComosProject_see_all.png|400px]][[File:ComosProject_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Describe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

The Database ID is also the same as in Comos, on the Project settings for Mobile Solutions, the Enterprise Server here is that one from {{UBIK}} like you set up the Notification Endpoint.
Project_ID, Working_Overlay_ID is again form Comos, Project_ID is Mandatory anyway, if you want to connect with an WorkingOverly from Comos this ID is also needed.
The Registration folder is only needet when you want to use XML Files for Objects that are not Classified in Comos.

[[File:New_Project_MC.png|400px]]
[[File:New_comos_project.png|400px]]

= Comos Login =


Similar to COMOS_PROJECT go to MetaClass COMOS_LOGIN and derive a new Metaclass.

Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> SERVICE_LOGIN -> BASICAUTH_SERVICE_LOGIN -> COMOS_LOGIN

Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> COMOS_LOGIN

[[File:ComosLogin_see_all.png|400px]][[File:ComosLogin_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Descripe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

You have to Link a instance form COMOS_PROJECT or its children, so link here the Instance you created bevor in the new Created COMOS_PROJECT Childclass
with the checkbox you ask UBIK to Authenticate before sending data, could be that System security is asking for this.
In Service URL you have to give the Comos WebstartPage url, and User and Password for Comos login (mostly Domain user)

[[File:New_login_MC.png|400px]]
[[File:New_Login.png|400px]]

= Interface Admin Comos =


Similar like before go to MetaClass INTERFACE_ADMIN_COMOS and derive a new Metaclass.

Reason is to get a Metaclass that is cut off from this SystemMetaClass, witch could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> INTERFACE_ADMIN_ROOT -> INTERFACE_ADMIN_COMOS

Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> {}Comos.Interface.Administration -> INTERFACE_ADMIN_COMOS

[[File:IA_COMOS_see_all.png|400px]][[File:IA_COMOS_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, don't forget to link to the Login Object please Save;

[[File:IA_CMW_LINK.png|400px]]

To Configure the Proxys that should be Imported and Exported please open the New InterfaceAdmin in a RelationEditor. Than drag an drop all the relevant Proxy to the Interface admin Object.

[[File:IA_RELATIONS.png|800px]]

= Relation between Comos Project and Language =


Different to bevore RelationalClass SYSREL_PROJECT_LANGUAGE stays the SystemMetaClass.

To find the MetaClass in {{UBIK}} See all goto -> RELATIONDATA -> SYSREL_PROJECT_LANGUAGE

Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> SYSREL_PROJECT_LANGUAGE

[[File:Lang_REL_see_all.png|400px]][[File:Lang_REL_ContentView.png|400px]]

Please open the Class in a Bulk Editor;

[[File:REL_OVERVIEW.png|1200px]]

To Create a new Instance set a Comos_Project Instance to LEFTUID and a Language Object to the RIGHTUID.

Add the Microsoft LCID number for your Language.

And also the Comos settings witch Language is the current Project, and User Default.

The Languages from UBIK u find in

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> INTERFACE_ADMIN_ROOT -> INTERFACE_ADMIN_COMOS

Or on Content View you find it below Namespaces; goto -> {}System -> {}System.Main -> {}System.Main.Language -> LANGUAGE -> {}System

{{Template:HowTo/End}}

==See also==


[[Add_Languages_to_UBIK]]

[https://cldr.unicode.org/ Unicode CLDR Project]

[https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-lcid/70feba9f-294e-491e-b6eb-56532684c37f Microsoft LCID]

HowTo:Set Up CUI Rest API

2026-08-13T08:08:13Z

FMW:

==Overview==
The CUI -> "{{Comos}} {{UBIK}} Interface" is a Standard Data exchange function between the tow Systems {{Comos}} and {{UBIK}} it is a bidirectional Communication based on Comos WEB Rest API and a UBIK CUI Plugin.

For Comos make sure you have a working Installation of {{Comos}} and {{Comos Web}} with access to its {{Comos}} Database, you also need the License called “COMOS_Mobile_Worker_Server”

On UBIK side to set it up please start with the Installation of UBIK, UBIK Database and its Web services and Enterprise Server(s)

* [[HowTo:Install_UBIK_Studio]]
* [[HowTo:Install_UBIK_Database]]
* [[HowTo:Install_UBIK_Web_Service]]
* [[Configure_Enterprise_Service_for_CUI]]

After that you have to possible ways to go on, Create a {{UBIK}} MetaClass struct manually or via Import from {{Comos}}.

If you want to export from {{Comos}} the first step is to check, update or Create Templates, like in this description PDF:

[[:File:Admin_Comos_UBIK_Interface_2025_10_EN.pdf]]

After Template Structure in {{Comos}} includes all the MetaClasses and Properties that you need on UBIK side, export these {{Comos}} Template as Meta information for UBIK:

In Standard Comos iDB there is a new Module section M67 for Comos Mobile Worker (UBIK)
For a standard MRO Use case there are Templates Predefined, these Templates are connected to Comos CDevices that have the Functional Classification C270 (iDB) (for cDB there is a C2 Classification available).
Bevor, please make sure that the Project settings for CUI Interface are there and Active; you find them in Project settings an make sure that the Active checkbox on COMOS Mobile Worker Interface is checked.

First make sure the Interface is "Active" in Project settings of SO1 (or your used Workinglayer)

[[File:Project_activation.png|400px]]

Next is to oben the ComosBaseObject in SO1, it should be found in iDB Databases at "@30|M67|A50|A20|A10", please make sure that the file path for the xml is existing and accessible.

[[File:Export_from_Comos.png|400px]]

To import in a UBIK Database you have to use {{UBIK}} Smart Studio [[Smart_Studio]]

* [[Smart_Modelling]]

* [[Setting_Up_UBIK_for_CUI]]

Configure Comos for CUI

2026-08-13T08:05:25Z

FMW: /* UBIK */

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.
Because {{Comos}} is not a Product from Augmensys, please request all Comos changes or adaptions at your local Simens or Siemens Parter.

{{Template:HowTo/Begin}}

= Idea and Concept =

The Interfaceing of Data is depending 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 shema 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}} Smar 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 UnitItems, and some ComosDocumentTypeProxy's
For detailed Informations about the {{UBIK}} Classes please see

* [[MetaProxy]]
* [[MetaClass]]
* [[SELECTIVELIST]]
* [[SELECTIVEITEM]]
* [[UNIT]]

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

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

[[File: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®.

[[File:Screenshot 2026-08-13 094922.png|1000px]]

= UBIK =


[[HowTo:Set_Up_CUI_Rest_API]]

{{Template:HowTo/End}}

==See also==


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]

Configure Comos for CUI

2026-08-13T08:03:26Z

FMW: /* See also */

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.
Because {{Comos}} is not a Product from Augmensys, please request all Comos changes or adaptions at your local Simens or Siemens Parter.

{{Template:HowTo/Begin}}

= Idea and Concept =

The Interfaceing of Data is depending 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 shema 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}} Smar 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 UnitItems, and some ComosDocumentTypeProxy's
For detailed Informations about the {{UBIK}} Classes please see

* [[MetaProxy]]
* [[MetaClass]]
* [[SELECTIVELIST]]
* [[SELECTIVEITEM]]
* [[UNIT]]

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

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

[[File: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®.

[[File:Screenshot 2026-08-13 094922.png|1000px]]

= UBIK =

<Give step-by-step instructions, use images, ...>

{{Template:HowTo/End}}

==See also==


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]

Configure Comos for CUI

2026-08-13T08:03:03Z

FMW: /* See also */

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.
Because {{Comos}} is not a Product from Augmensys, please request all Comos changes or adaptions at your local Simens or Siemens Parter.

{{Template:HowTo/Begin}}

= Idea and Concept =

The Interfaceing of Data is depending 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 shema 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}} Smar 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 UnitItems, and some ComosDocumentTypeProxy's
For detailed Informations about the {{UBIK}} Classes please see

* [[MetaProxy]]
* [[MetaClass]]
* [[SELECTIVELIST]]
* [[SELECTIVEITEM]]
* [[UNIT]]

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

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

[[File: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®.

[[File:Screenshot 2026-08-13 094922.png|1000px]]

= UBIK =

<Give step-by-step instructions, use images, ...>

{{Template:HowTo/End}}

==See also==


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]

Configure Comos for CUI

2026-08-13T08:02:19Z

FMW: /* See also */

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.
Because {{Comos}} is not a Product from Augmensys, please request all Comos changes or adaptions at your local Simens or Siemens Parter.

{{Template:HowTo/Begin}}

= Idea and Concept =

The Interfaceing of Data is depending 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 shema 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}} Smar 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 UnitItems, and some ComosDocumentTypeProxy's
For detailed Informations about the {{UBIK}} Classes please see

* [[MetaProxy]]
* [[MetaClass]]
* [[SELECTIVELIST]]
* [[SELECTIVEITEM]]
* [[UNIT]]

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

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

[[File: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®.

[[File:Screenshot 2026-08-13 094922.png|1000px]]

= UBIK =

<Give step-by-step instructions, use images, ...>

{{Template:HowTo/End}}

==See also==


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/]

Configure Comos for CUI

2026-08-13T07:54:25Z

FMW:

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.
Because {{Comos}} is not a Product from Augmensys, please request all Comos changes or adaptions at your local Simens or Siemens Parter.

{{Template:HowTo/Begin}}

= Idea and Concept =

The Interfaceing of Data is depending 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 shema 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}} Smar 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 UnitItems, and some ComosDocumentTypeProxy's
For detailed Informations about the {{UBIK}} Classes please see

* [[MetaProxy]]
* [[MetaClass]]
* [[SELECTIVELIST]]
* [[SELECTIVEITEM]]
* [[UNIT]]

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

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

[[File: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®.

[[File:Screenshot 2026-08-13 094922.png|1000px]]

= UBIK =

<Give step-by-step instructions, use images, ...>

{{Template:HowTo/End}}

==See also==

Configure Comos for CUI

2026-08-13T07:54:08Z

FMW:

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.
Because {{Comos}} is not a Product from Augmensys, please request all Comos changes or adaptions at your local Simens or Siemens Parter.

{{Template:HowTo/Begin}}

= Idea and Concept =

The Interfaceing of Data is depending 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 shema 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}} Smar 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 UnitItems, and some ComosDocumentTypeProxy's
For detailed Informations about the {{UBIK}} Classes please see

* [[MetaProxy]]
* [[MetaClass]]
* [[SELECTIVELIST]]
* [[SELECTIVEITEM]]
* [[UNIT]]

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

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

[[File: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®.

[[File:Screenshot 2026-08-13 094922.png|400px]]

= UBIK =

<Give step-by-step instructions, use images, ...>

{{Template:HowTo/End}}

==See also==

File:Screenshot 2026-08-13 094922.png

2026-08-13T07:51:30Z

FMW: FMW lud eine neue Version von File:Screenshot 2026-08-13 094922.png hoch

Datei hochgeladen mit MsUpload

Configure Comos for CUI

2026-08-13T07:50:44Z

FMW:

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.
Because {{Comos}} is not a Product from Augmensys, please request all Comos changes or adaptions at your local Simens or Siemens Parter.

{{Template:HowTo/Begin}}

= Idea and Concept =

The Interfaceing of Data is depending 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 shema 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}} Smar 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 UnitItems, and some ComosDocumentTypeProxy's
For detailed Informations about the {{UBIK}} Classes please see

* [[MetaProxy]]
* [[MetaClass]]
* [[SELECTIVELIST]]
* [[SELECTIVEITEM]]
* [[UNIT]]

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

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

[[File: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®.

[[File:Screenshot 2026-08-13 094922.png]50:50]

= UBIK =

<Give step-by-step instructions, use images, ...>

{{Template:HowTo/End}}

==See also==

Configure Comos for CUI

2026-08-13T07:49:52Z

FMW:

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.
Because {{Comos}} is not a Product from Augmensys, please request all Comos changes or adaptions at your local Simens or Siemens Parter.

{{Template:HowTo/Begin}}

= Idea and Concept =

The Interfaceing of Data is depending 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 shema 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}} Smar 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 UnitItems, and some ComosDocumentTypeProxy's
For detailed Informations about the {{UBIK}} Classes please see

* [[MetaProxy]]
* [[MetaClass]]
* [[SELECTIVELIST]]
* [[SELECTIVEITEM]]
* [[UNIT]]

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

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

[[File: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®.

[[File:Screenshot 2026-08-13 094922.png]]

= UBIK =

<Give step-by-step instructions, use images, ...>

{{Template:HowTo/End}}

==See also==

File:Screenshot 2026-08-13 094922.png

2026-08-13T07:49:43Z

FMW: Datei hochgeladen mit MsUpload

Datei hochgeladen mit MsUpload

File:Screenshot 2026-08-13 093803.png

2026-08-13T07:40:22Z

FMW: Datei hochgeladen mit MsUpload

Datei hochgeladen mit MsUpload

File:Screenshot 2026-08-13 091304.png

2026-08-13T07:13:41Z

FMW: Datei hochgeladen mit MsUpload

Datei hochgeladen mit MsUpload

Configure Comos for CUI

2026-08-13T06:37:23Z

FMW: /* Comos */

BatchWriteOrchestrator

2025-10-30T06:57:57Z

FMW:

BatchWriteOrchestrator is an orchestrator which can be configured to be executed on the UBIK Enterprise Service e.g. using PluginExecutionConfigPath.
for UBIK Studio Version 4.7 and higher, it has to posible calls "UBIK.CUI.Orchestration.BatchWriteOrchestrator" for a Single InterfaceAdminObject and "UBIK.CUI.Orchestration.MutliBatchWriteOrchestrator" for a tree of InterfaceAdminObjects

Offten Named as "CUIExportOrchestrator.json" and mentioned as "PluginExecutionConfigPath" in the "UBIK.EnterpriseService.exe.config" file
<source lang = "csharp">
{
"RepeateEveryMinutes": 10,
"SqlConnectionDefinition":
{
"SSPI": false,
"SQLUser": "....",
"SQLPassword": "....",
"SQLServer": "....,
"SQLInitialCatalog": "...."
},
"Tasks":
[
{
"ClassFullname": "UBIK.CUI.Orchestration.BatchWriteOrchestrator",
"MethodName": "Apply",
"MethodParameterPathFullName": "my_params.json",
}
]
}
</source>

<source lang = "csharp">
{
"RepeateEveryMinutes": 10,
"SqlConnectionDefinition":
{
"SSPI": false,
"SQLUser": "....",
"SQLPassword": "....",
"SQLServer": "....,
"SQLInitialCatalog": "...."
},
"Tasks":
[
{
"ClassFullname": "UBIK.CUI.Orchestration.MutliBatchWriteOrchestrator",
"MethodName": "Apply",
"MethodParameterPathFullName": "my_params.json",
}
]
}
</source>

You have to configure parameters via the method parameter file:
<source lang = "csharp">
public class ServiceParameter
{
public Guid? RegistrationInterfaceAdmin{ get; set; }

public Guid[]? Proxies{ get; }

public Integer? max_proxies{ get; }

public Guid? RestAPIInterfaceAdmin{ get; set; }
}
</source>

the file "my_params.json" used as "MethodParameterPathFullName" will be looking like this example
<source lang = "csharp">
{
"RegistrationInterfaceAdmin": null,
"Proxies": null,
"max_proxies": 500,
"RestAPIInterfaceAdmin": "e09bfeca-18e1-45e5-a605-038912882c2d"
}
</source>

{| class="wikitable" style="text-align: left; width: 100%"
|-
! style="width:25%" |Property
!! style="width:75%" |Description
|-
| RegistrationInterfaceAdmin
| Interface Admin witch was uesd to Import from xml file
|-
| Proxies
| ["GUID","GUID","GUID","GUID"] Array of GUID for Proxies that should be exportet
|-
| max_proxies
| Integer count of Proxies that should be prozessed in one bulk
|-
| RestAPIInterfaceAdmin
| GUID of Interface Admin Object that is relatet to the Proxies or the hirarchical owner of many Admin Objects for MultiBatch
|-

BatchWriteOrchestrator

2025-10-30T06:53:14Z

FMW:

BatchWriteOrchestrator is an orchestrator which can be configured to be executed on the UBIK Enterprise Service e.g. using PluginExecutionConfigPath.
for UBIK Studio Version 4.7 and higher, it has to posible calls "UBIK.CUI.Orchestration.BatchWriteOrchestrator" for a Single InterfaceAdminObject and "UBIK.CUI.Orchestration.MutliBatchWriteOrchestrator" for a tree of InterfaceAdminObjects

Offten Named as "CUIExportOrchestrator.json" and mentioned as "PluginExecutionConfigPath" in the "UBIK.EnterpriseService.exe.config" file
<source lang = "csharp">
{
"RepeateEveryMinutes": 10,
"SqlConnectionDefinition":
{
"SSPI": false,
"SQLUser": "....",
"SQLPassword": "....",
"SQLServer": "....,
"SQLInitialCatalog": "...."
},
"Tasks":
[
{
"ClassFullname": "UBIK.CUI.Orchestration.BatchWriteOrchestrator",
"MethodName": "Apply",
"MethodParameterPathFullName": "my_params.json",
}
]
}
</source>

<source lang = "csharp">
{
"RepeateEveryMinutes": 10,
"SqlConnectionDefinition":
{
"SSPI": false,
"SQLUser": "....",
"SQLPassword": "....",
"SQLServer": "....,
"SQLInitialCatalog": "...."
},
"Tasks":
[
{
"ClassFullname": "UBIK.CUI.Orchestration.MutliBatchWriteOrchestrator",
"MethodName": "Apply",
"MethodParameterPathFullName": "my_params.json",
}
]
}
</source>

You have to configure parameters via the method parameter file:
<source lang = "csharp">
public class ServiceParameter
{
public Guid? RegistrationInterfaceAdmin{ get; set; }

public Guid[]? Proxies{ get; }

public Guid? RestAPIInterfaceAdmin{ get; set; }
}
</source>

the file "my_params.json" used as "MethodParameterPathFullName" will be looking like this example
<source lang = "csharp">
{
"RegistrationInterfaceAdmin": null,
"Proxies": null,
"max_proxies": 500,
"RestAPIInterfaceAdmin": "e09bfeca-18e1-45e5-a605-038912882c2d"
}
</source>

{| class="wikitable" style="text-align: left; width: 100%"
|-
! style="width:25%" |Property
!! style="width:75%" |Description
|-
| RegistrationInterfaceAdmin
| Interface Admin witch was uesd to Import from xml file
|-
| Proxies
| ["GUID","GUID","GUID","GUID"] Array of GUID for Proxies that should be exportet
|-
| max_proxies
| Integer count of Proxies that should be prozessed in one bulk
|-
| RestAPIInterfaceAdmin
| GUID of Interface Admin Object that is relatet to the Proxies or the hirarchical owner of many Admin Objects for MultiBatch
|-

BatchWriteOrchestrator

2025-10-30T06:52:47Z

FMW:

BatchWriteOrchestrator is an orchestrator which can be configured to be executed on the UBIK Enterprise Service e.g. using PluginExecutionConfigPath.
for UBIK Studio Version 4.7 and higher, it has to posible calls "UBIK.CUI.Orchestration.BatchWriteOrchestrator" for a Single InterfaceAdminObject and "UBIK.CUI.Orchestration.MutliBatchWriteOrchestrator" for a tree of InterfaceAdminObjects

Offten Named as "CUIExportOrchestrator.json" and mentioned as "PluginExecutionConfigPath" in the "UBIK.EnterpriseService.exe.config" file
<source lang = "csharp">
{
"RepeateEveryMinutes": 10,
"SqlConnectionDefinition":
{
"SSPI": false,
"SQLUser": "....",
"SQLPassword": "....",
"SQLServer": "....,
"SQLInitialCatalog": "...."
},
"Tasks":
[
{
"ClassFullname": "UBIK.CUI.Orchestration.BatchWriteOrchestrator",
"MethodName": "Apply",
"MethodParameterPathFullName": "my_params.json",
}
]
}
</source>

<source lang = "csharp">
{
"RepeateEveryMinutes": 10,
"SqlConnectionDefinition":
{
"SSPI": false,
"SQLUser": "....",
"SQLPassword": "....",
"SQLServer": "....,
"SQLInitialCatalog": "...."
},
"Tasks":
[
{
"ClassFullname": "UBIK.CUI.Orchestration.MutliBatchWriteOrchestrator",
"MethodName": "Apply",
"MethodParameterPathFullName": "my_params.json",
}
]
}
</source>

You have to configure parameters via the method parameter file:
<source lang = "csharp">
public class ServiceParameter
{
public Guid? RegistrationInterfaceAdmin{ get; set; }

public Guid[]? Proxies{ get; }

public Guid? RestAPIInterfaceAdmin{ get; set; }
}
</source>

the file "my_params.json" used as "MethodParameterPathFullName" will be looking like this example
<source lang = "csharp">
{
"RegistrationInterfaceAdmin": null,
"Proxies": null,
"max_proxies": 500,
"RestAPIInterfaceAdmin": "e09bfeca-18e1-45e5-a605-038912882c2d"
}
</source>

{| class="wikitable" style="text-align: left; width: 100%"
|-
! style="width:25%" |Property
!! style="width:75%" |Description
|-
| RegistrationInterfaceAdmin
| Interface Admin witch was uesd to Import from xml file
|-
| Proxies
| ["GUID","GUID","GUID","GUID"] Array of GUID for Proxies that should be exportet
|-
| max_proxies
| 500 count of Proxies that should be prozessed in one bulk
|-
| RestAPIInterfaceAdmin
| GUID of Interface Admin Object that is relatet to the Proxies or the hirarchical owner of many Admin Objects for MultiBatch
|-

HowTo:Set Up CUI Rest API

2025-10-24T07:38:36Z

FMW:

==Overview==
The CUI -> "{{Comos}} {{UBIK}} Interface" is a Standard Dataexchange function betwen the tow Systems {{Comos}} and {{UBIK}} it is a bidirektional Communikation baesd on Comos WEB Rest API and a UBIK CUI Plugin.

For Comos make sure you have a working Installation of {{Comos}} and {{Comos Web}} with acces to its {{Comos}} Database, you also need the License called “COMOS_Mobile_Worker_Server”

On UBIK side to set it up please start with the Installation of UBIK, UBIK Database and its Webservices and EnterpriseServer(s)

* [[HowTo:Install_UBIK_Studio]]
* [[HowTo:Install_UBIK_Database]]
* [[HowTo:Install_UBIK_Web_Service]]
* [[Configure_Enterprise_Service_for_CUI]]

After that you have to possible ways to go on, Create a {{UBIK}} MetaClass strukte manually or via Import from Comos.

If you want to export from Comos the first step is to check, update or Create Templates, like in this description PDF:

[[:File:Admin_Comos_UBIK_Interface_2025_10_EN.pdf]]

After Template Structure in Comos includes all the MetaClasses and Properties that you need on UBIK side, export these Comos Template as Metainformation for UBIK:

In Standard Comos iDB there is a new Module section M67 for Comos Mobile Worker (UBIK)
For a standard MRO Use case there are Templates Predefined, these Templates are connected to Comos CDevices that have the Functional Classification C270 (iDB) (for cDB there is a C2 Classification available).
Bevor, please make sure that the Project settings for CUI Interface are there and Active; you find them in Project settings an make sure that the Active checkbox on COMOS Mobile Worker Interface is checked.

First make sure the Interface is "Active" in Project settings of SO1 (or your used Workinglayer)

[[File:Project_activation.png|400px]]

Next is to oben the ComosBaseObject in SO1, it should be found in iDB Databases at "@30|M67|A50|A20|A10", please make sure that the filepath for the xml is existing and accessable.

[[File:Export_from_Comos.png|400px]]

To import in a UBIK Database you have to use {{UBIK}} Smart Studio [[Smart_Studio]]

* [[Smart_Modelling]]

* [[Setting_Up_UBIK_for_CUI]]

File:Admin Comos UBIK Interface 2025 10 EN.pdf

2025-10-24T07:38:24Z

FMW: Datei hochgeladen mit MsUpload

Datei hochgeladen mit MsUpload

Configure Comos for CUI

2025-10-20T11:58:26Z

FMW: Created page with "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. Because {{Comos..."

UNIT

2025-10-20T11:57:36Z

FMW: /* See also */

{{MetaClassInfoBox
| title = Unit
| name = UNIT
| internalname = SystemObjects.UNIT
| namespace = System.Unit
| image = [[File:SY_UNIT.png|220px]]
| imagecaption = Unit
| purpose = Manage SI units
| version = 2+
| typestring = UBIK.Kernel.MetaClass
| runtimetype = UBIK.Kernel.Unit
}}
A unit is an object to define a SI unit.

==See also==


[[UNITITEM]]

[[System_of_units]]

[[Category:Metaclasses|UNIT]]

UNIT

2025-10-20T11:57:28Z

FMW: /* See also */

UNIT

2025-10-20T11:56:41Z

FMW:

UNIT

2025-10-20T11:56:32Z

FMW:

UNIT

2025-10-20T11:56:23Z

FMW:

UNIT

2025-10-20T11:56:15Z

FMW:

UNIT

2025-10-20T11:56:01Z

FMW:

HowTo:Set Up CUI Rest API

2025-10-16T12:58:34Z

FMW:

==Overview==
The CUI -> "{{Comos}} {{UBIK}} Interface" is a Standard Dataexchange function betwen the tow Systems {{Comos}} and {{UBIK}} it is a bidirektional Communikation baesd on Comos WEB Rest API and a UBIK CUI Plugin.

For Comos make sure you have a working Installation of {{Comos}} and {{Comos Web}} with acces to its {{Comos}} Database, you also need the License called “COMOS_Mobile_Worker_Server”

On UBIK side to set it up please start with the Installation of UBIK, UBIK Database and its Webservices and EnterpriseServer(s)

* [[HowTo:Install_UBIK_Studio]]
* [[HowTo:Install_UBIK_Database]]
* [[HowTo:Install_UBIK_Web_Service]]
* [[Configure_Enterprise_Service_for_CUI]]

After that you have to possible ways to go on, Create a {{UBIK}} MetaClass strukte manually or via Import from Comos.

If you want to export from Comos the first step is to check, update or Create Templates, like in this description PDF:

[[:File:Admin_Comos_UBIK_Interface_2023_07_EN.pdf]]

After Template Structure in Comos includes all the MetaClasses and Properties that you need on UBIK side, export these Comos Template as Metainformation for UBIK:

In Standard Comos iDB there is a new Module section M67 for Comos Mobile Worker (UBIK)
For a standard MRO Use case there are Templates Predefined, these Templates are connected to Comos CDevices that have the Functional Classification C270 (iDB) (for cDB there is a C2 Classification available).
Bevor, please make sure that the Project settings for CUI Interface are there and Active; you find them in Project settings an make sure that the Active checkbox on COMOS Mobile Worker Interface is checked.

First make sure the Interface is "Active" in Project settings of SO1 (or your used Workinglayer)

[[File:Project_activation.png|400px]]

Next is to oben the ComosBaseObject in SO1, it should be found in iDB Databases at "@30|M67|A50|A20|A10", please make sure that the filepath for the xml is existing and accessable.

[[File:Export_from_Comos.png|400px]]

To import in a UBIK Database you have to use {{UBIK}} Smart Studio [[Smart_Studio]]

* [[Smart_Modelling]]

* [[Setting_Up_UBIK_for_CUI]]

Setting Up UBIK for CUI

2025-10-16T12:55:13Z

FMW:

Setting uo a UBIK Database fur CUI Dataexchange
{{Template:HowTo/Begin}}

= Instructions =

To set up Interfacing on UBIK Database you need Configurations \ Objects

* Comos Project
* Comos Login
* Interface Admin Comos
* Relation between Comos Project and Language

= Comos Project =


Best approatch is to go to MetaClass COMOS_PROJECT and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> COMOS_PROJECT

Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface ->COMOS_PROJECT

[[File:ComosProject_see_all.png|400px]][[File:ComosProject_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Descripe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

The Database ID is also the same as in Comos, on the Project settings for Mobile Solutions, the Enterprise Server here is that one from {{UBIK}} like you set up the Notification Endpoint.
Project_ID, Working_Overlay_ID is again form Comos, Project_ID is Mandatory anyway, if you want to connect with an WorkingOverly from Comos this ID is also needet.
The Registration folder is only needet when you want to use XML Files for Objects that are not Classified in Comos.

[[File:New_Project_MC.png|400px]]
[[File:New_comos_project.png|400px]]

= Comos Login =


Similar to COMOS_PROJECT go to MetaClass COMOS_LOGIN and derive a new Metaclass.

Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> SERVICE_LOGIN -> BASICAUTH_SERVICE_LOGIN -> COMOS_LOGIN

Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> COMOS_LOGIN

[[File:ComosLogin_see_all.png|400px]][[File:ComosLogin_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Descripe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

You have to Link a instance form COMOS_PROJECT or its children, so link here the Instance you created bevor in the new Created COMOS_PROJECT Childclass
with the checkbox you ask UBIK to Authenticate bevore sending data, could be that Systemsecurty is asking for this.
In Service URL you have to give the Comos WebstartPage url, and User and Password for Comos login (mostly Domainuser)

[[File:New_login_MC.png|400px]]
[[File:New_Login.png|400px]]

= Interface Admin Comos =


Similar like bevor go to MetaClass INTERFACE_ADMIN_COMOS and derive a new Metaclass.

Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> INTERFACE_ADMIN_ROOT -> INTERFACE_ADMIN_COMOS

Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> {}Comos.Interface.Administration -> INTERFACE_ADMIN_COMOS

[[File:IA_COMOS_see_all.png|400px]][[File:IA_COMOS_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, dont forget to link to the LoginObject please Save;

[[File:IA_CMW_LINK.png|400px]]

To Configure the Proxys that should be Imported and Exported please open the New InterfaceAdmin in a RelationEditor. Than drag an drop all the relevant Proxy to the Interface admin Object.

[[File:IA_RELATIONS.png|800px]]

= Relation between Comos Project and Language =


Different to bevore RelationalClass SYSREL_PROJECT_LANGUAGE stays the SystemMetaClass.

To find the MetaClass in {{UBIK}} See all goto -> RELATIONDATA -> SYSREL_PROJECT_LANGUAGE

Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> SYSREL_PROJECT_LANGUAGE

[[File:Lang_REL_see_all.png|400px]][[File:Lang_REL_ContentView.png|400px]]

Please open the Class in a Bulk Editor;

[[File:REL_OVERVIEW.png|1200px]]

To Create a new Instance set a Comos_Project Instance to LEFTUID and a Language Object to the RIGHTUID.

Add the Microsoft LCID number for your Language.

And also the Comos settings witch Language is the current Project, and User Default.

The Languages from UBIK u find in

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> INTERFACE_ADMIN_ROOT -> INTERFACE_ADMIN_COMOS

Or on Content View you find it below Namespaces; goto -> {}System -> {}System.Main -> {}System.Main.Language -> LANGUAGE -> {}System

{{Template:HowTo/End}}

==See also==


[[Add_Languages_to_UBIK]]

[https://cldr.unicode.org/ Unicode CLDR Project]

[https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-lcid/70feba9f-294e-491e-b6eb-56532684c37f Microsoft LCID]

Setting Up UBIK for CUI

2025-10-16T12:54:56Z

FMW:

Setting uo a UBIK Database fur CUI Dataexchange
{{Template:HowTo/Begin}}

= Instructions =

To set up Interfacing on UBIK Database you need Configurations \ Objects

* Comos Project
* Comos Login
* Interface Admin Comos
* Relation between Comos Project and Language

= Comos Project =


Best approatch is to go to MetaClass COMOS_PROJECT and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> COMOS_PROJECT

Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface ->COMOS_PROJECT

[[File:ComosProject_see_all.png|400px]][[File:ComosProject_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Descripe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

The Database ID is also the same as in Comos, on the Project settings for Mobile Solutions, the Enterprise Server here is that one from {{UBIK}} like you set up the Notification Endpoint.
Project_ID, Working_Overlay_ID is again form Comos, Project_ID is Mandatory anyway, if you want to connect with an WorkingOverly from Comos this ID is also needet.
The Registration folder is only needet when you want to use XML Files for Objects that are not Classified in Comos.

[[File:New_Project_MC.png|400px]]
[[File:New_comos_project.png|400px]]

= Comos Login =


Similar to COMOS_PROJECT go to MetaClass COMOS_LOGIN and derive a new Metaclass.

Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> SERVICE_LOGIN -> BASICAUTH_SERVICE_LOGIN -> COMOS_LOGIN

Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> COMOS_LOGIN

[[File:ComosLogin_see_all.png|400px]][[File:ComosLogin_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Descripe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

You have to Link a instance form COMOS_PROJECT or its children, so link here the Instance you created bevor in the new Created COMOS_PROJECT Childclass
with the checkbox you ask UBIK to Authenticate bevore sending data, could be that Systemsecurty is asking for this.
In Service URL you have to give the Comos WebstartPage url, and User and Password for Comos login (mostly Domainuser)

[[File:New_login_MC.png|400px]]
[[File:New_Login.png|400px]]

= Interface Admin Comos =


Similar like bevor go to MetaClass INTERFACE_ADMIN_COMOS and derive a new Metaclass.

Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> INTERFACE_ADMIN_ROOT -> INTERFACE_ADMIN_COMOS

Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> {}Comos.Interface.Administration -> INTERFACE_ADMIN_COMOS

[[File:IA_COMOS_see_all.png|400px]][[File:IA_COMOS_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, dont forget to link to the LoginObject please Save;

[[File:IA_CMW_LINK.png|400px]]

To Configure the Proxys that should be Imported and Exported please open the New InterfaceAdmin in a RelationEditor. Than drag an drop all the relevant Proxy to the Interface admin Object.

[[File:IA_RELATIONS.png|800px]]

= Relation between Comos Project and Language =


Different to bevore RelationalClass SYSREL_PROJECT_LANGUAGE stays the SystemMetaClass.

To find the MetaClass in {{UBIK}} See all goto -> RELATIONDATA -> SYSREL_PROJECT_LANGUAGE

Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> SYSREL_PROJECT_LANGUAGE

[[File:Lang_REL_see_all.png|400px]][[File:Lang_REL_ContentView.png|400px]]

Please open the Class in a Bulk Editor;

[[File:REL_OVERVIEW.png|1200px]]

To Create a new Instance set a Comos_Project Instance to LEFTUID and a Language Object to the RIGHTUID.

Add the Microsoft LCID number for your Language.

And also the Comos settings witch Language is the current Project, and User Default.

The Languages from UBIK u find in

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> INTERFACE_ADMIN_ROOT -> INTERFACE_ADMIN_COMOS

Or on Content View you find it below Namespaces; goto -> {}System -> {}System.Main -> {}System.Main.Language -> LANGUAGE -> {}System

{{Template:HowTo/End}}

==See also==


[[Add_Languages_to_UBIK]]

[[https://cldr.unicode.org/ Unicode CLDR Project]]

[https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-lcid/70feba9f-294e-491e-b6eb-56532684c37f Microsoft LCID]

HowTo:Add Languages to UBIK

2025-10-16T12:48:32Z

FMW:

A set of languages can easily be added to the {{UBIK}} database by using the [[Database Manager]].

#In the menu select ''Database → Database Manager''
#Change to the tab ''Languages''.<br/>[[File:UI_HowTo_Add_Languages_01.png|220 px|border|alt=Add Languages|Add Languages]]
#You see a list of the configured database languages on this tab
#Select the amount of languages you want to add in the field ''New Languages''
#Press {{key press|Add}} to create the new set of languages and confirm with {{key press|OK}}.<br/>[[File:UI_HowTo_Add_Languages_02.png|220 px|border|alt=Confirm Add Languages|Confirm Add Languages]]
#The system will add the new languages to {{UBIK}} and execute all the necessary database updates. Once the creation is finished you will see additional entries at the bottom of the list.
#UBIK Languages are normaly using Language Codes according to ISO 639

==See also==
* [[Database Manager]]
* [[Bulk Editor]]
* [[https://en.wikipedia.org/wiki/ISO_639 ISO 639]]

[[Category:How-To|Add Languages to UBIK]]

Setting Up UBIK for CUI

2025-10-16T12:42:38Z

FMW:

Setting uo a UBIK Database fur CUI Dataexchange
{{Template:HowTo/Begin}}

= Instructions =

To set up Interfacing on UBIK Database you need Configurations \ Objects

* Comos Project
* Comos Login
* Interface Admin Comos
* Relation between Comos Project and Language

= Comos Project =


Best approatch is to go to MetaClass COMOS_PROJECT and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> COMOS_PROJECT
Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface ->COMOS_PROJECT

[[File:ComosProject_see_all.png|400px]][[File:ComosProject_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Descripe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

The Database ID is also the same as in Comos, on the Project settings for Mobile Solutions, the Enterprise Server here is that one from {{UBIK}} like you set up the Notification Endpoint.
Project_ID, Working_Overlay_ID is again form Comos, Project_ID is Mandatory anyway, if you want to connect with an WorkingOverly from Comos this ID is also needet.
The Registration folder is only needet when you want to use XML Files for Objects that are not Classified in Comos.

[[File:New_Project_MC.png|400px]]
[[File:New_comos_project.png|400px]]

= Comos Login =


Similar to COMOS_PROJECT go to MetaClass COMOS_LOGIN and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> SERVICE_LOGIN -> BASICAUTH_SERVICE_LOGIN -> COMOS_LOGIN
Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> COMOS_LOGIN

[[File:ComosLogin_see_all.png|400px]][[File:ComosLogin_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Descripe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

You have to Link a instance form COMOS_PROJECT or its children, so link here the Instance you created bevor in the new Created COMOS_PROJECT Childclass
with the checkbox you ask UBIK to Authenticate bevore sending data, could be that Systemsecurty is asking for this.
In Service URL you have to give the Comos WebstartPage url, and User and Password for Comos login (mostly Domainuser)

[[File:New_login_MC.png|400px]]
[[File:New_Login.png|400px]]

= Interface Admin Comos =


Similar like bevor go to MetaClass INTERFACE_ADMIN_COMOS and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> INTERFACE_ADMIN_ROOT -> INTERFACE_ADMIN_COMOS
Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> {}Comos.Interface.Administration -> INTERFACE_ADMIN_COMOS

[[File:IA_COMOS_see_all.png|400px]][[File:IA_COMOS_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, dont forget to link to the LoginObject please Save;

[[File:IA_CMW_LINK.png|400px]]

To Configure the Proxys that should be Imported and Exported please open the New InterfaceAdmin in a RelationEditor. Than drag an drop all the relevant Proxy to the Interface admin Object.

[[File:IA_RELATIONS.png|800px]]

= Relation between Comos Project and Language =


Different to bevore RelationalClass SYSREL_PROJECT_LANGUAGE stays the SystemMetaClass.

To find the MetaClass in {{UBIK}} See all goto -> RELATIONDATA -> SYSREL_PROJECT_LANGUAGE
Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> SYSREL_PROJECT_LANGUAGE

[[File:Lang_REL_see_all.png|400px]][[File:Lang_REL_ContentView.png|400px]]

Please open the Class in a Bulk Editor;

[[File:REL_OVERVIEW.png|1200px]]

To Create a new Instance set a Comos_Project Instance to LEFTUID and a Language Object to the RIGHTUID.
Add the Microsoft LCID number for your Language.
And also the Comos settings witch Language is the current Project, and User Default.

The Languages from UBIK u find in

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> INTERFACE_ADMIN_ROOT -> INTERFACE_ADMIN_COMOS
Or on Content View you find it below Namespaces; goto -> {}System -> {}System.Main -> {}System.Main.Language -> LANGUAGE -> {}System

{{Template:HowTo/End}}

==See also==


[[Add_Languages_to_UBIK]]
[https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-lcid/70feba9f-294e-491e-b6eb-56532684c37f Microsoft LCID]

Setting Up UBIK for CUI

2025-10-16T12:39:52Z

FMW: /* See also */

Setting uo a UBIK Database fur CUI Dataexchange
{{Template:HowTo/Begin}}

= Instructions =

To set up Interfacing on UBIK Database you need Configurations \ Objects

* Comos Project
* Comos Login
* Interface Admin Comos
* Relation between Comos Project and Language

= Comos Project =


Best approatch is to go to MetaClass COMOS_PROJECT and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> COMOS_PROJECT
Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface ->COMOS_PROJECT

[[File:ComosProject_see_all.png|400px]][[File:ComosProject_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Descripe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

The Database ID is also the same as in Comos, on the Project settings for Mobile Solutions, the Enterprise Server here is that one from {{UBIK}} like you set up the Notification Endpoint.
Project_ID, Working_Overlay_ID is again form Comos, Project_ID is Mandatory anyway, if you want to connect with an WorkingOverly from Comos this ID is also needet.
The Registration folder is only needet when you want to use XML Files for Objects that are not Classified in Comos.

[[File:New_Project_MC.png|400px]]
[[File:New_comos_project.png|400px]]

= Comos Login =


Similar to COMOS_PROJECT go to MetaClass COMOS_LOGIN and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> SERVICE_LOGIN -> BASICAUTH_SERVICE_LOGIN -> COMOS_LOGIN
Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> COMOS_LOGIN

[[File:ComosLogin_see_all.png|400px]][[File:ComosLogin_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Descripe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

You have to Link a instance form COMOS_PROJECT or its children, so link here the Instance you created bevor in the new Created COMOS_PROJECT Childclass
with the checkbox you ask UBIK to Authenticate bevore sending data, could be that Systemsecurty is asking for this.
In Service URL you have to give the Comos WebstartPage url, and User and Password for Comos login (mostly Domainuser)

[[File:New_login_MC.png|400px]]
[[File:New_Login.png|400px]]

= Interface Admin Comos =


Similar like bevor go to MetaClass INTERFACE_ADMIN_COMOS and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> INTERFACE_ADMIN_ROOT -> INTERFACE_ADMIN_COMOS
Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> {}Comos.Interface.Administration -> INTERFACE_ADMIN_COMOS

[[File:IA_COMOS_see_all.png|400px]][[File:IA_COMOS_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, dont forget to link to the LoginObject please Save;

[[File:IA_CMW_LINK.png|400px]]

To Configure the Proxys that should be Imported and Exported please open the New InterfaceAdmin in a RelationEditor. Than drag an drop all the relevant Proxy to the Interface admin Object.

[[File:IA_RELATIONS.png|800px]]

= Relation between Comos Project and Language =


Different to bevore RelationalClass SYSREL_PROJECT_LANGUAGE stays the SystemMetaClass.

To find the MetaClass in {{UBIK}} See all goto -> RELATIONDATA -> SYSREL_PROJECT_LANGUAGE
Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> SYSREL_PROJECT_LANGUAGE

[[File:Lang_REL_see_all.png|400px]][[File:Lang_REL_ContentView.png|400px]]

Please open the Class in a Bulk Editor;

[[File:REL_OVERVIEW.png|1200px]]

To Create a new Instance set a Comos_Project Instance to LEFTUID and a Language Object to the RIGHTUID.
Add the Microsoft LCID number for your Language.
And also the Comos settings witch Language is the current Project, and User Default.

The Languages from UBIK u find in

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> INTERFACE_ADMIN_ROOT -> INTERFACE_ADMIN_COMOS
Or on Content View you find it below Namespaces; goto -> {}System -> {}System.Main -> {}System.Main.Language -> LANGUAGE -> {}System

{{Template:HowTo/End}}

==See also==


[[Add_Languages_to_UBIK]]

Setting Up UBIK for CUI

2025-10-16T12:38:54Z

FMW: /* Relation between Comos Project and Language */

Setting uo a UBIK Database fur CUI Dataexchange
{{Template:HowTo/Begin}}

= Instructions =

To set up Interfacing on UBIK Database you need Configurations \ Objects

* Comos Project
* Comos Login
* Interface Admin Comos
* Relation between Comos Project and Language

= Comos Project =


Best approatch is to go to MetaClass COMOS_PROJECT and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> COMOS_PROJECT
Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface ->COMOS_PROJECT

[[File:ComosProject_see_all.png|400px]][[File:ComosProject_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Descripe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

The Database ID is also the same as in Comos, on the Project settings for Mobile Solutions, the Enterprise Server here is that one from {{UBIK}} like you set up the Notification Endpoint.
Project_ID, Working_Overlay_ID is again form Comos, Project_ID is Mandatory anyway, if you want to connect with an WorkingOverly from Comos this ID is also needet.
The Registration folder is only needet when you want to use XML Files for Objects that are not Classified in Comos.

[[File:New_Project_MC.png|400px]]
[[File:New_comos_project.png|400px]]

= Comos Login =


Similar to COMOS_PROJECT go to MetaClass COMOS_LOGIN and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> SERVICE_LOGIN -> BASICAUTH_SERVICE_LOGIN -> COMOS_LOGIN
Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> COMOS_LOGIN

[[File:ComosLogin_see_all.png|400px]][[File:ComosLogin_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Descripe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

You have to Link a instance form COMOS_PROJECT or its children, so link here the Instance you created bevor in the new Created COMOS_PROJECT Childclass
with the checkbox you ask UBIK to Authenticate bevore sending data, could be that Systemsecurty is asking for this.
In Service URL you have to give the Comos WebstartPage url, and User and Password for Comos login (mostly Domainuser)

[[File:New_login_MC.png|400px]]
[[File:New_Login.png|400px]]

= Interface Admin Comos =


Similar like bevor go to MetaClass INTERFACE_ADMIN_COMOS and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> INTERFACE_ADMIN_ROOT -> INTERFACE_ADMIN_COMOS
Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> {}Comos.Interface.Administration -> INTERFACE_ADMIN_COMOS

[[File:IA_COMOS_see_all.png|400px]][[File:IA_COMOS_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, dont forget to link to the LoginObject please Save;

[[File:IA_CMW_LINK.png|400px]]

To Configure the Proxys that should be Imported and Exported please open the New InterfaceAdmin in a RelationEditor. Than drag an drop all the relevant Proxy to the Interface admin Object.

[[File:IA_RELATIONS.png|800px]]

= Relation between Comos Project and Language =


Different to bevore RelationalClass SYSREL_PROJECT_LANGUAGE stays the SystemMetaClass.

To find the MetaClass in {{UBIK}} See all goto -> RELATIONDATA -> SYSREL_PROJECT_LANGUAGE
Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> SYSREL_PROJECT_LANGUAGE

[[File:Lang_REL_see_all.png|400px]][[File:Lang_REL_ContentView.png|400px]]

Please open the Class in a Bulk Editor;

[[File:REL_OVERVIEW.png|1200px]]

To Create a new Instance set a Comos_Project Instance to LEFTUID and a Language Object to the RIGHTUID.
Add the Microsoft LCID number for your Language.
And also the Comos settings witch Language is the current Project, and User Default.

The Languages from UBIK u find in

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> INTERFACE_ADMIN_ROOT -> INTERFACE_ADMIN_COMOS
Or on Content View you find it below Namespaces; goto -> {}System -> {}System.Main -> {}System.Main.Language -> LANGUAGE -> {}System

{{Template:HowTo/End}}

==See also==

Setting Up UBIK for CUI

2025-10-16T12:38:31Z

FMW:

Setting uo a UBIK Database fur CUI Dataexchange
{{Template:HowTo/Begin}}

= Instructions =

To set up Interfacing on UBIK Database you need Configurations \ Objects

* Comos Project
* Comos Login
* Interface Admin Comos
* Relation between Comos Project and Language

= Comos Project =


Best approatch is to go to MetaClass COMOS_PROJECT and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> COMOS_PROJECT
Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface ->COMOS_PROJECT

[[File:ComosProject_see_all.png|400px]][[File:ComosProject_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Descripe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

The Database ID is also the same as in Comos, on the Project settings for Mobile Solutions, the Enterprise Server here is that one from {{UBIK}} like you set up the Notification Endpoint.
Project_ID, Working_Overlay_ID is again form Comos, Project_ID is Mandatory anyway, if you want to connect with an WorkingOverly from Comos this ID is also needet.
The Registration folder is only needet when you want to use XML Files for Objects that are not Classified in Comos.

[[File:New_Project_MC.png|400px]]
[[File:New_comos_project.png|400px]]

= Comos Login =


Similar to COMOS_PROJECT go to MetaClass COMOS_LOGIN and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> SERVICE_LOGIN -> BASICAUTH_SERVICE_LOGIN -> COMOS_LOGIN
Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> COMOS_LOGIN

[[File:ComosLogin_see_all.png|400px]][[File:ComosLogin_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Descripe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

You have to Link a instance form COMOS_PROJECT or its children, so link here the Instance you created bevor in the new Created COMOS_PROJECT Childclass
with the checkbox you ask UBIK to Authenticate bevore sending data, could be that Systemsecurty is asking for this.
In Service URL you have to give the Comos WebstartPage url, and User and Password for Comos login (mostly Domainuser)

[[File:New_login_MC.png|400px]]
[[File:New_Login.png|400px]]

= Interface Admin Comos =


Similar like bevor go to MetaClass INTERFACE_ADMIN_COMOS and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> INTERFACE_ADMIN_ROOT -> INTERFACE_ADMIN_COMOS
Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> {}Comos.Interface.Administration -> INTERFACE_ADMIN_COMOS

[[File:IA_COMOS_see_all.png|400px]][[File:IA_COMOS_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, dont forget to link to the LoginObject please Save;

[[File:IA_CMW_LINK.png|400px]]

To Configure the Proxys that should be Imported and Exported please open the New InterfaceAdmin in a RelationEditor. Than drag an drop all the relevant Proxy to the Interface admin Object.

[[File:IA_RELATIONS.png|800px]]

= Relation between Comos Project and Language =


Different to bevore RelationalClass SYSREL_PROJECT_LANGUAGE stays the SystemMetaClass.

To find the MetaClass in {{UBIK}} See all goto -> RELATIONDATA -> SYSREL_PROJECT_LANGUAGE
Or on Content View you find it below Namespaces; goto -> {}Comos -> {}Comos.Interface -> SYSREL_PROJECT_LANGUAGE

[[File:Lang_REL_see_all.png|400px]][[File:Lang_REL_ContentView.png|400px]]

Please open the Class in a Bulk Editor;

[[File:REL_OVERVIEW.png|400px]]

To Create a new Instance set a Comos_Project Instance to LEFTUID and a Language Object to the RIGHTUID.
Add the Microsoft LCID number for your Language.
And also the Comos settings witch Language is the current Project, and User Default.

The Languages from UBIK u find in

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> INTERFACE_ADMIN_ROOT -> INTERFACE_ADMIN_COMOS
Or on Content View you find it below Namespaces; goto -> {}System -> {}System.Main -> {}System.Main.Language -> LANGUAGE -> {}System

{{Template:HowTo/End}}

==See also==

File:REL OVERVIEW.png

2025-10-16T12:34:30Z

FMW: Datei hochgeladen mit MsUpload

Datei hochgeladen mit MsUpload

File:Lang REL ContentView.png

2025-10-16T12:26:22Z

FMW: Datei hochgeladen mit MsUpload

Datei hochgeladen mit MsUpload

File:Lang REL see all.png

2025-10-16T12:26:22Z

FMW: Datei hochgeladen mit MsUpload

Datei hochgeladen mit MsUpload

Setting Up UBIK for CUI

2025-10-16T12:03:00Z

FMW:

Setting uo a UBIK Database fur CUI Dataexchange
{{Template:HowTo/Begin}}

= Instructions =

To set up Interfacing on UBIK Database you need Configurations \ Objects

* Comos Project
* Comos Login
* Interface Admin Comos
* Relation between Comos Project and Language

= Comos Project =


Best approatch is to go to MetaClass COMOS_PROJECT and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> COMOS_PROJECT
Or on Content View you find it below Namespaces; goto -> Comos -> Comos.Interface ->COMOS_PROJECT

[[File:ComosProject_see_all.png|400px]][[File:ComosProject_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Descripe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

The Database ID is also the same as in Comos, on the Project settings for Mobile Solutions, the Enterprise Server here is that one from {{UBIK}} like you set up the Notification Endpoint.
Project_ID, Working_Overlay_ID is again form Comos, Project_ID is Mandatory anyway, if you want to connect with an WorkingOverly from Comos this ID is also needet.
The Registration folder is only needet when you want to use XML Files for Objects that are not Classified in Comos.

[[File:New_Project_MC.png|400px]]
[[File:New_comos_project.png|400px]]

= Comos Login =


Similar to COMOS_PROJECT go to MetaClass COMOS_LOGIN and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> SERVICE_LOGIN -> BASICAUTH_SERVICE_LOGIN -> COMOS_LOGIN
Or on Content View you find it below Namespaces; goto -> Comos -> Comos.Interface -> COMOS_LOGIN

[[File:ComosLogin_see_all.png|400px]][[File:ComosLogin_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Descripe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

You have to Link a instance form COMOS_PROJECT or its children, so link here the Instance you created bevor in the new Created COMOS_PROJECT Childclass
with the checkbox you ask UBIK to Authenticate bevore sending data, could be that Systemsecurty is asking for this.
In Service URL you have to give the Comos WebstartPage url, and User and Password for Comos login (mostly Domainuser)

[[File:New_login_MC.png|400px]]
[[File:New_Login.png|400px]]

= Interface Admin Comos =


Similar like bevor go to MetaClass INTERFACE_ADMIN_COMOS and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> INTERFACE_ADMIN_ROOT -> INTERFACE_ADMIN_COMOS
Or on Content View you find it below Namespaces; goto -> Comos -> Comos.Interface -> Comos.Interface.Administration -> INTERFACE_ADMIN_COMOS

[[File:IA_COMOS_see_all.png|400px]][[File:IA_COMOS_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, dont forget to link to the LoginObject please Save;

[[File:IA_CMW_LINK.png|400px]]

To Configure the Proxys that should be Imported and Exported please open the New InterfaceAdmin in a RelationEditor. Than drag an drop all the relevant Proxy to the Interface admin Object.

[[File:IA_RELATIONS.png|400px]]

= Relation between Comos Project and Language =


{{Template:HowTo/End}}

==See also==

File:IA RELATIONS.png

2025-10-16T12:02:36Z

FMW: Datei hochgeladen mit MsUpload

Datei hochgeladen mit MsUpload

File:IA CMW LINK.png

2025-10-16T11:53:23Z

FMW: Datei hochgeladen mit MsUpload

Datei hochgeladen mit MsUpload

Setting Up UBIK for CUI

2025-10-16T11:44:33Z

FMW:

Setting uo a UBIK Database fur CUI Dataexchange
{{Template:HowTo/Begin}}

= Instructions =

To set up Interfacing on UBIK Database you need Configurations \ Objects

* Comos Project
* Comos Login
* Interface Admin Comos
* Relation between Comos Project and Language

= Comos Project =


Best approatch is to go to MetaClass COMOS_PROJECT and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> COMOS_PROJECT
Or on Content View you find it below Namespaces; goto -> Comos -> Comos.Interface ->COMOS_PROJECT

[[File:ComosProject_see_all.png|400px]][[File:ComosProject_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Descripe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

The Database ID is also the same as in Comos, on the Project settings for Mobile Solutions, the Enterprise Server here is that one from {{UBIK}} like you set up the Notification Endpoint.
Project_ID, Working_Overlay_ID is again form Comos, Project_ID is Mandatory anyway, if you want to connect with an WorkingOverly from Comos this ID is also needet.
The Registration folder is only needet when you want to use XML Files for Objects that are not Classified in Comos.

[[File:New_Project_MC.png|400px]]
[[File:New_comos_project.png|400px]]

= Comos Login =


Similar to COMOS_PROJECT go to MetaClass COMOS_LOGIN and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> SYSTEMOBJECT -> SERVICE_LOGIN -> BASICAUTH_SERVICE_LOGIN -> COMOS_LOGIN
Or on Content View you find it below Namespaces; goto -> Comos -> Comos.Interface -> COMOS_LOGIN

[[File:ComosLogin_see_all.png|400px]][[File:ComosLogin_ContentView.png|400px]]

After giving the new MetaClass a Name and Description, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance.
You can name and Descripe it at will, but it is a god Idea to use a Name or Description that is also in Comos.

You have to Link a instance form COMOS_PROJECT or its children, so link here the Instance you created bevor in the new Created COMOS_PROJECT Childclass
with the checkbox you ask UBIK to Authenticate bevore sending data, could be that Systemsecurty is asking for this.
In Service URL you have to give the Comos WebstartPage url, and User and Password for Comos login (mostly Domainuser)

[[File:New_login_MC.png|400px]]
[[File:New_Login.png|400px]]

= Interface Admin Comos =


Similar like bevor go to MetaClass INTERFACE_ADMIN_COMOS and derive a new Metaclass.
Reason is to get a Metaclass that is cut off from this SystemMetaClass, wich could be changed on an Update of UBIK.

To find the MetaClass in {{UBIK}} See all goto -> SYSROOT -> INTERFACE_ADMIN_ROOT -> INTERFACE_ADMIN_COMOS
Or on Content View you find it below Namespaces; goto -> Comos -> Comos.Interface -> Comos.Interface.Administration -> INTERFACE_ADMIN_COMOS

[[File:IA_COMOS_see_all.png|400px]][[File:IA_COMOS_ContentView.png|400px]]

= Relation between Comos Project and Language =


{{Template:HowTo/End}}

==See also==

File:IA COMOS see all.png

2025-10-16T11:44:10Z

FMW: Datei hochgeladen mit MsUpload

Datei hochgeladen mit MsUpload

File:IA COMOS ContentView.png

2025-10-16T11:44:09Z

FMW: Datei hochgeladen mit MsUpload

Datei hochgeladen mit MsUpload