Changes between Version 1 and Version 2 of ZooWorkshop/FOSS4GJapan/UsingZooFromOSGeoLiveVM

Timestamp:

Oct 15, 2010, 1:47:15 PM (16 years ago)

Author:

djay

Comment:

--

ZooWorkshop/FOSS4GJapan/UsingZooFromOSGeoLiveVM

@@ -66 +66 @@
 Two other softwares form the OSGeoLive environment will be used during this workshop. Geoserver will first be used to provide WFS input data for the ZOO Services we are going to develop. The Geoserver sample dataset (United States polygons) will be passed to our service during section 3. So please start the Geoserver using the corresponding launcher in the Servers folder, as illustrated in the following screenshot :
 
+[[Image(Practical introduction to ZOO - 1.png,width=400px,align=center)]]
 
 OpenLayers library is also available on the OSGeoLive virtual machine image disk, and it will be used during section 4, for building a simple WPS client application able to query the newly developed ZOO Services. 
@@ -71 +72 @@
 As we planned to use OGR C-API and Python module of the GDAL library, we will need the corresponding header files, libraries and associated files. Hopefully everything was already available per default and so ready to use on the OSGeoLive packaging.
 
+== Testing the ZOO installation with GetCapabilities ==
+
+You can now simply query ZOO Kernel using the following request from your Internet browser:
+
+[http://localhost/cgi-bin/zoo_loader.cgi?Request=GetCapabilities&Service=WPS]
+
+You should then get a valid Capabilities XML document, as the following :
+
+Please note that no Process node is returned in the ProcessOfferings section, as no ZOO Service is available yet. You can also proceed to a GetCapabilities request from the command line, using the following command:
+
+{{{
+#!sh
+cd /usr/lib/cgi-bin
+./zoo_loader.cgi “request=GetCapabilities&service=WPS”
+}}}
+
+The same result as in your browser will be returned, as shown in the following screenshot:
+
+== Preparing your ZOO ServiceProvider directory ==
+
+In order to simplify the task, we will first comment the directory structure which should be used when creating a new Services Provider :
+
+ * The main Services Provider directory including :
+  * A cgi-env directory which will contain all the zcfg metadata files and the service shared
+object (C Shared Library or Python module)
+  * The Makefile and the *c files needed to compile your Services Provider.
+
+Please create a ws_sp main Services Provider directory in the existing zoo-services one located in /home/user/zoows/sources/, respecting the tree above .
+
+{{{
+#!sh
+mkdir -p /home/user/zoows/sources/zoo-services/ws_sp/cgi-env
+}}}
+
+The Makefile and the code of the C and Python Service Shared Object will be detailed in the next sections.
+