Changes between Version 15 and Version 16 of InstallFromSource


Ignore:
Timestamp:
Dec 30, 2015 3:33:31 PM (21 months ago)
Author:
pbaumann
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • InstallFromSource

    v15 v16  
    204204}}}
    205205
    206 == Initialize petascope ==
    207 
    208 Petascope is the geo Web service frontend of rasdaman. It adds geo semantics on top of arrays, thereby enabling regular and irregular grids based on the [http://external.opengeospatial.org/twiki_public/CoveragesDWG/WebHome OGC coverage standards]. Following successful deployment, petascope accepts OGC W*S requests at URL `http://localhost:8080/rasdaman/ows`.
    209 
    210 For more details, see the [wiki:PetascopeUserGuide user guide] and [wiki:PetascopeDevGuide developer guide].
    211 
    212 === PostgreSQL ===
    213 
    214 To implement the geo semantics, petascope uses a relational database for the geo-related metadata. Currently, only PostgreSQL is supported; for the future, support of SQLite is planned (in parallel to the rasdaman array engine). This is how to set up PostgreSQL for use by petascope:
    215 
    216 1. [wiki:rasdamanStoragePostgreSQL Prepare PostgreSQL for use with rasdaman]
    217 
    218 1. Add a user to PostgreSQL for petascope:
    219 {{{
    220 sudo -u postgres createuser -s petauser -P
    221 }}}
    222 1. Set the `metadata_user` and `metadata_pass` variables in `$RMANHOME/etc/petascope.properties` to the above user and password.
    223 1. make sure PostgreSQL needs to be running
    224 1. Initialize the petascope database schema:
    225 {{{
    226 #!sh
    227 update_petascopedb.sh
    228 }}}
    229 
    230 === Running the Servlet ===
    231 
    232 As petascope is implemented as a Java servlet it needs a servlet container for its operations. Two alternatives are available:
    233 * separately install some servlet container, like Tomcat, and deploy petascope there; In case of problems, consult the servlet container log files (such as `/var/log/tomcat7/catalina.out` on Debian 8 and `/usr/share/tomcat/petascope.log` on CentOS 7).
    234 * run the petascope service directly, by way of the embedded servlet container, jetty; More information on how to use this option can be found on [wiki:PetascopeEmbedded this page].
    235 
    236 == Initialize SECORE ==
    237 
    238 SECORE (Semantic Coordinate Reference System Resolver) is a service that maps CRS URLs to CRS definitions. This component, which is part of the standard rasdaman distribution, is used by the [http://www.opengeospatial.com Open Geospatial Consortium] (OGC) for operating their official CRS resolver.
    239 
    240 SECORE, being a servlet like petascope, gets installed automatically unless `--disable-java` is specified at `configure`. The deployment directory of all war files can be set during the `configure` step with the `--with-wardir=DIR` option.
    241 
    242 For further details on SECORE management, security and troubleshooting see the [wiki:SecoreAdministration administration] and [wiki:SecoreDevGuide developer guide] pages.
     206== Initialize geo service support ==
     207
     208Petascope is the geo Web service frontend of rasdaman. It adds geo semantics on top of arrays, thereby enabling regular and irregular grids based on the [http://external.opengeospatial.org/twiki_public/CoveragesDWG/WebHome OGC coverage standards].
     209To activate this functionality, perform the steps of the [wiki:PetascopeInstallGuide petascope installation guide].
     210
     211Following successful deployment, petascope accepts OGC W*S requests at URL `http://localhost:8080/rasdaman/ows`.
    243212
    244213