Difference between revisions of "InterfaceAdministration"
| Line 7: | Line 7: | ||
Once an import/export via interface run is executed, a new instance of [[InterfaceExecution]] is automatically generated. The name is generated out of the InterfaceAdministration object name and the current date and time. | Once an import/export via interface run is executed, a new instance of [[InterfaceExecution]] is automatically generated. The name is generated out of the InterfaceAdministration object name and the current date and time. | ||
| + | |||
| + | {{Version/ServerSince|2.6.4}} Using the 'Extensive Logging Enabled' ('Ausführliches Log' in german) you can switch the verbose logging on. This log will provide very detailed information of what went wrong exactly when unsuccessfully executing an import or export of data. | ||
==See also== | ==See also== | ||
* [[InterfaceExecution]] | * [[InterfaceExecution]] | ||
| − | [[Category: | + | [[Category:Interfacing|InterfaceAdministration]] |
| − | [[Category: | + | [[Category:UBIK Object|InterfaceAdministration]] |
Revision as of 12:34, 6 March 2020
Basics
InterfaceAdministration is an administrative object for a set of MetaProxy objects. An InterfaceAdministration is a specialized MetaClass having the ClassType InterfaceAdministration. It handles the management of a certain interface configuration related to MetaProxies, that is executed for data import and/or export.
InterfaceAdministration content has to be derived from the MetaClass INTERFACE ADMIN ROOT. The content object itself can relate to a set of MetaProxies that are used for interface runs. InterfaceAdmin content objects hold a Relation to ProxyMetaProperties named SYSREL INTERFACE ADMIN METAPROXY. Via this relation, all involved MetaProxies are accessible via the administation object.
Once an import/export via interface run is executed, a new instance of InterfaceExecution is automatically generated. The name is generated out of the InterfaceAdministration object name and the current date and time.
Using the 'Extensive Logging Enabled' ('Ausführliches Log' in german) you can switch the verbose logging on. This log will provide very detailed information of what went wrong exactly when unsuccessfully executing an import or export of data.
