Difference between revisions of "RuntimeResourceClassification"

From Gcube Wiki
Jump to: navigation, search
(→‎Ecological Modeling Database Runtime Resource)
(→‎Ecological Modeling Database Runtime Resource)
Line 265: Line 265:
 
</source>
 
</source>
  
−
=== Ecological Modeling Database Runtime Resource ===
+
=== Ecological Modelling Database Runtime Resource ===
  
−
The ''Ecological Modeling Database Runtime Resource'' gives information about where the Ecological Modeling Database is deployed.
+
The ''Ecological Modelling Database Runtime Resource'' gives information about access to the application database.
  
 
==== Description====
 
==== Description====
Line 275: Line 275:
 
* at VRE level, if the Time Series instance is VRE dedicated.
 
* at VRE level, if the Time Series instance is VRE dedicated.
  
−
The Ecological Modelling Database runtime resource is ''mandatory'' if in the VO/VRE are installed application that want to access Time Series Database instance.
+
The Ecological Modelling Database runtime resource is ''mandatory'' for each scopes in which an Ecological Modelling application instance is deployed.
  
 
==== Fields ====
 
==== Fields ====
−
Other than required Runtime Resource fields, two access point entry are required:
+
In order to be validated by the application, the Runtime Resource must follow these rules :  
−
* one with entry name "jdbc" with the necessary information for JDBC access to the database
+
 
−
* one with entry name "readonly" with the readonly access information to the database
+
* Category = ''Database''
−
Both the access point need a "dbname" property specifying the Time Series db name.
+
* Platform/Name = ''postgres''
 +
 
 +
Two Access Points compliant with the following rules are required :
 +
 
 +
* Internal logic database access point :
 +
** Entry Name = ''jdbc''
 +
** user
 +
** password
 +
** Additional Properties :
 +
*** schema (String) = ''aquamaps''
 +
*** tableSpacePrefix (String)
 +
*** tableSpaceCount (Integer)
 +
*** maxConnection (Integer)
 +
 
 +
 
 +
* Publisher database access point :
 +
** Entry Name = ''jdbc''
 +
** user
 +
** password
 +
** Additional Properties :
 +
*** schema (String) = ''aquamapsPublisher''
 +
*** maxConnection (Integer)
  
 
==== Example ====
 
==== Example ====
Line 288: Line 309:
 
   <Profile>
 
   <Profile>
 
       <Category>Database</Category>
 
       <Category>Database</Category>
−
       <Name>TimeSeriesDatabase</Name>
+
       <Name>AquaMaps Service DataBase</Name>
 
       <Description />
 
       <Description />
 
       <Platform>
 
       <Platform>
 
         <Name>postgres</Name>
 
         <Name>postgres</Name>
−
         <Version>9</Version>
+
         <Version>8</Version>
 
         <MinorVersion>1</MinorVersion>
 
         <MinorVersion>1</MinorVersion>
−
         <RevisionVersion>0</RevisionVersion>
+
         <RevisionVersion>1</RevisionVersion>
−
         <BuildVersion>0</BuildVersion>
+
         <BuildVersion>1</BuildVersion>
 
       </Platform>
 
       </Platform>
 
       <RunTime>
 
       <RunTime>
−
         <HostedOn>node24.d.d4science.research-infrastructures.eu</HostedOn>
+
         <HostedOn>dbtest.research-infrastructures.eu</HostedOn>
−
         <GHN UniqueID="" />
+
         <GHN UniqueID="0b473f00-fa6e-11e0-bb84-8d6426bd0941" />
 
         <Status>READY</Status>
 
         <Status>READY</Status>
 
       </RunTime>
 
       </RunTime>
 
       <AccessPoint>
 
       <AccessPoint>
−
         <Description>jdbc conection url</Description>
+
         <Description>Internal buisness logic entry point</Description>
 
         <Interface>
 
         <Interface>
−
             <Endpoint EntryName="jdbc">//node24.d.d4science.research-infrastructures.eu/timeseries</Endpoint>
+
             <Endpoint EntryName="jdbc">//dbtest.research-infrastructures.eu:5432/aquamapsorgupdated</Endpoint>
 
         </Interface>
 
         </Interface>
 
         <AccessData>
 
         <AccessData>
−
             <Username>gcube</Username>
+
             <Username>utente</Username>
−
             <Password>*************</Password>
