Secure Global Desktop 4.31 Administration Guide > Arrays, servers and load balancing > Introducing the Secure Global Desktop Web Server

Introducing the Secure Global Desktop Web Server

Read this topic to...
Learn about the Secure Global Desktop Web Server.

You must have a web server running on each host on which Secure Global Desktop is installed. When you install Secure Global Desktop, Secure Global Desktop Setup also installs the Secure Global Desktop Web Server. The Secure Global Desktop Web Server is a web server which has been pre-configured for use with Secure Global Desktop. It consists of:

an Apache web server
the mod_ssl module for Apache
an Apache Jakarta Tomcat server

Note The Apache web server includes all the standard Apache modules as shared objects.

If you have an existing web server on the Secure Global Desktop host, this won't be affected by the Secure Global Desktop Web Server as this will be listening on a different port. You do not have to use the Secure Global Desktop Web Server, but to use your own web server you will have to configure it for use with Secure Global Desktop.

You can configure the Secure Global Desktop Web Server using standard Apache directives, see the Apache documentation for details.

You control the Secure Global Desktop Web Server independently of the Secure Global Desktop server, using the tarantella webserver command.

Securing the Secure Global Desktop Web Server

The Secure Global Desktop Web Server is also configured to be a secure (HTTPS) web server. You just need to install an appropriate server certificate or share the server certificate used for Secure Global Desktop security services.

Every web server in an array of Secure Global Desktop servers must use the same HTTP (or HTTPS) port. You must not mix HTTP and HTTPS web servers in the same Secure Global Desktop array.

Once you enable secure connections to a web server, the URL in the client profile must be re-configured to an HTTPS URL.

Related topics
The tarantella webserver command