Configure an Execution Pipeline

To configure an Execution Pipeline

1. In the %DNADataRoot%\RealTime\config\Settings directory, either create or open the pipeline JSON file.

   The JSON file should take the following format:

   {
     "RealTime": {
       "PipelineExtensions": {
         "KrunchDataStream": {
           "analog": {
             "UseLegacyExecution": true,
             "CachedSettingsSections": {
               "RealTime": "RealTime"
             },
             "Steps": {
               "AttachHPDB": {
                 "Description": "Attaches to the previously locked table and record and the remote record.",
                 "TypeName": "OASySDNA.RealTime.ExecutionPipelines.KrunchDataStream.Steps.Common.AttachHPDB",
                 "AssemblyName": "OASySDNA.RealTime.ExecutionPipelines.KrunchDataStream",
                 "DependsOn": "",
                 "Enabled": true
               },
               "RecordQuestionable": {
               "InitializeAnalogParameters": {
               "CheckKrunchPrereqs": {
               "ConfigurableQualityBit": {

   Key Name	Description / Allowable Values	Comments
   "RealTime"	<Silo Name>
   "PipelineExtensions"	<Application Name>	The Execution Pipeline currently uses the hard-coded keywords "RealTime" and "PipeLineExtensions" for retrieving other configuration items/sub-items below.
   "KrunchDataStream"	<Pipeline Name>	There can be more than one pipeline within the section formed by the "RealTime" and "PipelineExtensions" keywords. "KrunchDataStream" is a well known pipeline.
   "analog"	<Table Name> For example: "analog", "status", "rate".	A pipeline can contain multiple tables with their own detailed configurations. Next are the configurations that are <Silo> / <Application> / <Pipeline> / <Table> specific.
   "UseLegacyExecution"	Set to one of the following:      false - Enable.      true - Disable pipeline execution.	This configuration allows either the pipeline or an existing legacy method to process individual tables.
   "CachedSettingsSections"	Cached configuration(s) available as context for step executions. For example: "RealTime": "RealTime".	This configuration allows one or more cached configuration in the form of <silo>: <configuration type>.
   "Steps"	"Steps"	The Steps is an array of step structures.
   "AttachHPDB"	<Step Key> For example: "AttachHPDB".	The execution pipeline identifies a step using the step key.
   "Description"	<Description of the step.>
   "TypeName"	<Name of the class created for this step.>	Each step is typically written as a class. As such, there is a corresponding type name to the class name.
   "AssemblyName"	<Name of the dll containing the binaries for the class.>	This is the assembly name containing the steps configured within the .csproj (Visual Studio project) file.
   "DependsOn"	<Step key that must run immediately before this step.>	Note that the first step in a pipeline, such as "AttachHPDB", does not have a previous step.
   "Enabled"	Set this to true so that the Execution Pipeline will load the assembly required for processing.	Execution Pipeline loads the assembly when the step is enabled.

2.  Copy the dynamic-link library (DLL) file to the %DNADataRoot%\RealTime\bin directory.
3.  Restart the RealTime service.