geOrchestra is a complete Spatial Data Infrastructure solution.
It features a metadata catalog (GeoNetwork 2.10), an OGC server (GeoServer 2.3.2) with fine-grained access control (based on GeoFence), an advanced viewer and editor, an extractor and many more (security and auth system based on proxy/CAS/LDAP, analytics, admin UIs, ...)
More information in the modules README:
- catalog (aka GeoNetwork)
- viewer (aka mapfishapp)
- extractor (aka extractorapp)
- geofence
- simple catalog (aka catalogapp)
- analytics
- ldapadmin
- downloadform
- ogc-server-statistics
- header
See also the release notes.
First, install the required packages:
sudo apt-get install ant ant-optional openjdk-7-jdk python-virtualenv libjai-imageio-core-java
Notes:
- openjdk-6-jdk works too
- GeoServer is known to perform better with Oracle JDK.
- libjai-imageio-core-java is a non-free package
Then clone the repository (either the stable branch or master if you're feeling lucky):
git clone -b 14.01 --recursive https://github.com/georchestra/georchestra.git
...and build:
cd georchestra
./mvn -Dmaven.test.skip=true -Ptemplate install
For testing purposes:
cd config/configurations
cp -r template myprofile
You can then edit files in myprofile to match your needs.
Finally, to build geOrchestra with your own configuration profile:
./mvn -Dmaven.test.skip=true -Dserver=myprofile install
Note: if you're planning to use geOrchestra on the long term, you're better off forking the georchestra/template configuration repository into a private git repository. This way, you'll be able to merge into your branch the changes from upstream.
Example workflow:
cd config/configurations
git clone git@github.com:georchestra/template.git myprofile
cd myprofile
git remote rename origin upstream
(feel free to add a new origin to a private server)
Do whatever updates you want in the master branch, and regularly merge the upstream changes:
git checkout master
git fetch upstream
git merge upstream/master
Note: merge upstream/master into your config if you're using geOrchestra master, or upstream/14.01 if you're using geOrchestra stable.
Read more about the configuration process.
geOrchestra runs well on Debian boxes with Tomcat6 (version 7 might hang your geonetwork, see #418). The minimum system requirement is 2 cores and 4Gb RAM. More is better ;-)
To install the required packages and setup the system, follow the install guide (based on a unique tomcat instance).
Once the system is ready, collect WAR files in a dedicated directory and rename them:
PROFILE=myprofile
VERSION=14.01
mkdir -p /tmp/georchestra_deploy_tmp
cd /tmp/georchestra_deploy_tmp
cp `find ~/.m2/repository/ -name "*-${VERSION}-${PROFILE}.war"` ./
mv security-proxy-${VERSION}-${PROFILE}.war ROOT.war
mv analytics-${VERSION}-${PROFILE}.war analytics-private.war
mv cas-server-webapp-${VERSION}-${PROFILE}.war cas.war
mv catalogapp-${VERSION}-${PROFILE}.war catalogapp-private.war
mv downloadform-${VERSION}-${PROFILE}.war downloadform-private.war
mv extractorapp-${VERSION}-${PROFILE}.war extractorapp-private.war
mv geonetwork-main-${VERSION}-${PROFILE}.war geonetwork-private.war
mv geoserver-webapp-${VERSION}-${PROFILE}.war geoserver-private.war
mv ldapadmin-${VERSION}-${PROFILE}.war ldapadmin-private.war
mv mapfishapp-${VERSION}-${PROFILE}.war mapfishapp-private.war
mv header-${VERSION}-${PROFILE}.war header-private.war
Copy WAR files in Tomcat webapps dir:
sudo service tomcat6 stop
sudo cp -f /tmp/georchestra_deploy_tmp/* /var/lib/tomcat6/webapps
sudo service tomcat6 start
This is the basic idea, but one can fully automate this step with custom crafted deployment scripts. An example is provided in the server-deploy module.