C H A P T E R 1 |
This chapter contains the system requirements for installing and using SGD version 4.40.
Topics in this chapter include the following:
Use the following hardware requirements as a guide and not as an exact sizing tool. For detailed help with hardware requirements, contact an SGD sales office.
The requirements for a server hosting SGD can be calculated based on the total of the following:
The following are the requirements for installing and running SGD:
This is in addition to what is required for the operating system itself and assumes the server is used only for SGD.
The following are the requirements to support users who log in to SGD and run applications:
![]() | Caution - The actual central processing unit (CPU) and memory requirements can vary significantly, depending on the applications used. |
The following table describes the supported installation platforms for SGD.
Operating System | Supported Versions |
---|---|
Solaris![]() |
8, 9, 10, 10 Trusted Extensions |
Solaris OS on x86 platforms | 10, 10 Trusted Extensions |
Red Hat Enterprise Linux (Intel x86 32-bit) | 4, 5 |
Fedora Linux (Intel x86 32-bit) | 7 |
SUSE Linux Enterprise Server (Intel x86 32‐bit) | 9, 10 |
You might have to make some operating system modifications. Without these modifications, SGD might not install properly or operate correctly.
When you install SGD on Linux platforms, localized messages in the supported languages can only be displayed if the gettext package is installed. If the gettext package is not installed, English is used during the installation.
SGD fails to install if the libXp.so.6 library is not available on the server. This library was deprecated in Fedora Core 3. However, the file is still available in the libXp package.
The libXm.so.3 library is required to support 5250 and 3270 applications. This library is available in the OpenMotif 2.2 package.
SGD fails to install if the libgdbm.so.2 library is not available on the server. SUSE Linux Enterprise Server 9 with Service Pack 2 contains version 3 of the library by default. Obtain and install version 2 of the library before installing SGD.
SGD fails to install if the libgdbm.so.2 and libexpat.so.0 libraries are not available on the server. SUSE Linux Enterprise Server 10 contains version 3 and version 1 of these libraries by default. Obtain and install the required version of these libraries before installing SGD.
You must install at least the End User Solaris OS distribution to get the libraries required by SGD. If you do not, SGD does not install.
SGD fails to install if the /usr/lib/libsendfile.so library is not available on the server. This library might be included with the Core Solaris Libraries (SUNWcsl) package, or you might have to apply patch number 111297 to obtain it.
A web server is an essential part of a working SGD installation. When you install SGD, you install the SGD Web Server. The SGD Web Server is an Apache web server that is preconfigured for use with SGD. The SGD Web Server consists of the components listed in the following table.
Component | Version |
---|---|
Apache HTTP Server | 1.3.36 |
mod_ssl | 2.8.27 |
OpenSSL | 0.9.8d |
mod_jk | 1.2.15 |
Apache Jakarta Tomcat | 5.0.28 |
Apache Axis | 1.2 |
You can use your own web server with SGD. How you do this is described in the Sun Secure Global Desktop Software 4.4 Administration Guide.
You must configure your network for use with SGD. The following are the main requirements:
SGD servers must have Domain Name System (DNS) entries that can be resolved by all clients.
DNS lookups and reverse lookups for an SGD server must always succeed.
Client devices must be able to make Transmission Control Protocol/Internet Protocol (TCP/IP) connections to SGD on the following TCP ports:
80 - For Hypertext Transfer Protocol (HTTP) connections between client devices and the SGD Web Server. The port number might vary depending on the port selected on installation.
443 - For Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS) connections between client devices and the SGD Web Server.
3144 - For standard (unencrypted) connections between client devices and SGD.
5307 - For secure connections between client devices and SGD. Secure connections use Secure Sockets Layer (SSL).
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:
The Sun Secure Global Desktop Software 4.4 Administration Guide has detailed information about all the ports used by SGD and how to use SGD with firewalls.
To use the webtop at http://server.example.com/sgd, where server.example.com is the name of an SGD server, you need the SGD Client and a supported web browser.
The SGD Client can operate in two modes:
Webtop mode. The SGD Client uses a special web page, called a webtop, to display the controls for SGD. This is the default mode.
Integrated mode. The SGD Client displays the controls for SGD in the desktop Start or Launch menu. Depending on other configuration factors, a web browser might only be needed for initial authentication, and for determining proxy server settings.
The following table lists the supported client platforms, the supported web browsers, and the supported desktop menu systems when the SGD Client is operating in Integrated mode.
Supported Client Platform | Supported Web Browsers | Integrated Mode Support |
---|---|---|
Microsoft Windows Vista | Internet Explorer 7.0+ | Microsoft Windows Start Menu |
Microsoft Windows XP Professional | Internet Explorer 6.0+, 7.0+ | Microsoft Windows Start Menu |
Microsoft Windows 2000 Professional | Internet Explorer 6.0+, 7.0+ | Microsoft Windows Start Menu |
Solaris 8+ OS on SPARC platforms | Mozilla 1.5+ | Sun Java Desktop System Launch Menu |
Solaris 10 OS Trusted Extensions on SPARC platforms | Mozilla 1.5+ | Not supported |
Solaris 10 OS on x86 platforms | Mozilla 1.5+ | Sun Java Desktop System Launch Menu |
Mac OS X 10.4+ | Safari 2.0+ | Not supported |
Fedora Linux 7 (Intel x86 32-bit) | Mozilla 1.5+ | Gnome or KDE Start Menu |
Red Hat Desktop version 4 | Mozilla 1.5+ | Gnome or KDE Start Menu |
SUSE Linux Enterprise Desktop 10 | Mozilla 1.5+ | Gnome or KDE Start Menu |
Ubuntu 7.04 | Mozilla 1.5+ | Gnome Start Menu |
Beta versions or preview releases of web browsers are not supported.
Web browsers must have the JavaScript programming
language enabled.
To support the following functionality, web browsers must have Java technology enabled:
If Java technology is not available, the SGD Client can be downloaded and installed manually.
The following are the supported plug-ins for Java technology:
Note - Sun Java Plug-in tool version 1.6.0 is the only supported plug-in for Microsoft Windows Vista platforms. |
When users start more than one user session using the same client device and web browser, the user sessions join rather than the new session ending the existing session. For user sessions to join in this way, the web browser must be configured to allow permanent cookies. If permanent cookies are not allowed, user sessions always end and this might cause application windows to disappear.
For best results, client devices must be configured for at least 256 colors.
Serial port mapping is only supported on UNIX, Linux, and Microsoft Windows platforms.
The SGD Enhancement Module is a software component that can be installed on an application server to provide the following additional functionality to SGD:
Seamless windows (Windows platforms only)[1]
The following are the supported installation platforms for the SGD Enhancement Module:
Operating System | Supported Versions |
---|---|
Microsoft Windows | Windows Server 2003
Microsoft Windows XP Professional[2] Microsoft Windows Vista Ultimate[2] Microsoft Windows Vista Business[2] |
Solaris OS on SPARC platforms | 8, 9, 10, 10 Trusted Extensions[3] |
Solaris OS on x86 platforms | 10, 10 Trusted Extensions[3] |
Red Hat Enterprise Linux (Intel x86 32-bit) | 4, 5 |
Fedora Linux (Intel x86 32-bit) | 7 |
SUSE Linux Enterprise Server (Intel x86 32-bit) | 9, 10 |
Application servers that are not supported platforms for the SGD Enhancement Module can be used with SGD to access a supported application type using any of the supported protocols.
SGD supports secure connections from clients using the following protocols:
The following encryption cipher suites are supported:
SGD supports Base 64-encoded PEM-format X.509 certificates that are signed with any of the following Certificate Authority (CA) certificates (root certificates):
Additional certificate types can be supported by installing the CA’s certificate (the root certificate) for that CA.
To use SGD with a proxy server, the proxy server must support tunneling.
For the webtop, you can use HTTP, Secure (SSL) or SOCKS v5 proxy servers.
For SOCKS v5 proxy servers, SGD supports the Basic and No Authentication Required authentication methods.
The following are the supported mechanisms for authenticating users to SGD:
Web server authentication (HTTP/HTTPS Basic Authentication), including Public Key Infrastructure (PKI) client certificates
SGD works with versions 4, 5, and 6 of the RSA Authentication Manager (formerly known as RSA ACE/Server).
SGD supports version 3 of the standard LDAP protocol. You can use LDAP authentication and the LDAP search methods for third-party authentication with any LDAP version 3‐compliant directory server. SGD supports this functionality on the following directory servers:
Sun Java System Directory
Server version 4.1+ (formerly known as Sun ONE, Netscape software, or iPlanet Directory
Server)
Other directory servers might work, but are not supported.
Active Directory authentication is only supported on Microsoft Active Directory servers.
The Directory Services Integration (sometimes known as webtop generation) functionality is supported on the following directory servers:
SGD supports printing to PostScript, Printer Command Language (PCL), and text‐only printers attached to the user’s client device.
The SGD tta_print_converter script performs any conversion needed to format print jobs correctly for the client printer. To convert from Postscript to PCL, Ghostscript must be installed on the SGD server.
To support SGD Portable Document Format (PDF) printing, Ghostscript version 6.52 or later must installed on the SGD server. The Ghostscript distribution must include the ps2pdf program. Microsoft Windows clients devices must have Adobe Reader version 4.0 or later.
SGD supports printing with the Common Unix Printing System (CUPS). CUPS version 1.1.19 or later must be installed on the SGD server. Additional configuration is required.
When printing from a Windows application that uses the Microsoft RDP protocol, SGD supports the printers supported by the Microsoft Windows application server.
SGD enables users to access a smart card reader attached to their client device from applications running on a Windows Server 2003 application server. Users can do the following:
Access the data on a smart card while using an application running on a Windows 2003 Server, for example, to use a certificate for signing or encrypting an email.
SGD works with any Personal Computer Smart Card (PCSC)-compliant smart card and reader.
Logging on to a Windows Server 2003 application server using a smart card has been tested successfully with smart cards listed in the following table.
Client Operating System and Libraries | Smart Card |
---|---|
Microsoft Windows XP Vista | ActivCard 64K |
Microsoft Windows XP Professional | ActivCard 64K |
Microsoft Windows 2000 Professional | ActivCard 64K |
Solaris OS with Sun
Ray![]() |
ActivCard 64K |
Fedora Linux with pcsc-lite 1.2.0 | ActivCard 64K |
Copyright © 2008, Sun Microsystems, Inc. All rights reserved.