Interface Manager - Revision history

KNO at 10:22, 8 May 2015

2015-05-08T10:22:22Z

2015-03-25T07:23:52Z

2015-03-13T14:31:17Z

2015-02-25T15:14:53Z

‎Testing

2015-02-25T15:12:20Z

‎Deploying to the EnterpriseService

2015-02-25T15:08:05Z

‎Deploying to the EnterpriseService

2015-02-25T15:07:18Z

‎Deploying to the EnterpriseService

2015-02-25T15:03:00Z

‎Deploying to the EnterpriseService

2015-02-25T14:58:58Z

‎Deploying to the EnterpriseService

2015-02-25T14:57:22Z

‎Configuration

@@ Line 72: / Line 72: @@
 [[Category:Interfacing]]
 [[Category:Workflow]]
-[[Category:Enterprise server]]
+[[Category:Enterprise service]]
 [[Category:Studio tools]]

@@ Line 1: / Line 1: @@
 [[File:UI_InterfaceManager.png|thumb|220px|Interface Manager]]
-The Interface Manager is meant for administration and testing of interfaces transferring data from or to {{UBIK}}, before deploying them to the [[EnterpriseService]]. When started, the interface manager searches for valid {{UBIK}} interface components, where an interface component can be either an assembly or a [[Workflow]].
+The Interface Manager is meant for administration and testing of interfaces transferring data from or to {{UBIK}}, before deploying them to the [[EnterpriseService|Enterprise Service]]. When started, the interface manager searches for valid {{UBIK}} interface components, where an interface component can be either an assembly or a [[Workflow]].
 ==Interface types==

@@ Line 72: / Line 72: @@
 [[Category:Interfacing]]
 [[Category:Workflow]]
 [[Category:Studio tools]]

@@ Line 41: / Line 41: @@
 ==Testing==
-The InterfaceManager allows you to test interface components or workflows before actually deploying them to the EnterpriseService. To do that, select one of the components in the respective sections and press the ''Execute'' button in the toolbar. The InterfaceManager will the actually call the EnterpriseService and pass it the .command file for processing.
+The InterfaceManager allows you to test interface components or workflows before actually deploying them to the EnterpriseService. To do that, select one of the components in the respective sections and press the [[File:IC_Studio_ExecuteInterface.png|Execute Interface]] ''Execute'' button in the toolbar. The InterfaceManager will the actually call the EnterpriseService and pass it the .command file for processing.
 {{Hint|If the Execute button for a certain component is disabled you need to create a command file first!}}

@@ Line 53: / Line 53: @@
 <InterfaceManager>
    <Interfaces>
-     <Interface FullName="UBIK.Interface.Module.XML" File="C:\00 Augmensys\30 UBIK\EnterpriseService\Bin\Interfaces\UBIK.Interface.Module.XML.dll" Class="UBIK.Interface.Module.XML.XMLDataInterface" Direction="I" />
+     <Interface FullName="UBIK.Interface.Module.XML" File="C:\UBIK\EnterpriseService\Bin\Interfaces\UBIK.Interface.Module.XML.dll" Class="UBIK.Interface.Module.XML.XMLDataInterface" Direction="I" />
      <Workflow UID="5eb1744d-1e3d-4c96-8398-ba3c843d37ee" Async="False" />
    </Interfaces>
    <Folders>
-     <Folder FullName="C:\00 Augmensys\30 UBIK\EnterpriseService\Command" />
+     <Folder FullName="C:\UBIK\EnterpriseService\Command" />
    </Folders>
 </InterfaceManager>
 </source>
 [[Category:Interfacing]]
 [[Category:Workflow]]
 [[Category:Studio tools]]

@@ Line 48: / Line 48: @@
 A valid .command file for a component can be created with the button [[File:IC_Studio_CreateCommandFile.png‎|Create command file]] ''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.
-The interface components, both programmed or workflows, have to be activated to be called by the Enterprise Service. To do so, enable the checkbox next to the according component and use {{keypress|Apply}}. A file ''Interfaces.xml'' should be created in the ''Interfaces'' sub-folder, having for example a content like this:
+The interface components, both programmed or workflows, have to be activated to be called by the Enterprise Service. To do so, enable the checkbox next to the according component and use {{key press|Apply}}. A file ''Interfaces.xml'' should be created in the ''Interfaces'' sub-folder, having for example a content like this:
 <source lang="xml">

@@ Line 47: / Line 47: @@
 ==Deploying to the EnterpriseService==
-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.
+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.
 [[Category:Interfacing]]
 [[Category:Workflow]]
 [[Category:Studio tools]]

← Older revision		Revision as of 14:57, 25 February 2015
Line 33:		Line 33:

	You can add any additional parameters you might need internally in your interface component or workflow. All parameters you add will be passed to the component at startup.		You can add any additional parameters you might need internally in your interface component or workflow. All parameters you add will be passed to the component at startup.
		+	{{Attention\|Additional parameters have to have an equivalent workflow argument as well.}}

	===Folders===		===Folders===