[659] | 1 | .. _install-installation: |
---|
| 2 | |
---|
| 3 | Installation on Unix/Linux |
---|
[696] | 4 | ========================== |
---|
[659] | 5 | |
---|
[696] | 6 | To build and install ZOO-Project on your Web Server you will need 4 |
---|
| 7 | steps : |
---|
| 8 | |
---|
[713] | 9 | .. contents:: |
---|
| 10 | :local: |
---|
| 11 | :depth: 1 |
---|
| 12 | :backlinks: top |
---|
[696] | 13 | |
---|
[713] | 14 | |
---|
[696] | 15 | Build cgic |
---|
| 16 | ---------- |
---|
| 17 | |
---|
| 18 | Run the following commands from the ``thirds/cgic`` directory to build |
---|
| 19 | the cgic library. |
---|
| 20 | |
---|
| 21 | :: |
---|
| 22 | |
---|
| 23 | cd thirds/cgic |
---|
| 24 | make |
---|
| 25 | |
---|
| 26 | The cgic library originaly come from `http://www.boutell.com/cgic |
---|
| 27 | <http://www.boutell.com/cgic>`_. |
---|
| 28 | |
---|
| 29 | .. warning:: |
---|
| 30 | |
---|
| 31 | You may need to edit the ``Makefile`` in case you are using a 64 bits |
---|
| 32 | platform for building and your fcgi library is not located in ``/usr/lib64``. |
---|
| 33 | |
---|
[714] | 34 | Install ZOO-Kernel |
---|
| 35 | ------------------ |
---|
[696] | 36 | |
---|
| 37 | |
---|
[659] | 38 | For the impatient |
---|
[696] | 39 | ................. |
---|
[659] | 40 | |
---|
| 41 | Run the following commands from the directory where you :ref:`install-download` and extracted the ZOO Kernel source code in order to build the ``zoo_loader.cgi`` CGI program with default options. |
---|
| 42 | |
---|
| 43 | :: |
---|
| 44 | |
---|
[696] | 45 | cd zoo-project/zoo-kernel |
---|
[659] | 46 | autoconf |
---|
| 47 | ./configure |
---|
| 48 | make |
---|
[696] | 49 | make install |
---|
[659] | 50 | |
---|
[696] | 51 | This should produce executables for the *zoo_loader.cgi* CGI program |
---|
| 52 | (located per default in ``/usr/lib/cgi-bin/``) and a shared library |
---|
| 53 | ``libzoo_service`` (located per default in ``/usr/local/lib``). |
---|
[659] | 54 | |
---|
| 55 | .. warning:: |
---|
| 56 | |
---|
[696] | 57 | Edit ZOO-Kernel installation settings in the ``main.cfg`` file (set |
---|
| 58 | ``tmpPath`` and ``tmpUrl`` to fit your web server configuration). |
---|
[659] | 59 | |
---|
| 60 | |
---|
[696] | 61 | Configure options |
---|
| 62 | ................. |
---|
[659] | 63 | |
---|
[714] | 64 | This section provides information on :ref:`kernel_index` configure options. It is recommanded to also read the :ref:`kernel_config` section for configuration technical details. |
---|
| 65 | |
---|
| 66 | |
---|
| 67 | Here is the list of available options in the same order as returned by |
---|
| 68 | ``./configure --help`` command: |
---|
| 69 | |
---|
[713] | 70 | .. contents:: |
---|
| 71 | :local: |
---|
| 72 | :depth: 2 |
---|
| 73 | :backlinks: top |
---|
| 74 | |
---|
| 75 | Specific CGI Directory |
---|
| 76 | ********************** |
---|
[659] | 77 | |
---|
[713] | 78 | In the case your ``cgi-bin`` is not located in ``/usr/lib/`` as it is |
---|
| 79 | assumed per default, then you can specify a specific target location |
---|
| 80 | by using the following option: |
---|
[659] | 81 | |
---|
[713] | 82 | .. code:: |
---|
[659] | 83 | |
---|
[713] | 84 | ./configure --with-cgi-dir=/Lbrary/WebServer/CGI-Executables |
---|
[659] | 85 | |
---|
[713] | 86 | This way, when you will run the ``make install`` command, the |
---|
| 87 | ZOO-Kernel will be deployed in the specified directory (so, |
---|
| 88 | `/Lbrary/WebServer/CGI-Executables`` in this example). |
---|
[659] | 89 | |
---|
[784] | 90 | Specific main.cfg location (Optional) |
---|
| 91 | ************************************** |
---|
| 92 | |
---|
| 93 | Per default, the ZOO-Kernel search for the ``main.cfg`` file from its |
---|
| 94 | installation directory but, in case you want to store this file in |
---|
| 95 | another place, then you can use the ``--with-etc-dir`` option so it |
---|
[806] | 96 | will search for the ``main.cfg`` file in the ``sysconfdir`` directory. |
---|
[784] | 97 | |
---|
| 98 | For instance, you can define that the directory to store the |
---|
| 99 | ``main.cfg`` file is the ``/etc/zoo-project`` directory, by using the |
---|
| 100 | following command: |
---|
| 101 | |
---|
| 102 | .. code:: |
---|
| 103 | |
---|
| 104 | ./configure --with-etc-dir=yes --sysconfdir=/etc/zoo-project |
---|
| 105 | |
---|
| 106 | |
---|
[711] | 107 | .. _zoo_install_db_backend: |
---|
| 108 | |
---|
[700] | 109 | Use a Database Backend (Optional) |
---|
[713] | 110 | ********************************** |
---|
[659] | 111 | |
---|
[700] | 112 | If you want to share the ongoing informations of running services |
---|
[713] | 113 | between various ZOO-Kernel instances then you should use this |
---|
| 114 | option: ``--with-db-backend``. This way, both the *GetStatus*, |
---|
| 115 | *GetResult* and *Dismiss* requests can be run from any host accessing |
---|
| 116 | the same database. Obviously, this will require that the ZOO-Kernel is |
---|
| 117 | able to access the Database server. To learn how to configure this |
---|
| 118 | connection and how to create this database please refer to :ref:`[1] |
---|
| 119 | <zoo_activate_db_backend>` and :ref:`[2] <zoo_create_db_backend>` |
---|
| 120 | respectively. |
---|
[700] | 121 | |
---|
| 122 | .. note:: |
---|
| 123 | By now, the ZOO-Kernel is not able to handle correctly the |
---|
| 124 | *Dismiss* request from any host. Nevertheless, it will provide |
---|
| 125 | valid response from any host, but only the host which is really |
---|
| 126 | handling the service will be able to stop it and remove all the |
---|
| 127 | linked files. |
---|
| 128 | |
---|
[722] | 129 | .. _zoo_create_db_backend: |
---|
| 130 | |
---|
| 131 | To create a new database to be used by the ZOO-Kernel, you have |
---|
| 132 | to load the `schema.sql |
---|
| 133 | <http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/sql/schema.sql>`_ |
---|
| 134 | file. For instance, you may run the following: |
---|
| 135 | |
---|
| 136 | .. code:: |
---|
| 137 | |
---|
| 138 | createdb zoo_project |
---|
| 139 | psql zoo_project -f zoo-project/zoo-kernel/sql/schema.sql |
---|
| 140 | |
---|
| 141 | .. note:: |
---|
| 142 | You can choose another schema to store ZOO-Kernel specific |
---|
| 143 | informations. In such a case, you would need to edit the |
---|
| 144 | schema.sql file to uncomment line `33 |
---|
| 145 | <http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/sql/schema.sql#L33>`_ |
---|
| 146 | and `34 |
---|
| 147 | <http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/sql/schema.sql#L34>`_. |
---|
| 148 | |
---|
[904] | 149 | Metadata Database (Optional) |
---|
| 150 | ***************************** |
---|
[722] | 151 | |
---|
[904] | 152 | .. _zoo_create_metadb: |
---|
[722] | 153 | |
---|
[904] | 154 | It is possible to use a PostgreSQL database to store metadata |
---|
| 155 | information about WPS Services. This support is optional and require |
---|
| 156 | to be activated by using the ``--with-metadb=yes`` option. |
---|
| 157 | |
---|
| 158 | To create the database for storing the metadata informations about the |
---|
| 159 | WPS Services, you may use the following command: |
---|
| 160 | |
---|
| 161 | .. code:: |
---|
| 162 | |
---|
| 163 | createdb zoo_metadb |
---|
| 164 | psql zoo_metadb -f zoo-project/zoo-kernel/sql/zoo_collectiondb.sql |
---|
| 165 | |
---|
| 166 | In case you want to convert an existing zcfg file then, you can use |
---|
| 167 | the ``zcfg2sql`` tool from the command line. |
---|
| 168 | |
---|
[714] | 169 | YAML Support (Optional) |
---|
| 170 | ************************ |
---|
[700] | 171 | |
---|
[714] | 172 | If ``yaml.h`` file is not found in your ``/usr/include`` directory and |
---|
| 173 | ``libyaml.so`` is not found in ``/usr/lib``, a ``--with-yaml`` option |
---|
[904] | 174 | can be used to specify its location. For instance, if the header file |
---|
[714] | 175 | lies in ``/usr/local/include`` and the shared library is located in |
---|
| 176 | ``/usr/local/lib``, you may use the following command: |
---|
[700] | 177 | |
---|
[714] | 178 | :: |
---|
[713] | 179 | |
---|
[714] | 180 | $ ./configure --with-yaml=/usr/local |
---|
| 181 | |
---|
| 182 | |
---|
| 183 | FastCGI Support (Required) |
---|
| 184 | *************************** |
---|
| 185 | |
---|
| 186 | If your FastCGI library is not available in the default search path, a |
---|
| 187 | ``--with-fastcgi`` option can be used to specify its location. For |
---|
| 188 | instance, if ``libfcgi.so`` lies in ``/usr/local/lib`` which is not in |
---|
| 189 | your ``LD_SEARCH_PATH``, you may use the following command: |
---|
| 190 | |
---|
| 191 | :: |
---|
| 192 | |
---|
| 193 | $ ./configure --with-fastcgi=/usr/local |
---|
| 194 | |
---|
| 195 | |
---|
| 196 | |
---|
[713] | 197 | GDAL Support (Required) |
---|
| 198 | ************************ |
---|
| 199 | |
---|
| 200 | If gdal-config program is not found in your ``PATH``, a |
---|
| 201 | ``--with-gdal-config`` option can be used to specify its location. For |
---|
| 202 | instance, if ``gdal-config`` lies in ``/usr/local/bin`` which is not in |
---|
[714] | 203 | your ``PATH``, you may use the following command: |
---|
[713] | 204 | |
---|
| 205 | :: |
---|
| 206 | |
---|
| 207 | $ ./configure --with-gdal-config=/usr/local/bin/gdal-config |
---|
| 208 | |
---|
[714] | 209 | |
---|
| 210 | GEOS Support (Optional) |
---|
| 211 | ************************ |
---|
| 212 | |
---|
| 213 | If ``geos-config`` program is not found in your ``PATH``, a |
---|
| 214 | ``--with-geosconfig`` option can be used to specify its location. For |
---|
| 215 | instance, if ``geos-config`` lies in ``/usr/local/bin`` which is not in |
---|
| 216 | your ``PATH``, you may use the following command: |
---|
| 217 | |
---|
| 218 | :: |
---|
| 219 | |
---|
| 220 | $ ./configure --with-geosconfig=/usr/local/bin/geos-config |
---|
| 221 | |
---|
| 222 | |
---|
| 223 | CGAL Support (Optional) |
---|
| 224 | ************************ |
---|
| 225 | |
---|
| 226 | If ``CGAL/Delaunay_triangulation_2.h`` program is not found in your |
---|
| 227 | ``/usr/include`` directory, a ``--with-cgal`` option can be used to |
---|
| 228 | specify its location. For instance, if the file lies in |
---|
| 229 | ``/usr/local/include`` which is not in your PATH, you may use the |
---|
| 230 | following command: |
---|
| 231 | |
---|
| 232 | :: |
---|
| 233 | |
---|
| 234 | $ ./configure --with-cgal=/usr/local |
---|
| 235 | |
---|
| 236 | |
---|
| 237 | |
---|
| 238 | MapServer Support (Optional) |
---|
| 239 | ***************************** |
---|
| 240 | |
---|
| 241 | |
---|
| 242 | In order to activate the WMS, WFS and WCS output support using |
---|
| 243 | MapServer, the ``--with-mapserver`` option must be used. The path to |
---|
| 244 | ``mapserver-config`` which is located in the source code of MapServer |
---|
| 245 | must also be set, using the following command: |
---|
| 246 | |
---|
| 247 | :: |
---|
| 248 | |
---|
| 249 | $ ./configure --with-mapserver=/path/to/your/mapserver_config/ |
---|
| 250 | |
---|
| 251 | |
---|
| 252 | Read more about the :ref:`kernel-mapserver`. |
---|
| 253 | |
---|
[713] | 254 | XML2 Support (Required) |
---|
| 255 | ************************ |
---|
| 256 | |
---|
| 257 | 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: |
---|
| 258 | |
---|
| 259 | :: |
---|
| 260 | |
---|
| 261 | $ ./configure --with-xml2config=/usr/local/bin/xml2-config |
---|
| 262 | |
---|
[696] | 263 | Python Support (Optional) |
---|
[713] | 264 | ************************** |
---|
[659] | 265 | |
---|
[696] | 266 | The ``--with-python=yes`` option is required to activate the :ref:`kernel_index` Python support, using the following command: |
---|
[659] | 267 | |
---|
[696] | 268 | :: |
---|
[659] | 269 | |
---|
[696] | 270 | $ ./configure --with-python=yes |
---|
[659] | 271 | |
---|
[696] | 272 | This assumes that python-config is found in your ``PATH``. If not, |
---|
| 273 | then you can specify the Python installation directory using the |
---|
| 274 | following command (with Python installed in the ``/usr/local`` |
---|
| 275 | directory): |
---|
[659] | 276 | |
---|
[696] | 277 | :: |
---|
[659] | 278 | |
---|
[696] | 279 | $ ./configure --with-python=/usr/local |
---|
[659] | 280 | |
---|
| 281 | |
---|
[696] | 282 | Python Version |
---|
[713] | 283 | ############## |
---|
[659] | 284 | |
---|
[696] | 285 | If multiple Python versions are available and you want to use a |
---|
| 286 | specific one, then you can use the ``--with-pyvers`` option as shown |
---|
| 287 | bellow: |
---|
[659] | 288 | |
---|
[696] | 289 | :: |
---|
[659] | 290 | |
---|
[696] | 291 | $ ./configure --with-pyvers=2.7 |
---|
[659] | 292 | |
---|
| 293 | |
---|
[714] | 294 | .. _js-support: |
---|
| 295 | |
---|
| 296 | JavaScript Support (Optional) |
---|
| 297 | ****************************** |
---|
| 298 | |
---|
| 299 | In order to activate the JavaScript support for ZOO-Kernel, |
---|
| 300 | the ``--with-js=yes`` configure option must be specified. If you are using |
---|
| 301 | a "Debian-like" GNU/Linux distribution then dpkg will be used to |
---|
| 302 | detect if the required packages are installed and you don't have to |
---|
| 303 | specify anything here. The following command is only needed (assuming |
---|
| 304 | that js_api.h and libmozjs.so are found in default directories): |
---|
| 305 | |
---|
| 306 | |
---|
| 307 | :: |
---|
| 308 | |
---|
| 309 | $ ./configure --with-js=yes |
---|
| 310 | |
---|
| 311 | If you want to use a custom installation of `SpiderMonkey |
---|
| 312 | <https://developer.mozilla.org/en/SpiderMonkey>`__ , or if you are not |
---|
| 313 | using a Debian packaging system, then you'll have to specify the |
---|
| 314 | directory where it is installed. For instance, if SpiderMonkey is in |
---|
| 315 | ``/usr/local/``, then the following command must be used: |
---|
| 316 | |
---|
| 317 | :: |
---|
| 318 | |
---|
| 319 | $ ./configure --with-js=/usr/local |
---|
| 320 | |
---|
| 321 | |
---|
[696] | 322 | PHP Support (Optional) |
---|
[713] | 323 | *********************** |
---|
[659] | 324 | |
---|
[696] | 325 | The ``--with-php=yes`` option is required to activate the |
---|
| 326 | :ref:`kernel_index` PHP support`, using the following command: |
---|
[659] | 327 | |
---|
[696] | 328 | :: |
---|
[659] | 329 | |
---|
[696] | 330 | $ ./configure --with-php=yes |
---|
[659] | 331 | |
---|
[696] | 332 | This assumes that ``php-config`` can be found in the ``<PATH>/bin`` |
---|
| 333 | directory . So, supposing the your ``php-config`` can be found in |
---|
| 334 | ``/usr/local/bin``, then use the following command: |
---|
[659] | 335 | |
---|
[696] | 336 | :: |
---|
[659] | 337 | |
---|
[696] | 338 | $ ./configure --with-php=/usr/local |
---|
[659] | 339 | |
---|
[696] | 340 | .. warning:: |
---|
| 341 | ZOO-Kernel optional PHP support requires a local PHP Embedded installation. Read more `here <http://zoo-project.org/trac/wiki/ZooKernel/Embed/PHP>`__. |
---|
[659] | 342 | |
---|
| 343 | |
---|
[696] | 344 | Java Support (Optional) |
---|
[713] | 345 | ************************ |
---|
[659] | 346 | |
---|
[696] | 347 | In order to activate the Java support for ZOO-Kernel, the |
---|
| 348 | `--with-java` configure option must be specified and sets the |
---|
| 349 | installation path of your Java SDK. For instance, if Java SDK is |
---|
| 350 | installed in the ``/usr/lib/jvm/java-6-sun-1.6.0.22/`` directory, |
---|
| 351 | then the following command can be used: |
---|
[659] | 352 | |
---|
[696] | 353 | :: |
---|
[659] | 354 | |
---|
[696] | 355 | $ ./configure --with-java=/usr/lib/jvm/java-6-sun-1.6.0.22/ |
---|
[659] | 356 | |
---|
[696] | 357 | This assumes that the ``include/linux`` and ``jre/lib/i386/client/`` |
---|
| 358 | subdirectories exist in ``/usr/lib/jvm/java-6-sun-1.6.0.22/``, and |
---|
| 359 | that the ``include/linux`` directory contains the ``jni.h`` headers file |
---|
| 360 | and that the ``jre/lib/i386/client/`` directory contains the ``libjvm.so`` |
---|
| 361 | file. |
---|
[659] | 362 | |
---|
[809] | 363 | .. note:: |
---|
| 364 | You can use the `--with-java-rpath` option to produce a binary |
---|
| 365 | aware of the libjvm location. |
---|
[659] | 366 | |
---|
[809] | 367 | |
---|
[696] | 368 | .. note:: |
---|
| 369 | With Mac OS X you only have to set *macos* as the value for the |
---|
| 370 | ``--with-java`` option to activate Java support. For example: |
---|
[659] | 371 | |
---|
[696] | 372 | :: |
---|
[659] | 373 | |
---|
[696] | 374 | $ ./configure --with-java=macos |
---|
[659] | 375 | |
---|
| 376 | |
---|
[714] | 377 | Perl Support (Optional) |
---|
| 378 | ************************ |
---|
[659] | 379 | |
---|
[714] | 380 | The ``--with-perl=yes`` option can be used for activating the |
---|
| 381 | ZOO-Kernel Perl support, as follow: |
---|
[659] | 382 | |
---|
[696] | 383 | :: |
---|
[659] | 384 | |
---|
[714] | 385 | $ ./configure --with-perl=yes |
---|
[659] | 386 | |
---|
[714] | 387 | This assumes that perl is found in your PATH. For instance, if Perl is |
---|
| 388 | installed in ``/usr/local`` and ``/usr/local/bin`` is not found in |
---|
| 389 | your ``PATH``, then the following command can be used (this assumes |
---|
| 390 | that ``/usr/local/bin/perl`` exists): |
---|
[659] | 391 | |
---|
[696] | 392 | :: |
---|
[659] | 393 | |
---|
[714] | 394 | $ ./configure --with-perl=/usr/local |
---|
[659] | 395 | |
---|
| 396 | |
---|
[696] | 397 | Orfeo Toolbox Support (Optional) |
---|
[713] | 398 | ********************************* |
---|
[659] | 399 | |
---|
[696] | 400 | In order to activate the optional Orfeo Toolbox support, the |
---|
| 401 | ``--with-otb`` option must be used, using the following command: |
---|
[659] | 402 | |
---|
[696] | 403 | :: |
---|
[659] | 404 | |
---|
[696] | 405 | $ ./configure --with-otb=/path/to/your/otb/ |
---|
[659] | 406 | |
---|
| 407 | |
---|
[696] | 408 | Read more about the :ref:`kernel-orfeotoolbox`. |
---|
[659] | 409 | |
---|
[696] | 410 | .. warning:: |
---|
| 411 | To build the Orfeo Toolbox support you will require ITK, the |
---|
| 412 | default version of ITK is 4.5, in case you use another version, |
---|
| 413 | please make sure to use the ``--with-itk-version`` to specificy |
---|
| 414 | what is the version available on your system. |
---|
[659] | 415 | |
---|
[696] | 416 | SAGA GIS Support (Optional) |
---|
[713] | 417 | **************************** |
---|
[659] | 418 | |
---|
| 419 | |
---|
[696] | 420 | In order to activate the optional SAGA GIS support, the *--with-saga* option must be used, using the following command: |
---|
[659] | 421 | |
---|
| 422 | :: |
---|
| 423 | |
---|
[696] | 424 | $ ./configure --with-saga=/path/to/your/saga/ |
---|
[659] | 425 | |
---|
| 426 | |
---|
[696] | 427 | Read more about the :ref:`kernel-sagagis`. |
---|
[659] | 428 | |
---|
[696] | 429 | .. warning:: |
---|
| 430 | In case wx-config is not in your ``PATH`` please, make sure to use |
---|
| 431 | the ``--with-wx-config`` to specify its location. |
---|
[659] | 432 | |
---|
[717] | 433 | Translation support (Optional) |
---|
| 434 | ****************************** |
---|
| 435 | |
---|
[722] | 436 | The ZOO-Kernel is able to translate the messages it produces in different |
---|
| 437 | natural languages. This requires that you download `the messages file |
---|
| 438 | <https://www.transifex.com/projects/p/zoo-kernel-internationalization/>`_ |
---|
| 439 | translated in your language, if any. Then, for this translation |
---|
| 440 | support to work, you have to generate manually the requested file on |
---|
| 441 | your system. For instance for the French translation, you may use the |
---|
| 442 | following command: |
---|
[717] | 443 | |
---|
| 444 | .. code:: |
---|
| 445 | |
---|
[722] | 446 | msgfmt messagespo_fr_FR.utf8.po -o /usr/share/locale/fr/LC_MESSAGES/zoo-kernel.mo |
---|
[717] | 447 | |
---|
| 448 | The ZOO-Kernel is also able to handle translation of |
---|
| 449 | ZOO-Services. Please, refer to :ref:`this document |
---|
| 450 | <service_translation>` for more details on the procedure to add new |
---|
| 451 | ZOO-Service translation files. |
---|
| 452 | |
---|
| 453 | .. warning:: |
---|
| 454 | The location of the final ``.mo`` file may vary depending on your |
---|
| 455 | system setup. |
---|
| 456 | |
---|
| 457 | |
---|
[696] | 458 | Install ZOO-Services |
---|
| 459 | -------------------- |
---|
[659] | 460 | |
---|
[696] | 461 | .. warning:: |
---|
| 462 | We present here a global installation procedure for basics |
---|
| 463 | ZOO-Services, for details about automatic installation of services |
---|
| 464 | provided by :ref:`kernel-orfeotoolbox` or :ref:`kernel-sagagis`, |
---|
| 465 | please refer to there specific documentations. |
---|
[659] | 466 | |
---|
[696] | 467 | Depending on the programming language used to implement the |
---|
| 468 | ZOO-Services you want to install, you will need to build a |
---|
| 469 | Services Provider. In the case of *C* and *Fotran*, you would create a |
---|
| 470 | shared library exporting the functions corresponding to all the |
---|
| 471 | ZOO-Services provided by this Services Provider. In case of *Java*, |
---|
| 472 | you will need to build a Java Class. In any other programming |
---|
| 473 | language, you should simply have to install the ServiceProvider and |
---|
| 474 | the zcfg files. |
---|
[659] | 475 | |
---|
[696] | 476 | If building a Shared library or a Java class is required, then you |
---|
| 477 | should find a ``Makefile`` in the service directory which is |
---|
| 478 | responsible to help you build this Services Provider. So you should |
---|
| 479 | simply run the `make` command from the Service directory to generate |
---|
| 480 | the required file. |
---|
[659] | 481 | |
---|
[696] | 482 | Then you simply need to copy the content of the ``cgi-env`` directory |
---|
| 483 | in ``cgi-bin``. |
---|
[659] | 484 | |
---|
[696] | 485 | To install the ``ogr/base-vect-ops`` Services Provider, supposing that |
---|
| 486 | your ``cgi-bin`` directory is ``/usr/local/lib`` use the following |
---|
| 487 | commands: |
---|
[659] | 488 | |
---|
[696] | 489 | .. code:: |
---|
[659] | 490 | |
---|
[696] | 491 | cd zoo-project/zoo-services/ogr/base-vect-ops |
---|
| 492 | make |
---|
| 493 | cp cgi-env/*.* /usr/lib/cgi-bin |
---|
[659] | 494 | |
---|
[696] | 495 | .. note:: |
---|
| 496 | You may also run ``make install`` directly after ``make``. |
---|
[659] | 497 | |
---|
| 498 | |
---|
[696] | 499 | To install the hello-py Services Provider, use the following commands: |
---|
[659] | 500 | |
---|
[696] | 501 | .. code:: |
---|
| 502 | |
---|
| 503 | cd zoo-project/zoo-services/hello-py/ |
---|
| 504 | cp cgi-env/* /usr/lib/cgi-bin |
---|
| 505 | |
---|
| 506 | |
---|
| 507 | Testing your installation |
---|
| 508 | ------------------------- |
---|
| 509 | |
---|
| 510 | To test your installation yous should first be able to run the |
---|
| 511 | following command from the ``cgi-bin`` directory: |
---|
| 512 | |
---|
| 513 | .. code:: |
---|
| 514 | |
---|
| 515 | ./zoo_loader.cgi "request=GetCapabilities&service=WPS" |
---|
| 516 | |
---|
| 517 | |
---|