Signal DSL - Revision history

Yang: /* Watcher Job */

2018-11-12T12:34:52Z

‎Watcher Job

Yang: /* Watcher Job */

2018-11-12T12:32:22Z

‎Watcher Job

Yang: /* Keyword applyon */

2018-11-12T12:21:53Z

‎Keyword applyon

Yang: /* Target File */

2018-11-12T12:18:45Z

‎Target File

Yang: /* Target File */

2018-11-12T12:17:51Z

‎Target File

Yang: /* Target File */

2018-11-12T12:17:26Z

‎Target File

Yang: /* package defintion */

2018-11-12T12:15:43Z

‎package defintion

Yang: /* 2 watcher types */

2018-11-12T12:10:48Z

‎2 watcher types

Yang: /* 2 watcher types */

2018-11-12T12:07:05Z

‎2 watcher types

Yang: /* 2 watcher types */

2018-11-12T12:06:37Z

‎2 watcher types

@@ Line 174: / Line 174: @@
 The maximum thread allowed to be parallel processed ('''max-parallel-thread-count''') is defined in the Datainterchange Configuration File, after keyword <code>entry key="Max-Parallel-Threads-Count" </code> for each Datainterchange Group.  In the run time, the maximum value of all max-parallel-thread-count from all Datainterchange Groups will be used to set the runtime max-parallel-thread-count.
-The current allowed maximum value is 15, and default value is 5. If this value could not be found from any datainterchange groups, the default count will be used to set the runtime max-parallel-thread-count.
+The current allowed '''maximum''' value is '''15''', and '''default''' value is '''5'''. If this value could not be found from any Datainterchange Configuration File for any Datainterchange Groups, the default count will be used to set the runtime max-parallel-thread-count.
 ==== 2 watcher types ====

@@ Line 165: / Line 165: @@
 ====Watcher Job====
 The watcher job queue is used to secure the sequential execution of each watcher jobs (task/list of tasks).
-Responsible for the sequential handling of each queued watcher jobs.
-The jobs generated at the same time from the same file mask watcher can be called as a job group. A grouping of jobs from the same watcher is actually taking place in order to better make use of multi-threading functionalities for the watchers which are allowed a parallel execution of their jobs (only one for a ﬁle mask watcher).
+The jobs generated at the same time from the same file mask watcher can be called as a job group. A grouping of jobs from the same watcher is actually taking place in order to better make use of multi-threading functionalities for the watchers which are allowed a parallel execution of their jobs (only one for a file mask watcher).
-Grouping the execution of jobs from the same watcher is mostly useful in the case of parallel execution of the watcher jobs. Currently this concerns watcher with ﬁle mask definition, whose jobs execute only one task. The file mask watcher can be used for importing a huge amount of data (independently / orthogonally) split over numerous ﬁles into os.bee software. Those ﬁles could be processed parallel with a same file mask watcher. The amount of parallel executed jobs is limited and determined by the property Max-Parallel-Threads-Count, which can be found and set in the corresponding DataInterchangeDSL conﬁguration ﬁle. Please note that the watcher job from a file name watcher deﬁned with sequential execution type will process  its list of tasks in only one dedicated Thread instance; the watcher job from a file name watcher with parallel execution type can execute its tasks in several available threads (not exceeding the maximum thread count).
-The maximum thread allowed to be parallel processed (max-parallel-thread-count) is defined in the datainterchange configuration file, after keyword <code>entry key="Max-Parallel-Threads-Count" </code> for each Datainterchange Group.  In the running time, the maximum value of all max-parallel-thread-count from all Datainterchange Groups will be used to set the runtime max-parallel-thread-count. The current allowed maximum value is 15, and default value is 5. If this value could not be found from any datainterchange groups, the default count will be used to set the runtime max-parallel-thread-count.
 ==== 2 watcher types ====

@@ Line 156: / Line 156: @@
 ====Keyword '''applyon'''====
