Difference between revisions of "DIS-BDII-Client"
(New page: ==Introduction== This Service replaces the DIS-R-GMA-Client Service implemented in the DILIGENT Alpha release: the EGEE infrastructure has definitely choosen the BDII Server as default gL...) |
(→Introduction) |
||
| Line 3: | Line 3: | ||
This Service replaces the DIS-R-GMA-Client Service implemented in the DILIGENT Alpha release: the EGEE infrastructure has definitely choosen the BDII Server as default gLite Information System, and there was not need to maintain a R-GMA Server harvester active in the DILIGENT Infrastructure. | This Service replaces the DIS-R-GMA-Client Service implemented in the DILIGENT Alpha release: the EGEE infrastructure has definitely choosen the BDII Server as default gLite Information System, and there was not need to maintain a R-GMA Server harvester active in the DILIGENT Infrastructure. | ||
This service is in charge to harvest resources information from the gLite BDII Server it has been configured to interact with. This information is related to grid resources (CEs, SEs, I/O Servers, etc.) belonging to each gLite based grid infrastructure the DILIGENT system is interacting with. Then, the gathered information is manipulated in order to be compliant with the schema adopted in DILIGENT and published as gLite Resource using the DIS-Registry (static information based on Glue schema specification v1.2) or as WS-Resource Properties on the local DIS-IP where the DIS-BDII is deployed via the Aggregator Framework support. | This service is in charge to harvest resources information from the gLite BDII Server it has been configured to interact with. This information is related to grid resources (CEs, SEs, I/O Servers, etc.) belonging to each gLite based grid infrastructure the DILIGENT system is interacting with. Then, the gathered information is manipulated in order to be compliant with the schema adopted in DILIGENT and published as gLite Resource using the DIS-Registry (static information based on Glue schema specification v1.2) or as WS-Resource Properties on the local DIS-IP where the DIS-BDII is deployed via the Aggregator Framework support. | ||
| + | |||
| + | == Implementation Overview== | ||
| + | |||
| + | The only public operations implemented by the DISBDIIClientFactoryService are | ||
| + | |||
| + | createResource(Type) | ||
| + | It allows creating WS-Resources of type DISBDIIClientService/CE/SE, returning a CreateResourceResponse object that contains the EPR of the new WS-Resource created. | ||
| + | The standard GT4 providers provide all the operations offered by the DISBDIIClientService, DISBDIICllientSE and DISBDIIClientCE services: | ||
| + | * SetResourceProperty; | ||
| + | *GetResourceProperty. | ||
| + | |||
| + | |||
| + | queryForProfiles (QueryForProfiles profiles) | ||
| + | Start harvesting from the BDII Server instance the service has been configure to interact, and creates Site/CE/SE/Service gLiteResource profiles contacting the DIS-Registry | ||
| + | |||
| + | |||
| + | queryForPropertes (QueryForProperties properties) | ||
| + | Start harvesting from the BDII Server instance the service has been configure to interact, and creates CE/SE/Service WS-Resource Properties publish them on the DIS. | ||
| + | |||
| + | |||
| + | == Dependencies == | ||
| + | |||
| + | |||
| + | == Usage Example == | ||
Revision as of 14:59, 30 May 2007
Introduction
This Service replaces the DIS-R-GMA-Client Service implemented in the DILIGENT Alpha release: the EGEE infrastructure has definitely choosen the BDII Server as default gLite Information System, and there was not need to maintain a R-GMA Server harvester active in the DILIGENT Infrastructure. This service is in charge to harvest resources information from the gLite BDII Server it has been configured to interact with. This information is related to grid resources (CEs, SEs, I/O Servers, etc.) belonging to each gLite based grid infrastructure the DILIGENT system is interacting with. Then, the gathered information is manipulated in order to be compliant with the schema adopted in DILIGENT and published as gLite Resource using the DIS-Registry (static information based on Glue schema specification v1.2) or as WS-Resource Properties on the local DIS-IP where the DIS-BDII is deployed via the Aggregator Framework support.
Implementation Overview
The only public operations implemented by the DISBDIIClientFactoryService are
createResource(Type) It allows creating WS-Resources of type DISBDIIClientService/CE/SE, returning a CreateResourceResponse object that contains the EPR of the new WS-Resource created. The standard GT4 providers provide all the operations offered by the DISBDIIClientService, DISBDIICllientSE and DISBDIIClientCE services:
- SetResourceProperty;
- GetResourceProperty.
queryForProfiles (QueryForProfiles profiles)
Start harvesting from the BDII Server instance the service has been configure to interact, and creates Site/CE/SE/Service gLiteResource profiles contacting the DIS-Registry
queryForPropertes (QueryForProperties properties)
Start harvesting from the BDII Server instance the service has been configure to interact, and creates CE/SE/Service WS-Resource Properties publish them on the DIS.
