Installation guide

Clock Synchronization
10
makes a secure connection on port 5307. After the connection is established, the
connection is downgraded to a standard connection on port 3144.
To run applications, SGD must be able to make TCP/IP connections to application servers. The types of
applications determine the TCP ports that must be open, for example:
• 22 – For X and character applications using Secure Shell (SSH)
• 23 – For Windows, X, and character applications using Telnet
• 3389 – For Windows applications using Windows Remote Desktop Services
• 6010 and above – For X applications
2.1.7. Clock Synchronization
In SGD, an array is a collection of SGD servers that share configuration information. As the SGD servers in
an array share information about user sessions and application sessions, it is important to synchronize the
clocks on the SGD hosts. Use Network Time Protocol (NTP) software or the rdate command to ensure
the clocks on all SGD hosts are synchronized.
2.1.8. SGD Web Server
The SGD web server consists of an Apache web server and a Tomcat JavaServer Pages (JSP) technology
container preconfigured for use with SGD.
The SGD web server consists of several components. The following table lists the web server component
versions for recent releases of SGD.
Component Name SGD
Version 4.70
SGD
Version 4.62
SGD
Version 4.61
SGD
Version 4.60
Apache HTTP Server 2.2.22 2.2.21 2.2.17 2.2.16
OpenSSL 1.0.0.j 1.0.0.e 1.0.0.d 1.0.0a
mod_jk 1.2.37 1.2.32 1.2.31 1.2.27
Apache Jakarta Tomcat 7.0.29 6.0.33 6.0.32 6.0.29
Apache Axis 1.4 1.4 1.4 1.4
The Apache web server includes all the standard Apache modules as shared objects.
The minimum Java Virtual Machine (JVM) software heap size for the Tomcat JSP technology container is
256 megabytes.
2.1.9. Supported Authentication Mechanisms
The following are the supported mechanisms for authenticating users to SGD:
• Lightweight Directory Access Protocol (LDAP) version 3
• Microsoft Active Directory
• Network Information Service (NIS)
• RSA SecurID