Installation on Unix/Linux¶

Specific CGI Directory¶

In the case your cgi-bin is not located in /usr/lib/ as it is assumed per default, then you can specify a specific target location by using the following option:

./configure --with-cgi-dir=/Lbrary/WebServer/CGI-Executables

This way, when you will run the make install command, the ZOO-Kernel will be deployed in the specified directory (so, /Lbrary/WebServer/CGI-Executables` in this example).

Specific main.cfg location (Optional)¶

Per default, the ZOO-Kernel search for the main.cfg file from its installation directory but, in case you want to store this file in another place, then you can use the --with-etc-dir option so it will search for the main.cfg file in the sysconfdir directory.

For instance, you can define that the directory to store the main.cfg file is the /etc/zoo-project directory, by using the following command:

./configure --with-etc-dir=yes --sysconfdir=/etc/zoo-project

Use a Database Backend (Optional)¶

If you want to share the ongoing informations of running services between various ZOO-Kernel instances then you should use this option: --with-db-backend. This way, both the GetStatus, GetResult and Dismiss requests can be run from any host accessing the same database. Obviously, this will require that the ZOO-Kernel is able to access the Database server. To learn how to configure this connection and how to create this database please refer to [1] and [2] respectively.

To create a new database to be used by the ZOO-Kernel, you have to load the schema.sql file. For instance, you may run the following:

createdb zoo_project
psql zoo_project -f zoo-project/zoo-kernel/sql/schema.sql

Metadata Database (Optional)¶

It is possible to use a PostgreSQL database to store metadata information about WPS Services. This support is optional and require to be activated by using the --with-metadb=yes option.

To create the database for storing the metadata informations about the WPS Services, you may use the following command:

createdb zoo_metadb
psql zoo_metadb -f zoo-project/zoo-kernel/sql/zoo_collectiondb.sql

In case you want to convert an existing zcfg file then, you can use the zcfg2sql tool from the command line. It can be found in thirds/zcfg2sql and can be build simply by running the make command. After compilation you only need to give it the path of the zcfg file you want to obtain the SQL queries required to store the metadata informations in the database rather than in zcfg file.

For instance you may use the following command:

#Direct import in the zoo_metadb database
./zcfg2sql /Path/To/MyZCFGs/myService.zcfg | psql zoo_metadb
#Create a SQL file for a futur import
./zcfg2sql /Path/To/MyZCFGs/myService.zcfg > myService.sql

YAML Support (Optional)¶

If yaml.h file is not found in your /usr/include directory and libyaml.so is not found in /usr/lib, a --with-yaml option can be used to specify its location. For instance, if the header file lies in /usr/local/include and the shared library is located in /usr/local/lib, you may use the following command:

$ ./configure --with-yaml=/usr/local

FastCGI Support (Required)¶

If your FastCGI library is not available in the default search path, a --with-fastcgi option can be used to specify its location. For instance, if libfcgi.so lies in /usr/local/lib which is not in your LD_SEARCH_PATH, you may use the following command:

$ ./configure --with-fastcgi=/usr/local

GDAL Support (Required)¶

If gdal-config program is not found in your PATH, a --with-gdal-config option can be used to specify its location. For instance, if gdal-config lies in /usr/local/bin which is not in your PATH, you may use the following command:

$ ./configure --with-gdal-config=/usr/local/bin/gdal-config

GEOS Support (Optional)¶

If geos-config program is not found in your PATH, a --with-geosconfig option can be used to specify its location. For instance, if geos-config lies in /usr/local/bin which is not in your PATH, you may use the following command:

$ ./configure --with-geosconfig=/usr/local/bin/geos-config

CGAL Support (Optional)¶

If CGAL/Delaunay_triangulation_2.h program is not found in your /usr/include directory, a --with-cgal option can be used to specify its location. For instance, if the file lies in /usr/local/include which is not in your PATH, you may use the following command:

$ ./configure --with-cgal=/usr/local

MapServer Support (Optional)¶

In order to activate the WMS, WFS and WCS output support using MapServer, the --with-mapserver option must be used. The path to mapserver-config which is located in the source code of MapServer must also be set, using the following command:

$ ./configure --with-mapserver=/path/to/your/mapserver_config/

Read more about the Optional MapServer support.

XML2 Support (Required)¶

If xml2-config program is not found in PATH, a –with-xml2config option can be used to specify its location. For instance, if xml2-config is installed in /usr/local/bin which is not in PATH, you may use the following command:

$ ./configure --with-xml2config=/usr/local/bin/xml2-config

OGC API - Processing Support (Optional)¶

In case you want to activate the support for OGC API - Processing, you can do so by using the –with-json: You will then need to coy the oas.cfg file in the same directory as your main.cfg. For instance, one may use the following command:

$ ./configure --with-json=/usr/

Python Support (Optional)¶

The --with-python=yes option is required to activate the ZOO-Kernel Python support, using the following command:

$ ./configure --with-python=yes

This assumes that python-config is found in your PATH. If not, then you can specify the Python installation directory using the following command (with Python installed in the /usr/local directory):

$ ./configure --with-python=/usr/local

$ ./configure --with-pyvers=2.7

JavaScript Support (Optional)¶

In order to activate the JavaScript support for ZOO-Kernel, the --with-js=yes configure option must be specified. If you are using a “Debian-like” GNU/Linux distribution then dpkg will be used to detect if the required packages are installed and you don’t have to specify anything here. The following command is only needed (assuming that js_api.h and libmozjs.so are found in default directories):

$ ./configure --with-js=yes

If you want to use a custom installation of SpiderMonkey , or if you are not using a Debian packaging system, then you’ll have to specify the directory where it is installed. For instance, if SpiderMonkey is in /usr/local/, then the following command must be used:

$ ./configure --with-js=/usr/local

PHP Support (Optional)¶

The --with-php=yes option is required to activate the ZOO-Kernel PHP support`, using the following command:

$ ./configure --with-php=yes

This assumes that php-config can be found in the <PATH>/bin directory . So, supposing the your php-config can be found in /usr/local/bin, then use the following command:

$ ./configure --with-php=/usr/local

Java Support (Optional)¶

In order to activate the Java support for ZOO-Kernel, the –with-java configure option must be specified and sets the installation path of your Java SDK. For instance, if Java SDK is installed in the /usr/lib/jvm/java-6-sun-1.6.0.22/ directory, then the following command can be used:

$ ./configure --with-java=/usr/lib/jvm/java-6-sun-1.6.0.22/

This assumes that the include/linux and jre/lib/i386/client/ subdirectories exist in /usr/lib/jvm/java-6-sun-1.6.0.22/, and that the include/linux directory contains the jni.h headers file and that the jre/lib/i386/client/ directory contains the libjvm.so file.

$ ./configure --with-java=macos

Perl Support (Optional)¶

The --with-perl=yes option can be used for activating the ZOO-Kernel Perl support, as follow:

$ ./configure --with-perl=yes

This assumes that perl is found in your PATH. For instance, if Perl is installed in /usr/local and /usr/local/bin is not found in your PATH, then the following command can be used (this assumes that /usr/local/bin/perl exists):

$ ./configure --with-perl=/usr/local

Orfeo Toolbox Support (Optional)¶

In order to activate the optional Orfeo Toolbox support, the --with-otb option must be used, using the following command:

$ ./configure --with-otb=/path/to/your/otb/

Read more about the Optional Orfeo Toolbox support.

SAGA GIS Support (Optional)¶

In order to activate the optional SAGA GIS support, the –with-saga option must be used, using the following command:

$ ./configure --with-saga=/path/to/your/saga/

Read more about the Optional SAGA GIS support.

Translation support (Optional)¶

The ZOO-Kernel is able to translate the messages it produces in different natural languages. This requires that you download the messages file translated in your language, if any. Then, for this translation support to work, you have to generate manually the requested file on your system. For instance for the French translation, you may use the following command:

msgfmt messagespo_fr_FR.utf8.po -o /usr/share/locale/fr/LC_MESSAGES/zoo-kernel.mo

The ZOO-Kernel is also able to handle translation of ZOO-Services. Please, refer to this document for more details on the procedure to add new ZOO-Service translation files.