The runtime host in iCIS is based on Microsoft Workflow Foundation 4.5. All Component definitions (Scripts, Adapterflows and Workflows) execute in the runtime host, and the host process supports simultaneous execution of Components. The same runtime host is used in both the service and in the Run component tool, a tool used to test individual Components in an isolated test environment.
iCore runtime is implemented through a number of Server parts that can be distributed to one or multiple Servers. Application pools make it possible to isolate the execution of Components in separate processes and to fine-tune where each Component executes to optimize performance. Runtime is responsible for the execution of Component definitions through Events and Jobs. During execution, runtime listens to and creates Events (internal or external). When an Event configuration matches the Event, the Component configuration is executed in the context of one or several Jobs. The Job in turn generates tracking entities like Nodes and Log entries.
The user can get an overview of runtime activities through the Tracking section in iCore Administrator.