Difference between revisions of "Data Transfer Scheduler"
From Gcube Wiki
(Created page with '__TOC__ == Data Transfer Schedule Service == The Data Transfer Scheduler Service is responsible for the transfer scheduling activity delegating and spawning the transfer logic …') |
|||
| Line 5: | Line 5: | ||
The Data Transfer Scheduler Service is responsible for the transfer scheduling activity delegating and spawning the transfer logic to the series of gDT Agent deployed on the infrastructure. It relies on Messaging to consume transfer results from gDT Agent. In detail the main service consists of one gCore statefull service (singleton) and one gCore stateless service. | The Data Transfer Scheduler Service is responsible for the transfer scheduling activity delegating and spawning the transfer logic to the series of gDT Agent deployed on the infrastructure. It relies on Messaging to consume transfer results from gDT Agent. In detail the main service consists of one gCore statefull service (singleton) and one gCore stateless service. | ||
| − | * The | + | * The ''statefull service'' has the '''factory porttype''' so that the submitting API of Data Transfer Scheduler Service can access it and every WS Resource that the factory creates for a different transfer-operation has one '''statefull porttype'''. |
[[File:Statefull_Service.png|500px|thumb|left|alt text]] | [[File:Statefull_Service.png|500px|thumb|left|alt text]] | ||
| − | * The | + | * The ''stateless service'' has the '''stateless porttype''' so that the management API of Data Transfer Scheduler service can get and set information about the users, the scopes, the files and what else the client wants to manage. |
The following figure indicates the complete parts of the Data Transfer Scheduler Service: | The following figure indicates the complete parts of the Data Transfer Scheduler Service: | ||
Revision as of 13:47, 13 July 2012
Data Transfer Schedule Service
The Data Transfer Scheduler Service is responsible for the transfer scheduling activity delegating and spawning the transfer logic to the series of gDT Agent deployed on the infrastructure. It relies on Messaging to consume transfer results from gDT Agent. In detail the main service consists of one gCore statefull service (singleton) and one gCore stateless service.
- The statefull service has the factory porttype so that the submitting API of Data Transfer Scheduler Service can access it and every WS Resource that the factory creates for a different transfer-operation has one statefull porttype.
- The stateless service has the stateless porttype so that the management API of Data Transfer Scheduler service can get and set information about the users, the scopes, the files and what else the client wants to manage.
The following figure indicates the complete parts of the Data Transfer Scheduler Service:
