Difference between revisions of "Setting Up UBIK for CUI"
| Line 63: | Line 63: | ||
[[File:IA_COMOS_see_all.png|400px]][[File:IA_COMOS_ContentView.png|400px]] | [[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 = | = Relation between Comos Project and Language = | ||
Revision as of 12:03, 16 October 2025
Setting uo a UBIK Database fur CUI Dataexchange
- Instructions
- Comos Project
- Comos Login
- Interface Admin Comos
- Relation between Comos Project and Language
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
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.
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
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)
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
After giving the new MetaClass a Name and Description, dont forget to link to the LoginObject please Save;
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.
