Difference between revisions of "RuntimeResourceClassification"
(→Runtime Resource Table) |
|||
| Line 9: | Line 9: | ||
! style="background-color:#F2F2F2" width=200 | RuntimeResource | ! style="background-color:#F2F2F2" width=200 | RuntimeResource | ||
|- | |- | ||
| − | | Time Series | + | | Time Series / Ecological Modeling || GCubeGisViewer || [[#Geo Server Runtime Resource|Geo Server]] |
|- | |- | ||
| − | | Time Series | + | | Time Series / Ecological Modeling || GCubeGisViewer || [[#Geo Network Runtime Resource|Geo Network]] |
| − | + | |- | |
| + | | Time Series || Time Series Portlet || [[#RStudio Runtime Resource|RStudio]] | ||
| + | |- | ||
| + | | Time Series || Time Series Portlet || [[#Time Series Database Runtime Resource|TimeSeries Database]] | ||
|} | |} | ||
Revision as of 10:06, 30 April 2012
The gCube Information System has recently been extended in order to support a new type of Resource, the Runtime Resource. This Resource will bla bla
Contents
Runtime Resource Table
| gCubeApp | Component | RuntimeResource |
|---|---|---|
| Time Series / Ecological Modeling | GCubeGisViewer | Geo Server |
| Time Series / Ecological Modeling | GCubeGisViewer | Geo Network |
| Time Series | Time Series Portlet | RStudio |
| Time Series | Time Series Portlet | TimeSeries Database |
Geo Server Runtime Resource
The Geo Server Runtime Resource gives information about Geo Server instance deployed: where the Geo Server is deployed and what are the credentials to contact it.
Description
There will be one Runtime Resource for Geo Server instance.
The resource can be registered;
- at VO level, if the Geo Server instance is shared between VREs.
- at VRE level, if the Geo Server instance is VRE dedicated.
The Geo Server runtime resource is mandatory if in the VO/VRE are installed application using the GCube Gis Viewer widget.
Fields
Other than required Runtime Resource fields almost one access point is necessary for a Geo Server Runtime Resource.
Example
<Profile> <Category>Gis</Category> <Name>GeoServer</Name> <Description>GeoServer configuration</Description> <Platform> <Name>GeoServer</Name> <Version>2</Version> <MinorVersion>1</MinorVersion> <RevisionVersion>0</RevisionVersion> <BuildVersion>0</BuildVersion> </Platform> <RunTime> <HostedOn>geoserver-dev.d4science-ii.research-infrastructures.eu</HostedOn> <GHN UniqueID="" /> <Status>READY</Status> </RunTime> <AccessPoint> <Description>Main access point</Description> <Interface> <Endpoint EntryName="geoserver">http://geoserver-dev.d4science-ii.research-infrastructures.eu/geoserver</Endpoint> </Interface> <AccessData> <Username>admin</Username> <Password>**************</Password> </AccessData> </AccessPoint> </Profile>
Geo Network Runtime Resource
The Geo Network Runtime Resource gives information about Geo Network instance deployed: where the Geo Network is deployed and what are the credentials to contact it.
Description
There will be one Runtime Resource for Geo Network instance.
The resource can be registered;
- at VO level, if the Geo Network instance is shared between VREs.
- at VRE level, if the Geo Network instance is VRE dedicated.
The Geo Network runtime resource is mandatory if in the VO/VRE are installed application using the GCube Gis Viewer widget.
Fields
Other than required Runtime Resource fields almost one access point is necessary for a Geo Network Runtime Resource.
Example
<Profile> <Category>Gis</Category> <Name>GeoNetwork</Name> <Description>GeoNetwork configuration</Description> <Platform> <Name>geonetwork</Name> <Version>2</Version> <MinorVersion>6</MinorVersion> <RevisionVersion>4</RevisionVersion> <BuildVersion>0</BuildVersion> </Platform> <RunTime> <HostedOn>geoserver-dev.d4science-ii.research-infrastructures.eu</HostedOn> <GHN UniqueID="" /> <Status>READY</Status> </RunTime> <AccessPoint> <Description>Main access point</Description> <Interface> <Endpoint EntryName="geonetwork">http://geoserver-dev.d4science-ii.research-infrastructures.eu:8080/geonetwork</Endpoint> </Interface> <AccessData> <Username>admin</Username> <Password>*********</Password> </AccessData> </AccessPoint> </Profile>
