Request
Request Definition
An individual unit of the processing when the pipeline is executed is called "Request".
Request will change unit according to sensor difference of executed pipeline. For example, in action of "Monitor whether there is a text file is added to the folder " request wil be executed for each file in monitoring folder. Even if the sensor is executed, the request is not started if contents of monitoring folder is no change. Similarly, in action of "Get mail", request will be started for each received mail.
It is similar for the direct type action. In "Receive a form request from a browser" action, the pipeline request will be started for each HTTP request received from a browser.
The order of request execution
Started request is processed according to pipeline definition. Started request in sensor stage, save processing contents to the queue in order to transfer processing completed in sensor to the filter. Processing engine of filter stage obtain processing contents and execute processing of filter action, then save processing contents to the queue in order to transfer to joint stage.
Each request is executed completely as separate thread in processing engine of each sensor/filter/joint. Therefore, the request executed later may ends earlier than the request previously executed according to timing.
In particular, in the case of schedule type action, when monitoring interval time is shorter than processing time, it is prone to processing block or catch-up, please pay attention.
Request parameter
For the request, the value can be transferred as a parameter. It is called "Request parameters". When the pipeline is executed in WebAPI of pipeline or "Execute pipeline" action of joint, the request parameter can be specified.
Request monitoring
The execution status of each request can be confirmed on some screens.
The status and the log of request executed recently can be confirmed on the main page of each pipeline while setting pipeline or confirming test. If click each request ID, details can be confirmed, stop and re-execution can be operated.
The request list (pipeline request monitor) can be used while operating. All pipeline requests can be seen in request list. Only a necessary request can be seen, and the request where errors occurred can be executed again collectively by specifying pipeline or date.
About details of request list, please see "Coordinator Operation Guide".