Once your SaadaDB works fine on your local machine, you can make it world wide accessible whithout becoming an expert in security or a hacker in your institution. A way to keep you SaadaDB at its place is to request a proxy channel on a world wide open web server.

 “A proxy is a computer that offers a computer network service to allow clients to make indirect network connections to other network services” (Wikipedia e.g.)

 Here we will not discuss about the security managemennt on Tomcats (see Tomcat Web pages) but how to change the URL base of your SaadaDB to make it visible behind the proxy.

 Imagine that your SaadaDB (named MySaada e.g.) is running on your machine(e.g. myhost) on the port 8080. The URL opening your SaadaDB’s homepage is then http://myhost:8080/MySaada. If somebody is trying this URL from outside of your institution he can (certainly) get an error because your local machine is not authorized to run as a server and especially on the 8080 port. If the URL works anyway, you can leave this page.

Let us suppose that the official web server of your institution is http://my.instituton.org. You are willing to make the URL http://my.instituton.org/MySaada pointing to your database :

 Ask your system manager to open the proxy channel : For an Apache Web server the following code sample must be oppened to the httpd.conf file .

Cookies are essential to run the Saada web interface.

 Update the URL root of your SaadaDB installation.
— Go into the directory $SAADA_DB_HOME/config
— Edit the file saadadb.xml
— Replace the line <url_root>http://myhost:8080/MySaada</url_root> with <url_root>http://my.instituton.org/MySaada</url_root>
— Go into the directory $SAADA_DB_HOME/bin
— Compile the web interface : ./sant servelt.compile
— Deploy the web interface : ./deploytomact

 Important Once the new address (http://my.instituton.org/MySaada) is working, the old one (http://myhost:8080/MySaada) is no longer working.