Changeset 722 for branches


Ignore:
Timestamp:
Jul 2, 2015, 1:25:29 PM (9 years ago)
Author:
djay
Message:

Add document to help translating the internal messages using transifex. Put db creation in installation. Update windows installation procedure (nothing specific to setup on IIS or Apache, but it is known as working on both) including details for available options.

Location:
branches/PublicaMundi_David-devel/docs
Files:
1 added
6 edited

Legend:

Unmodified
Added
Removed

  • branches/PublicaMundi_David-devel/docs/contribute/index.rst

    r717 r722  
    1717   dev
    1818   release
     19   translate
    1920   contributors

  • branches/PublicaMundi_David-devel/docs/install/installation.rst

    r717 r722  
    110110    linked files.
    111111
     112.. _zoo_create_db_backend:
     113
     114To create a new database to be used by the ZOO-Kernel, you have
     115to load the `schema.sql
     116<http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/sql/schema.sql>`_
     117file. For instance, you may run the following:
     118
     119.. code::
     120
     121    createdb zoo_project
     122    psql zoo_project -f zoo-project/zoo-kernel/sql/schema.sql
     123
     124.. note::
     125    You can choose another schema to store ZOO-Kernel specific
     126    informations. In such a case, you would need to edit the
     127    schema.sql file to uncomment line `33
     128    <http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/sql/schema.sql#L33>`_
     129    and `34
     130    <http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/sql/schema.sql#L34>`_.
     131
     132
     133
    112134YAML Support (Optional)
    113135************************
    … …  
    373395******************************
    374396
    375 The ZOO-Kernel is able to translate the messages it produce in different
    376 natural languages. For this translation support to work, you have to
    377 generate and install manually the quested files on your system, by
    378 using the following command:
    379 
    380 .. code::
    381 
    382     msgfmt zoo-project/zoo-kernel/locale/po/fr_FR.utf8.po -o /usr/share/locale/fr/LC_MESSAGES/zoo-kernel.mo
     397The ZOO-Kernel is able to translate the messages it produces in different
     398natural languages. This requires that you download `the messages file
     399<https://www.transifex.com/projects/p/zoo-kernel-internationalization/>`_
     400translated in your language, if any. Then, for this translation
     401support to work, you have to generate manually the requested file on
     402your system. For instance for the French translation, you may use the
     403following command:
     404
     405.. code::
     406
     407    msgfmt messagespo_fr_FR.utf8.po -o /usr/share/locale/fr/LC_MESSAGES/zoo-kernel.mo
    383408
    384409The ZOO-Kernel is also able to handle translation of

  • branches/PublicaMundi_David-devel/docs/install/windows.rst

    r696 r722  
    88====================
    99
    10 Using OSGeo4W
    11 --------------
    12 
    13 Install OSGeo4W
    14 ..........................................
    15 
    16 First download the OSGeo4W installer from  http://trac.osgeo.org/osgeo4w/, and install it with all the dependencies needed by your
    17 WPS services such as GDAL for example.
     10Compile ZOO-Project from source
     11-------------------------------
    1812
    1913.. warning::
    20     FastCGI, libxml, Python and cURL are mandatory
    21 
    22 Install ZOO4W
    23 ..........................................
    24 
    25 Once OSGeo4W installed on your platform, you will need more GNU tools and libraries. `This package <http://www.zoo-project.org/dl/tool-win32.zip>`__  contains full dependencies required to compile on a WIN32 platform and this one contains `full runtime dependencies <http://www.zoo-project.org/dl/zoo-runtime.zip>`__ . Place it to your ``C:\OSGeo4W\bin``.
    26 
    27 Download the `binary version <http://www.zoo-project.org/dl/zoo_loader.cgi>`__  of ZOO Kernel for WIN32, then place it in the ``C:\OSGeo4W\bin`` directory. Don't forget to place the *main.cfg* file in the same directory, you can use a modified copy of  `this file <http://www.zoo-project.org/trac/browser/trunk/zoo-kernel/main.cfg>`__.
    28 
    29 Additionaly, the binary version of the OGR Services Provider available from `here <http://www.zoo-project.org/dl/zoo-services-win32.zip>`__ can be used directly. Place the two libraries with their respective .zcfg files in your local ``C:\OSGeo4W\bin`` directory to do so.
    30 
    31 Compile ZOO from source
    32 ---------------------
    33 
    34 .. warning::
    35    Ensure to first perform the :ref:`prerequisite steps <kernel-installation-prereq>` before compiling the ZOO Kernel.
    36 
    37 The following steps are for use with the Microsoft Visual Studio compiler (and tested with MSVC 2008).
    38 
    39 1. Make sure the gnuwin32 tools *bison.exe*  and *flex.exe* are found in your path.  You can download the GNUwin32 tools `here <http://www.zoo-project.org/dl/tool-win32.zip>`__.
    40 
    41 2. Modify the *nmake.opt* file to point to your local libraries.  You can find a modified nmake.opt that points to local libs `here <http://www.zoo-project.org/trac/attachment/ticket/27/nmake.opt>`__.
    42    You can also find a modified ``zoo-project\zoo-kernel\makefile.vc`` file `here <http://www.zoo-project.org/trac/attachment/ticket/27/makefile.vc>`__.
     14   Ensure to first perform the :ref:`prerequisite steps
     15   <install-prereq>` before compiling the ZOO Kernel.
     16
     17The following steps are for use with the Microsoft Visual Studio
     18compiler (and tested with MSVC 2010).
     19
     201. Make sure the gnuwin32 tools ``bison.exe``  and ``flex.exe`` are found
     21   in your path.  You can download the GNUwin32 tools `here
     22   <http://www.zoo-project.org/dl/tool-win32.zip>`__.
     23
     242. Modify the ``nmake.opt`` file to point to your local libraries. Note
     25   that you can also use definition directly in the command line if
     26   you prefer. See :ref:`win_configure_options` for details about this
     27   options.
     28
    4329   
    44303. Execute:
    … …  
    4834     nmake /f makefile.vc
    4935     
    50 4. A file *zoo_loader.cgi* should be created.  Note that if another file named *zoo_loader.cgi.manifest* is also created, you
    51    will have to run another command:
    52    
     364. A file ``zoo_loader.cgi`` and ``libzoo_service.dll`` should be
     37   created.  Note that if another file named
     38   ``zoo_loader.cgi.manifest`` is also created, you will have to run
     39   another command:
     40
    5341   ::
    5442   
    5543     nmake /f makefile.vc embed-manifest
    5644     
    57 5. Copy the files *zoo_loader.cgi*  and *main.cfg* into your cgi-bin directory.
    58 
    59 6. Using the command prompt, test the zoo-kernel by executing the following command:
     455. Copy the files ``zoo_loader.cgi``, ``libzoo_service.dll``  and
     46   ``main.cfg`` into your cgi-bin directory.
     47
     486. Using the command prompt, test the ZOO-Kernel by executing the
     49   following command:
    6050
    6151   ::
    … …  
    7767     </ows:ExceptionReport>
    7868     
    79 7. Edit the *main.cfg* file so that it contains values describing your WPS service.  An example of such
    80    a file running on Windows is:
     697. Edit the ``main.cfg`` file so that it contains values describing
     70   your WPS service.  An example of such a file running on Windows is:
    8171   
    8272   ::
    … …  
    133123       ...
    134124       
     125
     126.. _win_configure_options:
     127
     128Build options
     129.............
     130
     131Various build options can be set in the ``nmake.opt`` file to define
     132the location of the built libraries you want to use to build your
     133ZOO-Kernel. Some are optional and some are required, they are listed
     134below exhaustively:
     135
     136.. contents::
     137    :local:
     138    :depth: 1
     139    :backlinks: top
     140
     141
     142gettext (Required)
     143******************
     144
     145The location of the libintl (built when building gettext) should be
     146specified by defining the ``INTL_DIR`` environment variable. It
     147supposes that the header and the ``intl.lib`` file are available.
     148
     149So for instance, in case you build the gettext in
     150``\buildkit\srcs\gettext-0.14.6``, you may define the following before
     151running ``nmake /f makefile.vc``:
     152
     153.. code::
     154
     155    set INTL_DIR=\buildkit\srcs\gettext-0.14.6\gettext-runtime\intl
     156
     157
     158libCURL (Required)
     159******************
     160
     161The location of the libCURL should be specified by defining
     162the ``CURL_DIR`` environment variable. It supposes that there are 2
     163sub-directory ``include`` containing the libCURL header and ``lib``
     164which contains the ``libcurl.lib`` file.
     165
     166So for instance, in case you build the libCURL in
     167``\buildkit\srcs\curl-7.38.0``, you may define the following before
     168running ``nmake /f makefile.vc``:
     169
     170.. code::
     171
     172    set CURL_DIR=\buildkit\srcs\curl-7.38.0\builds\libcurl-vc10-x86-release-dll-ssl-dll-zlib-dll-ipvs6-sspi
     173
     174
     175libFCGI (Required)
     176******************
     177
     178The location of the libFCGI should be specified by defining the
     179``FCGI_DIR`` environment variable. It supposes that there are 2
     180sub-directory ``include`` containing the FastCGI header and
     181``libfcgi/Release`` which contains the ``libfcgi.lib`` file.
     182
     183So for instance, in case you build the libXML2 library in
     184``\buildkit\srcs\fcgi-2.4.1``, you may define the following before
     185running ``nmake /f makefile.vc``:
     186
     187.. code::
     188
     189    set FCGI_DIR=\buildkit\srcs\fcgi-2.41.1
     190
     191libXML2 (Required)
     192******************
     193
     194The location of the libXML2 should be specified by defining the
     195``XML2_DIR`` environment variable. It supposes that there are 2
     196sub-directory ``include`` containing the libXML2 header and
     197``win32\bin.msvc`` which contains the ``libxml2.lib`` file.
     198
     199So for instance, in case you build the libXML2 library in
     200``\buildkit\srcs\libxml2-2.9.0``, you may define the following before
     201running ``nmake /f makefile.vc``:
     202
     203.. code::
     204
     205    set XML2_DIR=\buildkit\srcs\libxml2-2.9.0
     206
     207OpenSSL (Required)
     208******************
     209
     210The location of the OpenSSL library should be specified by defining
     211the ``SSL_DIR`` environment variable. It supposes that there are 2
     212sub-directory ``inc32`` containing the header files and
     213``out32dll`` which contains the ``ssleay32.lib`` file.
     214
     215So for instance, in case you build the libXML2 library in
     216``\buildkit\srcs\openssl-1.0.2c``, you may define the following before
     217running ``nmake /f makefile.vc``:
     218
     219.. code::
     220
     221    set SSL_DIR=\buildkit\srcs\openssl-1.0.2c
     222
     223GDAL (Required)
     224******************
     225
     226The location of the GDAL library should be specified by defining
     227the ``GDAL_DIR`` environment variable. It corresponds to the path
     228where you uncompress and built GDAL, it supposes that you have the
     229``gdal_i.lib`` file available in this directory.
     230
     231So for instance, in case you build the libXML2 library in
     232``\buildkit\srcs\gdal-1.10.1``, you may define the following before
     233running ``nmake /f makefile.vc``:
     234
     235.. code::
     236
     237    set GDAL_DIR=\buildkit\srcs\gdal-1.10.1
     238
     239MapServer (Optional)
     240********************
     241
     242The location of the MapServer library path should be specified by
     243defining the ``MS_DIR`` environment variable. It corresponds to the
     244path where you build MapServer on your system, this directory should
     245contain the ``nmake.opt`` file used.
     246
     247So for instance, in case you build Python in
     248``\buildkit\srcs\mapserver-6.2.0``, you may define the following before
     249running ``nmake /f makefile.vc``:
     250
     251.. code::
     252
     253    set MS_DIR=\buildkit\srcs\mapserver-6.2.0
     254
     255
     256Python (Optional)
     257*****************
     258
     259The location of the Python binaries path should be specified by
     260defining the ``PY_DIR`` environment variable. It corresponds to the
     261path where you build Python on your system. The location of the
     262``pythonXX.lib`` files should be specified by setting the
     263``PY_LIBRARY`` environment variable.
     264
     265So for instance, in case you build Python in
     266``\buildkit\srcs\Python-2.7``, you may define the following before
     267running ``nmake /f makefile.vc``:
     268
     269.. code::
     270
     271    set PY_DIR=\buildkit\srcs\Python-2.7
     272    set PY_LIBRARY=\buildkit\srcs\Python-2.7\PCBuild\python27.lib
     273
     274JavaScript (Optional)
     275*********************
     276
     277The location of libmozjs should be specified by defining the
     278``JS_DIR`` environment variable. It corresponds to the path where you
     279build libmozjs on your system, it supposes that the header and
     280the ``mozjs185-1.0.lib`` file are available in this directory.
     281
     282So for instance, in case you build libmozjs in
     283``\buildkit\srcs\js-1.8.5``, you may define the following before
     284running ``nmake /f makefile.vc``:
     285
     286.. code::
     287
     288    set JS_DIR=\buildkit\srcs\js-1.8.5
     289
     290PHP (Optional)
     291*****************
     292
     293The location of PHP should be specified by defining the ``PHP_DIR``
     294environment variable. It corresponds to the path where you build PHP
     295on your system. The location of the ``php5embed.lib`` files should be
     296specified by setting the ``PHP_LIB`` environment variable.
     297
     298So for instance, in case you build PHP in
     299``\buildkit\srcs\php-5.5.10``, you may define the following before
     300running ``nmake /f makefile.vc``:
     301
     302.. code::
     303
     304    set PHP_DIR=\buildkit\srcs\php-5.5.10
     305    set PHP_LIB=\buildkit\srcs\php-5.5.10\Release_TS\php5embed.lib
     306
     307Database backend (Optional)
     308***************************
     309
     310ZOO-Kernel can use a database backend to store ongoing status
     311informations of running services, for activating this operation mode,
     312you should define the evironment variable ``DB`` and set it to any
     313value. So, to activate this option, you may use the following before
     314running ``nmake /f makefile.vc``:
     315
     316.. code::
     317
     318    set DB=activated
     319
     320.. note::
     321    To learn how to setup the corresponding database, please refer to
     322    :ref:`this section <zoo_create_db_backend>`.
     323
     324
     325
     326
    135327Optionally Compile Individual Services
    136328.............................................................

  • branches/PublicaMundi_David-devel/docs/kernel/configuration.rst

    r713 r722  
    208208    PG:"dbname=zoo_project host=127.0.0.1 port=5432 user=username"
    209209
    210 .. _zoo_create_db_backend:
    211 
    212 To create a new database to be used by the ZOO-Kernel, you have
    213 to load the `schema.sql
    214 <http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/sql/schema.sql>`_
    215 file. For instance, you may run the following:
    216 
    217 .. code::
    218 
    219     createdb zoo_project
    220     psql zoo_project -f zoo-project/zoo-kernel/sql/schema.sql
    221 
    222 .. note::
    223     You can choose another schema to store ZOO-Kernel specific
    224     informations. In such a case, you would need to edit the
    225     schema.sql file to uncomment line `33
    226     <http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/sql/schema.sql#L33>`_
    227     and `34
    228     <http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/sql/schema.sql#L34>`_.
    229 
    230 
     210Please refer to this `section <zoo_create_db_backend>`_ to learn how
     211to setup the database.
    231212
    232213     

  • branches/PublicaMundi_David-devel/docs/kernel/what.rst

    r711 r722  
    1717new or existing web platforms.
    1818
    19 
    2019ZOO-Kernel lets you process geospatial or non geospatial data using
    2120well formed WPS requests. The WPS server is able to manage and chain
    … …  
    2524First class WPS server
    2625-----------------------
     26
     27Simple
     28......
     29
     30The ZOO-Kernel rely on simple principles and tends to ease the
     31implementation of new services by sharing similar data structures for
     32every supported programming languages. The ZOO-Kernel is responsible
     33to parse the requests it receives and return the corresponding WPS
     34response.
     35
     36In case of an *Execute* request, the ZOO-Kernel stores informations in
     37a basic KVP data structure for the programming language used to
     38implement the service, dynamically load the Service Provider defined
     39in the zcfg file and run a specific function corresponding to the
     40service, passing three arguments. Once the function return, ZOO-Kernel
     41knows if the service run succeessfuly or failed by checking the
     42returned value. In the case it succeeded, the ZOO-Kernel then parse
     43the third arguments containing the result and produce the output in
     44the desired format.
     45
     46
    2747
    2848Compliant
    … …  
    82102.. _`Hash`: http://ruby-doc.org/core-2.2.0/Hash.html
    83103
    84 
    85 Scalable
    86 ........................................................
    87 
    88 ZOO-Kernel can **scale** to large infrastructures involving high
    89 numbers of (concurrent) WPS requests and/or huge amounts of
    90 input/output.
    91 
    92 
    93 

  • branches/PublicaMundi_David-devel/docs/services/translation.rst

    r717 r722  
    3131   
    3232
    33 Then generate the 'messages.po' file based on the Services Provider
     33Then generate the ``messages.po`` file based on the Services Provider
    3434source code (located in ``service.c`` in this example) using the
    3535following command:
    … …  
    4040      xgettext service.c locale/.cache/my_service_string_to_translate.c -o message.po -p locale/po/ -k_ss
    4141
    42 Once 'messages.po' is created, use the following command to create the
    43 ``.po`` file for the targeted language to translate into. We will use the
    44 French language here as an example:
     42Once ``messages.po`` is created, use the following command to create
     43the ``.po`` file for the targeted language to translate into. We will
     44use the French language here as an example:
    4545
    4646  ::
Note: See TracChangeset for help on using the changeset viewer.

Download now !

Search

Context Navigation

Main Navigation

ZOO Sponsors

http://www.zoo-project.org/trac/chrome/site/img/geolabs-logo.pnghttp://www.zoo-project.org/trac/chrome/site/img/neogeo-logo.png http://www.zoo-project.org/trac/chrome/site/img/apptech-logo.png http://www.zoo-project.org/trac/chrome/site/img/3liz-logo.png http://www.zoo-project.org/trac/chrome/site/img/gateway-logo.png

Become a sponsor !

Knowledge partners

http://www.zoo-project.org/trac/chrome/site/img/ocu-logo.png http://www.zoo-project.org/trac/chrome/site/img/gucas-logo.png http://www.zoo-project.org/trac/chrome/site/img/polimi-logo.png http://www.zoo-project.org/trac/chrome/site/img/fem-logo.png http://www.zoo-project.org/trac/chrome/site/img/supsi-logo.png http://www.zoo-project.org/trac/chrome/site/img/cumtb-logo.png

Become a knowledge partner

Related links

http://zoo-project.org/img/ogclogo.png http://zoo-project.org/img/osgeologo.png