+
             <Password>UwNMZOK7FlIjGPR+NZCV6w==</Password>
 
         </AccessData>
 
         </AccessData>
 
         <Properties>
 
         <Properties>
 
             <Property>
 
             <Property>
−
               <Name>dbname</Name>
+
               <Name>schema</Name>
−
               <Value encrypted="false">timeseries</Value>
+
               <Value encrypted="false">aquamaps</Value>
 +
            </Property>
 +
            <Property>
 +
              <Name>maxConnection</Name>
 +
              <Value encrypted="false">20</Value>
 +
            </Property>
 +
            <Property>
 +
              <Name>tableSpaceCount</Name>
 +
              <Value encrypted="false">4</Value>
 +
            </Property>
 +
            <Property>
 +
              <Name>tableSpacePrefix</Name>
 +
              <Value encrypted="false">tbsp_</Value>
 
             </Property>
 
             </Property>
 
         </Properties>
 
         </Properties>
 
       </AccessPoint>
 
       </AccessPoint>
 
       <AccessPoint>
 
       <AccessPoint>
−
         <Description>read only access point</Description>
+
         <Description>publisher entry point</Description>
 
         <Interface>
 
         <Interface>
−
             <Endpoint EntryName="readonly">//node24.d.d4science.research-infrastructures.eu/timeseries</Endpoint>
+
             <Endpoint EntryName="jdbc">//dbtest.research-infrastructures.eu:5432/apublisherdb</Endpoint>
 
         </Interface>
 
         </Interface>
 
         <AccessData>
 
         <AccessData>
−
             <Username>readonlyuser</Username>
+
             <Username>utente</Username>
−
             <Password>************</Password>
+
             <Password>UwNMZOK7FlIjGPR+NZCV6w==</Password>
 
         </AccessData>
 
         </AccessData>
 
         <Properties>
 
         <Properties>
 
             <Property>
 
             <Property>
−
               <Name>dbname</Name>
+
               <Name>schema</Name>
−
               <Value encrypted="false">timeseries</Value>
+
               <Value encrypted="false">aquamapsPublisher</Value>
 +
            </Property>
 +
            <Property>
 +
              <Name>maxConnection</Name>
 +
              <Value encrypted="false">20</Value>
 
             </Property>
 
             </Property>
 
         </Properties>
 
         </Properties>

Revision as of 17:09, 8 May 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

Runtime Resource Table

gCubeApp Component RuntimeResource
Time Series / Ecological Modeling GCubeGisViewer / Ecological Modeling suite Geo Server
Time Series / Ecological Modeling GCubeGisViewer / Ecological Modeling suite Geo Network
Time Series Time Series Portlet RStudio
Time Series Time Series Portlet TimeSeries Database
Ecological Modeling Ecological Modeling Service Ecological Modeling Database
Ecological Modeling Ecological Modeling Service Gis 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.

Ecological Modelling Configuration

In order to let Ecological Modelling applications recognize the resource, its profile must be compliant with these rules :

  • Category = Gis
  • Platform/Name = GeoServer

One AccessPoint is validated if :

  • Endpoint EntryName =geoserver
  • Additional Properties :
    • aquamapsDefaultDistributionStyle (String) - mandatory
    • aquamapsDataStore (String) - mandatory
    • aquamapsWorkspace (String) - mandatory

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.

Ecological Modelling Configuration

In order to let Ecological Modelling applications recognize the resource, its profile must be compliant with these rules :

  • Category = Gis
  • Platform/Name = geonetwork

One AccessPoint is validated if :

  • Endpoint EntryName =geonetwork


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>

RStudio Runtime Resource

The RStudio Runtime Resource gives information about where the RStudio instance is deployed.

Description

The Runtime Resource should have "RStudio" name and there will be one Runtime Resource for RStudio instance.

The resource can be registered;

  • at VO level, if the RStudio instance is shared between VREs.
  • at VRE level, if the RStudio instance is VRE dedicated.

The RStudio runtime resource is mandatory if in the VO/VRE are installed application that offers access to RStudio instance.

Fields

Other than required Runtime Resource fields almost one access point is necessary for a RStudio Runtime Resource with entry name "RStudio".

