Once your SaadaDB works fine on your machine, you could need to push the Web interface on another application server (e.g another Tomcat instance). Until now, the application server must be run on the machine where the SaadaDB is installed as for any other Saada applications

 This operation can be required for performance issues or to conform to the local security policy.
 Edit the file $SAADA_DB_HOME/bin/saadadb.properties
— Put the new Tomcat location in the field TOMCAT_HOME
 Edit the file $SAADA_DB_HOME/config/saadadb.xml
— Update the url_root element if needed. This element must be modified in case of a direct connection. If the SaadaDB is accessed through a proxy, you should better keep the same url_root and modify the proxy setup (see article 128)
 Go into the $SAADA_DB_HOME/bin directory
— run the command tomcatdeploy or « ./sant tomcat.deploy »
 Restart the new application server