Changes between Version 16 and Version 17 of ZooWorkshop/FOSS4GJapan/UsingZooFromOSGeoLiveVM

Timestamp:

Nov 1, 2010, 7:15:23 PM (14 years ago)

Author:

djay

Comment:

Add the introduction to the updateStatus function we have to add in the ZooWorkshop/FOSS4GJapan/CreatingOGRBasedWebServices section

ZooWorkshop/FOSS4GJapan/UsingZooFromOSGeoLiveVM

@@ -18 +18 @@
 Please note that we will talk about ZOO Kernel or {{{zoo_loader.cgi}}} script without any distinction during this workshop.
 
-The {{{main.cfg}}} file contains metadata informations about the identification and provider but also some important settings. The file is composed of various sections, namely {{{main}}}, {{{identification}}} and {{{provider}}} per default. Obviously, you are free to add new sections to the file if you need them for a specific Service. Nevertheless, you have to know that the {{{env}}} and {{{lenv}}} sections name are used in a specific way. The {{{env}}} one lets you define environment variables that your Service requires during its runtime. For instance, if your Service requires to access to a X server running on framebuffer, you can add {{{DISPLAY=:1}}} line in your env section to take this specificity into account. As for the {{{env}}} section, there is the section {{{lenv}}} where specific informations about status informations of a running Service will be written by the ZOO Kernel or the ZOO Services. For instance, when your service failed, you can set the value for {{{message}}} in {{{lenv}}} to see it displayed in the {{{Status}}} node of the {{{ExecuteResponse}}} returned back to the client. If your service will take long time and can get informations about processing status, you can then set a value between 0 and 100 to {{{status}}} in {{{lenv}}} to represent the percentage completed of the running Service task.
+The {{{main.cfg}}} file contains metadata informations about the identification and provider but also some important settings. The file is composed of various sections, namely {{{main}}}, {{{identification}}} and {{{provider}}} per default. Obviously, you are free to add new sections to the file if you need them for a specific Service. Nevertheless, you have to know that the {{{env}}} and {{{lenv}}} sections name are used in a specific way. 
 
-Please take a look to this file. Three important parameters are commented bellow:
+The {{{env}}} section lets you define environment variables that your Service requires during its runtime. For instance, if your Service requires to access to a X server running on framebuffer, then you will have to set the {{{DISPLAY}}} environnement variably, in this case you would add {{{DISPLAY=:1}}} line in your {{{env}}} section. 
+
+As for the {{{env}}} section, there is the section {{{lenv}}} where specific informations about status informations of a running Service will be written by the ZOO Kernel or the ZOO Services. For instance, when your service failed, you can set the value for {{{message}}} in {{{lenv}}} to see it displayed in the {{{Status}}} node of the {{{ExecuteResponse}}} returned back to the client. If your service will take long time and can get informations about processing status, you can then set a value between 0 and 100 to {{{status}}} in {{{lenv}}} to represent the percentage completed of the running Service task, we will talk deeper about this later in this workshop.
+
+Please take a look to your local file {{{main.cfg}}} file. Three important parameters are commented bellow:
 
  * {{{serverAddress}}} : The url to access to the ZOO Kernel