LFC

The client and the server code of LFC has many overlaps therefore they are in the same CVS module: LCG-DM

However the build process produces separate client and server packages:

• client: LFC-client, LFC-interfaces (Perl and Python bindings)
• server: LFC-server-mysql, LFC-server-oracle

The client package can be installed independently of the server package, along with its dependencies: vdt_globus_essentials, glite-security-voms-api-c, lcg-dm-common

DPM

The client and the server code of DPM has many overlaps therefore they are in the same CVS module: LCG-DM

However the build process produces separate client and server packages:

• client: DPM-client, DPM-interfaces (Perl and Python bindings)
• server: DPM-name-server-mysql, DPM-name-server-oracle, DPM-rfio-server, DPM-server-mysql, DPM-server-oracle, DPM-srm-server-mysql, DPM-srm-server-oracle

The client package can be installed independently of the server package, along with its dependencies: vdt_globus_essentials, glite-security-voms-api-c, lcg-dm-common

FTS

The service interface of FTS is a web service, which is described as a WSDL. The interfaces are located in the org.glite.data.transfer-interface and org.glite.security.delegation-interface CVS modules, which are also available as glite-data-transfer-interfaces and glite-security-delegation-interface for third party developments.

The client code of FTS is split in several CVS modules of which produce the following packages: glite-data-transfer-api-c, glite-data-transfer-cli, glite-data-delegation-api-c, glite-data-delegation-cli. One also needs to install their dependencies: vdt_globus_essentials, gridsite-core, CGSI_gSOAP_2.7, glite-data-util-c.

With some effort it would be possible to merge glite-data-transfer-api-c into glite-data-transfer-cli, and glite-data-delegation-api-c into glite-data-delegation-cli, however it would not change the size of the installed client side packages significantly.

The server side of FTS is also split into several CVS modules of which produce the following packages: glite-data-transfer-fts (web service frontend), glite-data-agents-common, glite-data-transfer-agents, glite-data-transfer-proxyrenewal, glite-data-srm-api-c, glite-data-srm2-api-c, glite-data-srm-util-cpp, glite-data-util-c, glite-data-transfer-url-copy, glite-data-transfer-monitor-gridview, glite-data-transfer-monitor-report, glite-data-transfer-scripts.

Hydra

The service interface of Hydra is a web service, which is described as a WSDL. The interface is located in the org.glite.data.catalog-interface CVS module, which is also available as glite-data-catalog-interface package for third party developments.

The client code of Hydra is in the org.glite.data.hydra-cli CVS module which produce the glite-data-hydra-cli package. It also needs the following dependencies: vdt_globus_essentials, gridsite-core, CGSI_gSOAP_2.7, glite-data-util-c.

The server side of Hydra is in the org.glite.data.hydra-service CVS module, which produces the glite-data-hydra-service package.

-- AkosFrohner - 28 Nov 2007