Docs updates

docs/technical_faq.rst

@@ -9,8 +9,8 @@ the following infraestructure:
 
 -  Four virtual machines, two for the front-ends and another two for the
    back-end
--  All of them use as operating system Ubuntu server LTS 12.04
--  The real time database server(Redis) works with 16 GB of memory and
+-  All of them use as operating system Ubuntu server LTS 16.04
+-  The real time database server(Redis) works with 32 GB of memory and
    36 GB of hard disk
 -  The other three servers works with 4 GB of memory and 16 GB of hard
    disk
@@ -24,7 +24,7 @@ I successfully published an observation, but I cannot see the data in catalog.
 ------------------------------------------------------------------------------
 
 Check that the Catalog and Sentilo API Server are in the same timezone,
-for example in UTC. Make sure the sentilo-server script has the
+for example in UTC. Make sure the sentilo-server is executed with the
 following VM option:
 
 ::
@@ -44,7 +44,7 @@ https://developers.google.com/maps/documentation/javascript/get-api-key
 and create one.
 
 If you are using the last release of Sentilo(1.6) you can define the API
-key inside the catalog-config.properties configuration file:
+key inside the sentilo/sentilo-catalog-web/src/main/resources/properties/catalog-config.properties configuration file:
 
 .. code:: properties
 
@@ -53,12 +53,20 @@ key inside the catalog-config.properties configuration file:
 
 --------------
 
+Remember you'll have to recompile sentilo-catalog-web redeploy the sentilo-catalog-web.war after that.
+
+
 I created a provider and immediately after that, an observation using the new provider’s token is rejected with 401 “Invalid credential”
 ----------------------------------------------------------------------------------------------------------------------------------------
 
 The providers are activated in a background job that runs every 5
 minutes. Please wait a moment :-)
 
+Another possible reason is that the Sentilo API server started before the Catalog application (probably deployed on your Tomcat).
+At startup, the API server performs a call to /sentilo-catalog-web/api/entities/permissions in order to mirror the permissions stored in MongoDB with Redis.
+If this call fails because the sentilo-catalog-web is not deployed yet, the permissions are not correctly created.
+To resolve the issue, reboot your Sentilo and ensure that the API server starts always after the sentilo-catalog-web is fully deployed.
+
 --------------
 
 The command mvn package appassembler:assemble fails.

docs/use_a_virtual_machine.rst

@@ -5,7 +5,7 @@ A Sentilo sample instance is available for testing purposes distributed
 as a Open Virtual Appliance file
 (`OVA <https://en.wikipedia.org/wiki/Open_Virtualization_Format>`__).
 
-The appliance contains the **1.7.0 Sentilo release**.
+The appliance contains the **1.8.0 Sentilo release**.
 
 Components installed:
 
@@ -15,23 +15,11 @@ Components installed:
 -  Sentilo Alert Agent
 -  Sentilo Location Updater Agent
 
-Two different distribution files are available:
-
 -  One designed for **Virtual Box**, available
-   `here <http://www.sentilo.io/wordpress/?wpfb_dl=24>`__. It has been
-   tested using version **5.0.24**.
--  The second one, built for **ESXI** systems, available
-   `here <http://www.sentilo.io/wordpress/?wpfb_dl=25>`__. It has been
-   tested using **VMPlayer 12.5.5** and **ESXI 6.0**.
-
-Please, keep in mind some important facts:
-
--  The virtual machine credentials are **sentilo/sentilo**.
--  You should config the network type as **“Bridged Adapter”.**
--  When stopping the virtual machine, it should be done in a organized
-   way, in a Virtual Box environment you have to do this using the
-   option **“Shutdown ACPI”**. You could also do this from the command
-   line executing **“sudo shutdown -h now”**
+   `here <http://www.sentilo.io/wordpress/download/appliance/view(6).html>`__. It has been
+   tested using version **5.0.40**.
+
+The virtual machine credentials are **sentilo/sentilo**.
 
 After the virtual machine is started, all the sentilo services are
 launched automatically. The IP of the virtual machine is assigned