Changes

Interface Manager

67 bytes added, 09:41, 3 August 2012

When started, the interface manager searches for valid UBIK interface components. This search is performed in the sub-directory ''Interfaces''.

~~1) UBIK scans for assemblies (*.dll) which start with the name ''UBIK.Interface.''~~

~~2) it looks for types (classes) in those assemblies which derive from ''UBIK.~~== Identifying Interface~~.UBIKInterfaceBase''~~Components ==

3* UBIK scans for assemblies (*.dll) which start with the name ''UBIK.Interface.'' * it looks for types (classes) in those assemblies which derive from ''UBIK.Interface.UBIKInterfaceBase'' * it checks if those types implement either ''UBIK.Interface.IUBIKImport'' or ''UBIK.Interface.IUBIKExport'' or both

All components that fulfill those criteria will be listed in the boxes ''Import Interfaces'' and/or ''Export Interfaces''. Checking a component will mark it generally for execution with the [[UBIK EnterpriseService]], if a respective valid .command file lands in one of the folders that can be added to ''Command Directories''.

== Additional Functions ==

The ''Parameters'' table allows the creation of named parameters that are passed via the .command file, to enable conditional execution.

A valid .command file for a component can be created with the button ''Create command file'' at any time, it will also be stored in the Interfaces sub-folder and named accordingly. Use this generated file to call your interface via the EnterpriseService later.

JKN

Bureaucrat, administrator

1,471

edits