-The keyword '''applyon''' has been introduced in order to define per watcher, which directory has to be monitored for the triggering events: creations of target files in this directory, which match the given file mask or file name. The watcher-monitored directory corresponds to the import-path ( in conﬁguration ﬁle after keyword <code>entry key ="<datainterchange uinit >-import" </code>)  of the Datainterchange Unit marked with the keyword '''applyon''' as the watcher tasks in the SignalDSL file.
+The keyword '''applyon''' has been introduced in order to define per watcher, which directory has to be monitored for the triggering events:
-If a conﬁguration ﬁle (the DatainterchangeDSL conﬁguration ﬁle, which also contains the SignalDSL properties) exists, the needed import-path property of the Datainterchange Unit exists and its value is valid, then this ﬁle path will be used to monitor. Otherwise, the default path of the Datainterchange Unit defined in the corresponding DatainterchangeDSL ﬁle will be used as the monitored directory.
+creations of target files in this directory, which match the given file mask or file name.
 ====Watcher Job====

@@ Line 149: / Line 149: @@
 A target file is the file which is generated inside the monitored directory, whose filename (+extension) matches the file mask or the file name.
-The datainterchange file used for import processes will be deleted at the end of a successful import, if it is explicitly set in its datainterchange definition. See [[Datainterchange DSL documentation page]] for more information.
+The datainterchange file used for import processes will be deleted at the end of a successful import, if it is explicitly set in its datainterchange definition. See [[Datainterchange DSL]] for more information.
 In case the target file is at the same time used in datainterchange as the import file, it will be deleted at the end of the execution of the watcher job (parallel or sequential), even if it’s not set in the datainterchange definition.

@@ Line 149: / Line 149: @@
 A target file is the file which is generated inside the monitored directory, whose filename (+extension) matches the file mask or the file name.
-The datainterchange file used for import processes will be deleted at the end of a successful import, if it is explicitly set in its datainterchange definition. See [Datainterchange DSL documentation page] for more information.
+The datainterchange file used for import processes will be deleted at the end of a successful import, if it is explicitly set in its datainterchange definition. See [[Datainterchange DSL documentation page]] for more information.
 In case the target file is at the same time used in datainterchange as the import file, it will be deleted at the end of the execution of the watcher job (parallel or sequential), even if it’s not set in the datainterchange definition.

@@ Line 153: / Line 153: @@
 In case the target file is at the same time used in datainterchange as the import file, it will be deleted at the end of the execution of the watcher job (parallel or sequential), even if it’s not set in the datainterchange definition.
-If the import process is failed, at the end of the import process, the corresponding import file will be renamed with form "FAILEDIMPORT" +< actual date formated >+ "Original file name.LOCKED" (as the definition in the following blog post).
+If the import process is failed, at the end of the import process, the corresponding import file will be renamed with form <code>FAILEDIMPORT+< actual date formated >+Original file name.LOCKED</code> (as the definition in the following blog post).
-−
 ====Keyword '''applyon'''====

@@ Line 42: / Line 42: @@
 ** In cases the needed datainterchange properties are '''not available''' in the '''Datainterchange Configuration File''', or the '''Datainterchange Configuration File''' doesn't exist, the default definition of the properties from the DatainterchangeDSL file will be used.
 ** Currently it is not possible to monitor changes on a (web)url-based directory (destination). You may however define a watcher with a ''url-based directory'' and set schedulers to import data from it.
-** Watcher/scheduler generates watcher/scheduler jobs, they will be stored into a queue and processed by the watcher/scheduler job handler. Keyword '''sequential''' and '''parallel''' determinate how the jobs will be executed. As same as the literally meaning, Keyword '''sequential''' means all tasks/jobs will be sequentially executed; Keyword '''parallel''' means all tasks/jobs will be parallel executed.
+** Watcher/scheduler generates watcher/scheduler jobs, they will be stored into a queue and processed by the watcher/scheduler job handler. Keyword '''sequential''' and '''parallel''' determinate how the jobs will be executed. As same as the literally meaning, Keyword '''sequential''' means all tasks/jobs will be sequentially executed; Keyword '''parallel''' means all tasks/jobs will be parallel executed. If it is not defined, '''sequential''' will be take as the default value.
 ► Following are the example predefined datainterchange definition and the corresponding configuration files which will be used in the SingalDSL definition example in this documentation.

@@ Line 186: / Line 186: @@
+}
 </syntaxhighlight>
