Overview

In a production environment a collection of Oracle Secure Global Desktop (SGD) servers is configured into an array that shares configuration information and performs load-balancing tasks, fronted by one or more SGD gateways sitting in a DMZ (see the following article discussing the SGD gateway and its advantages).

Why co-locate the gateay

In order to run a simple setup without the need for sophisticated load-balancing, or a proof of concept, the SGD gatway can be co-located with the SGD server. Since both the gateway and the server listen to ports 80 and 443, this process changes the ports the SGD server listens to.

Steps to co-locate the SGD gateway

The process to co-locate the gateway with the SGD server is as follows

• stop the SGD server
  /opt/tarantella/bin/tarantella stop --kill
• install the SGD gateway rpm package
  yum install /opt/tarantella/var/docroot/gateway/SUNWsgdg-5.40-901.$(uname -m).rpm
• run the tarantella command to discover the local gateway
  /opt/tarantella/bin/tarantella discover gateway --local
• start the SGD server and gateway
  /opt/tarantella/bin/tarantella start
  /opt/SUNWsgd/bin/gateway start

Steps to drop a co-located SGD gateway

In order to configure multiple SGD servers into an array, the SGD gateway needs to run on its own dedicated system. If we have a setup with a co-located gateway we need to first drop the local gateway. The following steps need to be run as root user on the server with the co-located gateway

• stop the SGD server
  /opt/tarantella/bin/tarantella stop --kill
• stop the SGD gateway
  /opt/SUNWsgdg/bin/gateway stop --force
• run the drop command
  /opt/tarantella/bin/tarantella drop gateway --local
• start the SGD server
  /opt/tarantella/bin/tarantella start