Changes between Version 2 and Version 3 of InstallFromRPM


Ignore:
Timestamp:
Dec 18, 2015 4:33:38 PM (22 months ago)
Author:
dmisev
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • InstallFromRPM

    v2 v3  
    11111. Set `OSVERSION` to 6 or 7, depending on your CentOS version:
    1212{{{
     13#!sh
    1314export OSVERSION=7
    1415export TOMCAT=tomcat
     
    17181. Add the rasdaman repository to yum:
    1819{{{
     20#!sh
    1921cd /etc/yum.repos.d
    2022sudo curl "https://copr.fedoraproject.org/coprs/misev/rasdaman/repo/epel-$OSVERSION/misev-rasdaman-epel-$OSVERSION.repo" -o rasdaman.repo
     
    24261. Rasdaman packages should be available now via yum:
    2527{{{
     28#!sh
    2629yum search rasdaman
    2730}}}
    2831 Output:
    2932{{{
     33#!sh
    3034rasdaman.x86_64 : rasdaman - Raster Data Manager
    3135rasdaman-debuginfo.x86_64 : Debug information for package rasdaman
     
    40441. Add the EPEL repository to yum ([https://fedoraproject.org/wiki/EPEL official page]):
    4145{{{
     46#!sh
    4247sudo yum install epel-release
    4348}}}
    44491. CentOS 6 only: add this [https://copr.fedoraproject.org/coprs/pali/el6gis/ ELGIS 6 Copr] for up-to-date boost libraries:
    4550{{{
     51#!sh
    4652cd /etc/yum.repos.d
    4753sudo curl "https://copr.fedoraproject.org/coprs/pali/el6gis/repo/epel-6/pali-el6gis-epel-6.repo" -O
     
    50561. Install packages (add more packages as necessary), and turn services on:
    5157{{{
     58#!sh
    5259sudo yum install rasdaman rasdaman-petascope rasdaman-docs
    5360sudo chkconfig postgresql on
     
    56631. 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:
    5764{{{
     65#!sh
    5866sudo service postgresql initdb
    5967sudo service postgresql start
     
    61691. Next let's initialize and start rasdaman:
    6270{{{
     71#!sh
    6372sudo service rasdaman initdb
    6473sudo service rasdaman start
     
    66751. Check that everything is fine:
    6776{{{
     77#!sh
    6878rasql -q 'select c from RAS_COLLECTIONNAMES as c' --out string
    6979}}}
    7080 Typical output:
    7181{{{
     82#!sh
    7283rasql: rasdaman query tool v1.0, rasdaman v9.0.0 -- generated on 02.07.2015 08:44:56.
    7384opening database RASBASE at localhost:7001...ok
     
    78891. Let's proceed to initializing petascope, the OGC frontend component of rasdaman:
    7990{{{
     91#!sh
    8092sudo service rasdaman initpetascopedb
    8193sudo service $TOMCAT restart
     
    83951. Check that petascope is initialized properly, typically at this URL:
    8496{{{
     97#!sh
    8598http://localhost:8080/rasdaman/ows
    8699}}}
    871001. To ingest data with `wcst_import.sh`, a flexible WCS-T python ingestion tool, in addition the `glob2` python package needs to be installed:
    88101{{{
     102#!sh
    89103sudo easy_install glob2
    90104}}}
     
    94108The RPMs are updated whenever a new version of rasdaman is released. To fetch the updated rasdaman run:
    95109{{{
     110#!sh
    96111sudo yum update
    97112sudo service rasdaman restart
     
    99114Sometimes the database schemas may need to be updated (version changelogs indicate if this is necessary):
    100115{{{
     116#!sh
    101117sudo service rasdaman stop
    102118sudo service rasdaman updatedb
     
    112128A `rasdaman` service script allows to start/stop rasdaman, e.g.
    113129{{{
     130#!sh
    114131service rasdaman start
    115132service rasdaman stop