Example

  <Profile>
      <Category>OnlineService</Category>
      <Name>RStudio</Name>
      <Description>RStudio™ is a free and open source integrated development environment (IDE) for R</Description>
      <Platform>
         <Name>RStudio</Name>
         <Version>2</Version>
         <MinorVersion>11</MinorVersion>
         <RevisionVersion>1</RevisionVersion>
         <BuildVersion>0</BuildVersion>
      </Platform>
      <RunTime>
         <HostedOn>http://rstudio.research-infrastructures.eu</HostedOn>
         <GHN UniqueID="" />
         <Status>READY</Status>
      </RunTime>
      <AccessPoint>
         <Description>RStudio</Description>
         <Interface>
            <Endpoint EntryName="RStudio">http://rstudio.research-infrastructures.eu</Endpoint>
         </Interface>
         <AccessData>
            <Username />
            <Password>6vW1u92cpdgHzYAgIurn9w==</Password>
         </AccessData>
      </AccessPoint>
   </Profile>


Time Series Database Runtime Resource

The Time Series Database Runtime Resource gives information about where the Time Series Database is deployed.

Description

The Runtime Resource should have "TimeSeriesDatabase" name and there will be one Runtime Resource for Time Series instance.

The resource can be registered;

  • at VO level, if the Time Series instance is shared between VREs.
  • at VRE level, if the Time Series instance is VRE dedicated.

The Time Series runtime resource is mandatory if in the VO/VRE are installed application that want to access Time Series Database instance.

Fields

Other than required Runtime Resource fields, two access point entry are required:

  • one with entry name "jdbc" with the necessary information for JDBC access to the database
  • one with entry name "readonly" with the readonly access information to the database

Both the access point need a "dbname" property specifying the Time Series db name.

Example

  <Profile>
      <Category>Database</Category>
      <Name>TimeSeriesDatabase</Name>
      <Description />
      <Platform>
         <Name>postgres</Name>
         <Version>9</Version>
         <MinorVersion>1</MinorVersion>
         <RevisionVersion>0</RevisionVersion>
         <BuildVersion>0</BuildVersion>
      </Platform>
      <RunTime>
         <HostedOn>node24.d.d4science.research-infrastructures.eu</HostedOn>
         <GHN UniqueID="" />
         <Status>READY</Status>
      </RunTime>
      <AccessPoint>
         <Description>jdbc conection url</Description>
         <Interface>
            <Endpoint EntryName="jdbc">//node24.d.d4science.research-infrastructures.eu/timeseries</Endpoint>
         </Interface>
         <AccessData>
            <Username>gcube</Username>
            <Password>*************</Password>
         </AccessData>
         <Properties>
            <Property>
               <Name>dbname</Name>
               <Value encrypted="false">timeseries</Value>
            </Property>
         </Properties>
      </AccessPoint>
      <AccessPoint>
         <Description>read only access point</Description>
         <Interface>
            <Endpoint EntryName="readonly">//node24.d.d4science.research-infrastructures.eu/timeseries</Endpoint>
         </Interface>
         <AccessData>
            <Username>readonlyuser</Username>
            <Password>************</Password>
         </AccessData>
         <Properties>
            <Property>
               <Name>dbname</Name>
               <Value encrypted="false">timeseries</Value>
            </Property>
         </Properties>
      </AccessPoint>
   </Profile>

Ecological Modelling Database Runtime Resource

The Ecological Modelling Database Runtime Resource gives information about access to the application database.

Description

The resource can be registered;

  • at VO level, if the Time Series instance is shared between VREs.
  • at VRE level, if the Time Series instance is VRE dedicated.

The Ecological Modelling Database runtime resource is mandatory for each scopes in which an Ecological Modelling application instance is deployed.

Fields

In order to be validated by the application, the Runtime Resource must follow these rules :

  • Category = Database
  • Platform/Name = postgres

Two Access Points compliant with the following rules are required :

  • Internal logic database access point :
    • Entry Name = jdbc
    • user
    • password
    • Additional Properties :
      • schema (String) = aquamaps
      • tableSpacePrefix (String)
      • tableSpaceCount (Integer)
      • maxConnection (Integer)


  • Publisher database access point :
    • Entry Name = jdbc
    • user
    • password
    • Additional Properties :
      • schema (String) = aquamapsPublisher
      • maxConnection (Integer)

