Difference between revisions of "GFeed-Service"
From Gcube Wiki
(→IS Requirements) |
(→IS Requirements) |
||
| Line 10: | Line 10: | ||
The following is a list of minimal requirements for the execution of gFeed Service. Please keep in mind that depending on deployed plugins these requirements may not be enough. | The following is a list of minimal requirements for the execution of gFeed Service. Please keep in mind that depending on deployed plugins these requirements may not be enough. | ||
| − | * Database | + | * Database : the service needs a dedicated DB for its logic and looks in the current context for a DB registered as Service Endpoint with |
| − | + | ||
** Category : Database | ** Category : Database | ||
** Name : Feeder_DB | ** Name : Feeder_DB | ||
| − | * Common configuration | + | * Common configuration : the service loads default plugins configurations from the IS by lookig for a Generic Resource registered as |
| − | + | ||
** Secondary type : configuration | ** Secondary type : configuration | ||
** Name : gcat-feeder | ** Name : gcat-feeder | ||
=HTTP Interface= | =HTTP Interface= | ||
Revision as of 16:32, 20 May 2019
Aim of this service is to describe the implementation of gFeed-Service (for more information refer to GFeed).
Architecture
Deployment
Plugins
IS Requirements
The following is a list of minimal requirements for the execution of gFeed Service. Please keep in mind that depending on deployed plugins these requirements may not be enough.
- Database : the service needs a dedicated DB for its logic and looks in the current context for a DB registered as Service Endpoint with
- Category : Database
- Name : Feeder_DB
- Common configuration : the service loads default plugins configurations from the IS by lookig for a Generic Resource registered as
- Secondary type : configuration
- Name : gcat-feeder