-: the file mask watcher ''WithMask'' monitors the import directory of Datainterchange Unit ''Gtin'' from Datainterchange Configuration File, when the file names match the mask "Gtin*.csv" (Gtin123.csv, Gtinabcd.csv...) occur, the watcher job <code>import Gtin</code> will be added to the watcher job queue and the jobs will be executed parallel with at most max-parallel-thread-count threads.
+: the file mask watcher ''WithMask'' monitors the import directory of Datainterchange Unit ''Gtin'' from Datainterchange Configuration File, when the file names match the mask "Gtin*.csv" (Gtin123.csv, Gtinabcd.csv...) occur, the watcher jobs with the same task <code>import Gtin</code> will be added to the same watcher job group into watcher job queue and the jobs in the same job group will be executed parallel with at most max-parallel-thread-count threads.
 * '''file name''' watcher:
@@ Line 208: / Line 208: @@
+}
 </syntaxhighlight>
-: the file name watcher ''WithName'' monitors the import directory of Datainterchange Unit ''Gtin'' from Datainterchange Configuration File, when the file named "brands.csv" occurs, the watcher job with task list <code>import Brandowner ... export Brand</code> will be added to the watcher job queue and the jobs will be executed one by one, the tasks in the same task list will be executed parallel with at most max-parallel-thread-count threads.
+: the file name watcher ''WithName'' monitors the import directory of Datainterchange Unit ''Gtin'' from Datainterchange Configuration File, when the file named "brands.csv" occurs, the watcher job with task list <code>import Brandowner ... export Brand</code> will be added to the watcher job queue, the tasks of the job from the same task list will be executed parallel with at most max-parallel-thread-count threads.
 === Scheduler ===

@@ Line 180: / Line 180: @@
 *** for '''parallel''' execution : at most max-parallel-thread-count threads of jobs in the same job group can be executing at the same time.
 *** for '''sequential''' execution : the jobs in the same job group will be executing one by one.
-*: ► '''Example''':
+: ► '''Example''':
-*:<syntaxhighlight lang="java">
+:<syntaxhighlight lang="java">
 watcher WithMask filemask "Gtin*.csv" parallel from Brands {
 	import Gtin
+}
 </syntaxhighlight>
-*: the file mask watcher ''WithMask'' monitors the import directory of Datainterchange Unit ''Gtin'' from Datainterchange Configuration File, when the file names match the mask "Gtin*.csv" (Gtin123.csv, Gtinabcd.csv...) occur, the watcher job <code>import Gtin</code> will be added to the watcher job queue and the jobs will be executed parallel with at most max-parallel-thread-count threads.
+: the file mask watcher ''WithMask'' monitors the import directory of Datainterchange Unit ''Gtin'' from Datainterchange Configuration File, when the file names match the mask "Gtin*.csv" (Gtin123.csv, Gtinabcd.csv...) occur, the watcher job <code>import Gtin</code> will be added to the watcher job queue and the jobs will be executed parallel with at most max-parallel-thread-count threads.
 * '''file name''' watcher:
@@ Line 197: / Line 197: @@
 *** for '''parallel''' execution : at most max-parallel-thread-count threads of tasks in the same job can be executing at the same time.
 *** for '''sequential''' execution : the tasks will be executing one by one.
-*: ► '''Example''':
+: ► '''Example''':
-*:<syntaxhighlight lang="java">
+:<syntaxhighlight lang="java">
 watcher WithName filename "brands.csv" parallel from Brands {
 	import Brandowner
@@ Line 208: / Line 208: @@
+}
 </syntaxhighlight>
-*: the file name watcher ''WithName'' monitors the import directory of Datainterchange Unit ''Gtin'' from Datainterchange Configuration File, when the file named "brands.csv" occurs, the watcher job with task list <code>import Brandowner ... export Brand</code> will be added to the watcher job queue and the jobs will be executed one by one, the tasks in the same task list will be executed parallel with at most max-parallel-thread-count threads.
+: the file name watcher ''WithName'' monitors the import directory of Datainterchange Unit ''Gtin'' from Datainterchange Configuration File, when the file named "brands.csv" occurs, the watcher job with task list <code>import Brandowner ... export Brand</code> will be added to the watcher job queue and the jobs will be executed one by one, the tasks in the same task list will be executed parallel with at most max-parallel-thread-count threads.
 === Scheduler ===