wiki:InstallFromRPM

Version 2 (modified by pbaumann, 22 months ago) (diff)

--

rasdaman RPM installation

This page describes installation of rasdaman RPM packages.

Currently, CentOS 7 and 6 are supported. The rasdaman packages are built and hosted at Copr Fedora.

Installation

  1. Set OSVERSION to 6 or 7, depending on your CentOS version:
    export OSVERSION=7
    export TOMCAT=tomcat
    [ $OSVERSION -eq 6 ] && TOMCAT=tomcat6
    
  2. Add the rasdaman repository to yum:
    cd /etc/yum.repos.d
    sudo curl "https://copr.fedoraproject.org/coprs/misev/rasdaman/repo/epel-$OSVERSION/misev-rasdaman-epel-$OSVERSION.repo" -o rasdaman.repo
    else
    sudo yum update
    
  3. Rasdaman packages should be available now via yum:
    yum search rasdaman
    
    Output:
    rasdaman.x86_64 : rasdaman - Raster Data Manager
    rasdaman-debuginfo.x86_64 : Debug information for package rasdaman
    rasdaman-devel.x86_64 : rasdaman headers
    rasdaman-docs.noarch : Documentation for rasdaman
    rasdaman-examples.noarch : Documentation for rasdaman
    rasdaman-petascope.noarch : Petascope is an add-in to the rasdaman
    rasdaman-rasdaview.x86_64 : WxWidgets based GUI client for rasdaman
    rasdaman-raswct.noarch : Rasdaman Web Client Toolkit based on JavaScript
    rasdaman-rasgeo.x86_64 : rasgeo is an add-in for GDAL-based image file import
    
  4. Add the EPEL repository to yum (official page):
    sudo yum install epel-release
    
  5. CentOS 6 only: add this ELGIS 6 Copr for up-to-date boost libraries:
    cd /etc/yum.repos.d
    sudo curl "https://copr.fedoraproject.org/coprs/pali/el6gis/repo/epel-6/pali-el6gis-epel-6.repo" -O
    sudo yum update
    
  6. Install packages (add more packages as necessary), and turn services on:
    sudo yum install rasdaman rasdaman-petascope rasdaman-docs
    sudo chkconfig postgresql on
    sudo chkconfig rasdaman on
    
  7. Now that rasdaman is installed we proceed to initializing and starting the server. First postgresql (if newly installed now as a dependency of rasdaman) should be initialized:
    sudo service postgresql initdb
    sudo service postgresql start
    
  8. Next let's initialize and start rasdaman:
    sudo service rasdaman initdb
    sudo service rasdaman start
    
  9. Check that everything is fine:
    rasql -q 'select c from RAS_COLLECTIONNAMES as c' --out string
    
    Typical output:
    rasql: rasdaman query tool v1.0, rasdaman v9.0.0 -- generated on 02.07.2015 08:44:56.
    opening database RASBASE at localhost:7001...ok
    Executing retrieval query...ok
    Query result collection has 0 element(s):
    rasql done.
    
  10. Let's proceed to initializing petascope, the OGC frontend component of rasdaman:
    sudo service rasdaman initpetascopedb
    sudo service $TOMCAT restart
    
  11. Check that petascope is initialized properly, typically at this URL:
    http://localhost:8080/rasdaman/ows
    
  12. To ingest data with wcst_import.sh, a flexible WCS-T python ingestion tool, in addition the glob2 python package needs to be installed:
    sudo easy_install glob2
    

Updating

The RPMs are updated whenever a new version of rasdaman is released. To fetch the updated rasdaman run:

sudo yum update
sudo service rasdaman restart

Sometimes the database schemas may need to be updated (version changelogs indicate if this is necessary):

sudo service rasdaman stop
sudo service rasdaman updatedb
sudo service rasdaman updatepetascopedb
sudo service rasdaman start
sudo service $TOMCAT restart

Management

Services

A rasdaman service script allows to start/stop rasdaman, e.g.

service rasdaman start
service rasdaman stop
service rasdaman status
...

Similarly there are tomcat/tomcat6 and postgresql service scripts.

The rasdaman database RASBASE is managed in an SQLite file /var/lib/rasdaman/data/RASBASE; blob files are in /var/lib/rasdaman/data/ so expect this directory to grow as data is imported. It is recommended to move this directory to a sufficiently large partition and create a symlink here.

Logs

Rasdaman server logs can be found in /var/log/rasdaman:

serverName.pid.log server worker logs, usually named N*.pid.log; ls -ltr is a useful command to see the latest modified logs at the bottom
rasmgr.pid.log server manager log
/var/lib/rasdaman/startup.log server manager startup log

Further relevant log locations are

postgresql /var/lib/pgsql/data/pg_log
tomcat petascope log messages can be found in:
CentOS 7: /usr/share/tomcat/petascope.log
CentOS 6: /var/log/tomcat6/catalina.out

Configuration files

Rasdaman configuration files can be found in /etc/rasdaman

rasmgr.conf allows fine-tunning the rasdaman servers, e.g. number of servers, names, database connection, etc.
petascope.properties set petascope properties, e.g. database/rasdaman connection details, CRS resolver URLs, various feature options
log4j.properties petascope logging configuration
wms_service.properties petascope properties specifically for the WMS service
~/.rasdaman/rasconnect in case the rasgeo (rasimport/raserase) component is used; has to be installed manually, see example configuration file [wiki;Install#rasgeo here]

Further relevant configuration files are

postgresql /var/lib/pgsql/data/{postgresql.conf,pg_hba.conf}
tomcat /etc/tomcat/ or /etc/tomcat6/

Documentation

Rasdaman documentation can be found in /usr/share/rasdaman/doc.

A petascope ingestion tool, which can flexibly insert geo data via the WCS-T interface of petascope can be found in /usr/share/rasdaman/wcst_import (can be invoked simply by wcst_import.sh).