Example

  <Profile>
      <Category>Database</Category>
      <Name>AquaMaps Service DataBase</Name>
      <Description />
      <Platform>
         <Name>postgres</Name>
         <Version>8</Version>
         <MinorVersion>1</MinorVersion>
         <RevisionVersion>1</RevisionVersion>
         <BuildVersion>1</BuildVersion>
      </Platform>
      <RunTime>
         <HostedOn>dbtest.research-infrastructures.eu</HostedOn>
         <GHN UniqueID="0b473f00-fa6e-11e0-bb84-8d6426bd0941" />
         <Status>READY</Status>
      </RunTime>
      <AccessPoint>
         <Description>Internal buisness logic entry point</Description>
         <Interface>
            <Endpoint EntryName="jdbc">//dbtest.research-infrastructures.eu:5432/aquamapsorgupdated</Endpoint>
         </Interface>
         <AccessData>
            <Username>utente</Username>
            <Password>UwNMZOK7FlIjGPR+NZCV6w==</Password>
         </AccessData>
         <Properties>
            <Property>
               <Name>schema</Name>
               <Value encrypted="false">aquamaps</Value>
            </Property>
            <Property>
               <Name>maxConnection</Name>
               <Value encrypted="false">20</Value>
            </Property>
            <Property>
               <Name>tableSpaceCount</Name>
               <Value encrypted="false">4</Value>
            </Property>
            <Property>
               <Name>tableSpacePrefix</Name>
               <Value encrypted="false">tbsp_</Value>
            </Property>
         </Properties>
      </AccessPoint>
      <AccessPoint>
         <Description>publisher entry point</Description>
         <Interface>
            <Endpoint EntryName="jdbc">//dbtest.research-infrastructures.eu:5432/apublisherdb</Endpoint>
         </Interface>
         <AccessData>
            <Username>utente</Username>
            <Password>UwNMZOK7FlIjGPR+NZCV6w==</Password>
         </AccessData>
         <Properties>
            <Property>
               <Name>schema</Name>
               <Value encrypted="false">aquamapsPublisher</Value>
            </Property>
            <Property>
               <Name>maxConnection</Name>
               <Value encrypted="false">20</Value>
            </Property>
         </Properties>
      </AccessPoint>
   </Profile>

Gis Database Runtime Resource

The Time Series Database Runtime Resource gives information about where the Time Series Database is deployed.

Description

The Runtime Resource should have "TimeSeriesDatabase" name and there will be one Runtime Resource for Time Series instance.

The resource can be registered;

  • at VO level, if the Time Series instance is shared between VREs.
  • at VRE level, if the Time Series instance is VRE dedicated.

The Time Series runtime resource is mandatory if in the VO/VRE are installed application that want to access Time Series Database instance.

Fields

Other than required Runtime Resource fields, two access point entry are required:

  • one with entry name "jdbc" with the necessary information for JDBC access to the database
  • one with entry name "readonly" with the readonly access information to the database

Both the access point need a "dbname" property specifying the Time Series db name.

Example

  <Profile>
      <Category>Database</Category>
      <Name>TimeSeriesDatabase</Name>
      <Description />
      <Platform>
         <Name>postgres</Name>
         <Version>9</Version>
         <MinorVersion>1</MinorVersion>
         <RevisionVersion>0</RevisionVersion>
         <BuildVersion>0</BuildVersion>
      </Platform>
      <RunTime>
         <HostedOn>node24.d.d4science.research-infrastructures.eu</HostedOn>
         <GHN UniqueID="" />
         <Status>READY</Status>
      </RunTime>
      <AccessPoint>
         <Description>jdbc conection url</Description>
         <Interface>
            <Endpoint EntryName="jdbc">//node24.d.d4science.research-infrastructures.eu/timeseries</Endpoint>
         </Interface>
         <AccessData>
            <Username>gcube</Username>
            <Password>*************</Password>
         </AccessData>
         <Properties>
            <Property>
               <Name>dbname</Name>
               <Value encrypted="false">timeseries</Value>
            </Property>
         </Properties>
      </AccessPoint>
      <AccessPoint>
         <Description>read only access point</Description>
         <Interface>
            <Endpoint EntryName="readonly">//node24.d.d4science.research-infrastructures.eu/timeseries</Endpoint>
         </Interface>
         <AccessData>
            <Username>readonlyuser</Username>
            <Password>************</Password>
         </AccessData>
         <Properties>
            <Property>
               <Name>dbname</Name>
               <Value encrypted="false">timeseries</Value>
            </Property>
         </Properties>
      </AccessPoint>
   </Profile>
Retrieved from "https://wiki.gcube-system.org/index.php?title=RuntimeResourceClassification&oldid=14527"