Difference between revisions of "GFeed-Service"
From Gcube Wiki
(→IS Requirements) |
(→Plugins) |
||
| Line 6: | Line 6: | ||
==Plugins== | ==Plugins== | ||
| + | Plugins are expected to be found in the service classpath. They are typically distributed as uber-jar and their deployment depends on the hosting container. | ||
| + | |||
| + | To see a complete list of available plugins implemetations please refer to [[gFeed-Plugins]] | ||
==IS Requirements== | ==IS Requirements== | ||
Revision as of 17:19, 20 May 2019
Aim of this service is to describe the implementation of gFeed-Service (for more information refer to GFeed).
Architecture
Deployment
Plugins
Plugins are expected to be found in the service classpath. They are typically distributed as uber-jar and their deployment depends on the hosting container.
To see a complete list of available plugins implemetations please refer to gFeed-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
