Difference between revisions of "Profile Specification"
Manuelesimi (Talk | contribs) (→DILIGENT Resources and profiles) |
Manuelesimi (Talk | contribs) (→DILIGENT Resources and profiles) |
||
| Line 5: | Line 5: | ||
=== DILIGENT Resources and profiles === | === DILIGENT Resources and profiles === | ||
| − | A ''DILIGENT Resource'' is anything whose related information can be gathered, stored, monitored, and disseminated in order to provide the valuable amount of knowledge needed during the creation and management of a VDL as well as to operate the entire DILIGENT infrastructure. | + | A ''DILIGENT Resource'' is anything whose related information can be gathered, stored, monitored, and disseminated in order to provide the valuable amount of knowledge needed during the creation and management of a VDL as well as to operate the entire DILIGENT infrastructure. In the project, the following resources have been identified: |
* VDL | * VDL | ||
| Line 24: | Line 24: | ||
In the following, we will focus about how to compile service profile | In the following, we will focus about how to compile service profile | ||
| − | ==== Service | + | ==== the Service resource ==== |
| − | Usually, a ''Service'' is defined as a software system that delivers functionalities. In DILIGENT, a Service is | + | Usually, a ''Service'' is defined as a software system that delivers functionalities. In DILIGENT, a Service is a not-empty set of related ''Packages'' (connected through dependencies) forming an unique logical entity. A Package is the smallest installable unit of software that can be deployed on a DHN (e.g. a JAR o a GAR archive). Packages are the way in which the software needed to set up a DL has to prepared in order to be used and stored in the system. |
| + | Once the service components have been developed, they must be described by compiling the service profile. | ||
| − | ==== Composition ==== | + | ===== Package types ===== |
| + | |||
| + | There are four types of package: | ||
| + | * WSRFService | ||
| + | * Library | ||
| + | ** Shared | ||
| + | ** Stubs | ||
| + | * Portlet | ||
| + | * GridJob | ||
| + | |||
| + | |||
| + | ===== Composition ===== | ||
The set of Packages forming a Service is composed by: | The set of Packages forming a Service is composed by: | ||
| − | *# one and only one Package of WSRFService | + | *# one and only one Package of WSRFService or Portlet type (the main package or the entry point) |
*# an arbitrary number of other Packages of different type logically related (even if not used) by it. | *# an arbitrary number of other Packages of different type logically related (even if not used) by it. | ||
| − | |||
| − | |||
== How to write the profile specification == | == How to write the profile specification == | ||
Revision as of 15:14, 12 February 2007
How to write the profile specification for this component depending on its type.
Preliminary definitions
DILIGENT Resources and profiles
A DILIGENT Resource is anything whose related information can be gathered, stored, monitored, and disseminated in order to provide the valuable amount of knowledge needed during the creation and management of a VDL as well as to operate the entire DILIGENT infrastructure. In the project, the following resources have been identified:
- VDL
- Collection
- Metadata Collection
- Transformation Rule
- Service
- Running Instance
- External Running Instance
- DHN
- CS
- CSInstance
- gLite resource
Such resources can be combined or created at VDL creation time in order to set up a new Virtual Digital Library. In order to be appropriately managed and discovered, a DILIGENT Resource has to be described by creating a profile document compliant with its XML schema. A Schema per each resource type has been defined and all of them are available in the CNR's SVN Repository In the following, we will focus about how to compile service profile
the Service resource
Usually, a Service is defined as a software system that delivers functionalities. In DILIGENT, a Service is a not-empty set of related Packages (connected through dependencies) forming an unique logical entity. A Package is the smallest installable unit of software that can be deployed on a DHN (e.g. a JAR o a GAR archive). Packages are the way in which the software needed to set up a DL has to prepared in order to be used and stored in the system. Once the service components have been developed, they must be described by compiling the service profile.
Package types
There are four types of package:
- WSRFService
- Library
- Shared
- Stubs
- Portlet
- GridJob
Composition
The set of Packages forming a Service is composed by:
- one and only one Package of WSRFService or Portlet type (the main package or the entry point)
- an arbitrary number of other Packages of different type logically related (even if not used) by it.
