Composition of Process
As a "server" core of "pipeline service" is composed of pipelining processing engine, pipeline processing engine is used to receive a variety of external event listener / service, and pipeline execution environment. Pipeline processing engine can dynamically read the pipeline definition file (extension ".xpf") that is the XML file describing the processing procedure of pipeline, compile and save it, get data according to the definition of the sensor action, start request of pipeline with multi thread and execute it. "Pipeline service" is composed of the following listener/service.
| Service name | Explanation |
|---|---|
| AAC-SOAP AAC-Engine |
Keep account information of pipeline service. To make the model easy in pipeline service, only manage the single user password management internal. Therefore, users do not realize the concept of user. |
| PIPELINE-Service | It is service to process the message queue that is the core of pipeline service. |
| PIPELINE-Filter | It is a process where filter action is processed. |
| PIPELINE-Joint-Parallel PIPELINE-Joint-Serial |
It is a process where joint action is processed. |
| PIPELINE-Recovery | It is a process of retrying when error occurs. |
| POLLING-Service | It is a process where polling of schedule type action of sensor is processed. |
| SCHEDULER-SOAP SCHEDULER-Engine |
It is a process to manage the schedule of schedule type action of sensor. |
| PIPELINE-Coordinator | It is a process to communicate with the pipeline coordinator. The HTTP listener inside. |
| PIPELINE-HTTPD | It is HTTP listener for the direct type action to receive the request of HTTP. |
| FTPService-FTPD | It is FTP service for the direct type action to trigger uploaded files. |