Secure Global Desktop 4.40 Administration Guide > Clients and Webtops > Working with the SGD Client
The SGD Client is the part of SGD that is installed on client devices and is required to run applications. This page includes the following topics:
The SGD Client can operate in either of the following modes:
Depending on the client platform, users see an icon in the System tray or Workspace switcher when the SGD Client is running.
The SGD Client performs the following functions:
The SGD Client can be installed automatically or manually.
If you have a web browser with Java™ technology enabled, the SGD Client is installed automatically when you
http://server.example.com/sgd URL, where
server.example.com is the name of an SGD server.
Note If you use Internet Explorer on Microsoft Windows Vista platforms, you must add the SGD server to the list of Trusted Sites in Internet Explorer's Security Settings before the SGD Client can be automatically downloaded and installed.
With automatic installation, different versions of the SGD Client are installed in separate directories. This means:
The SGD Client is installed in the following directories:
homedrive\Documents and Settings\username\Local Settings\Temp\tcc\version
The actual location depends on the user's privileges, the operating system, and the Java Plug-in being used.
Note If the user has a roaming user profile, see Microsoft Windows Users With Roaming Profiles.
If you want to use automatic installation and have more control over where the SGD Client is installed, you can develop your own web application for installing the SGD Client and use SGD web services to specify the installation location.
Users with Microsoft Windows client devices can have roaming user profiles. Roaming user profiles provide the user with the same working environment, no matter which Microsoft Windows computer they use. If Microsoft Windows users have roaming user profiles, the SGD Client is installed by default in a directory that is deleted when the user logs off. To allow the SGD Client to be installed automatically in a directory that is roamed, you must perform the following configuration:
# cp webtopsession.jsp ~webtopsession.jsp
tccRoamingline to the following:
String tccRoaming = "true";
After making this change, the SGD Client is installed in the following directory on Microsoft Windows client devices:
homedrive\Documents and Settings\username\Application Data\Temp\tcc\version
With manual installation, you have full control over where the SGD Client is installed. You download and install the
SGD Client from the SGD Web Server home page,
http://server.example.com. Click the Install the Sun Secure Global Desktop Client link.
The Sun Secure Global Desktop Client download page has instructions for downloading and installing the SGD Client.
On Microsoft Windows client devices, the default installation directory is:
homedrive\Program Files\Sun\Secure Global Desktop Client.
A shortcut for the SGD Client is also added to the Windows Start Menu.
Note Manual installation is not available for all supported client platforms.
The SGD Client needs to be configured so that it can connect to an SGD server. The connection settings are defined in a client profile that is stored on the client device. The profile controls the following:
Note The SGD Client can only connect to an SGD server if they both have the same major/patch (4.xx) version number.
There is one profile for each SGD server that the user connects to. The profile is downloaded when the user connects to a SGD server. If the SGD Client has been installed manually, the user is prompted for initial connection information the first time the SGD Client is started.
Typically users log in to SGD by starting a web browser and visiting the
Connecting to SGD in this way, automatically downloads and starts the SGD Client.
However, you can also start the SGD Client from the command line and connect to an SGD server.
You can run the SGD Client in either Webtop mode and Integrated mode in this way.
You start the SGD Client with the
tcc command on Microsoft Windows client platforms
ttatcc command on UNIX/Linux/Mac OS X client platforms, as follows:
tcc [ -profile name ] [ -loginurl url ] [ -preferredlanguage lang ] [ -logdir file ] [ -use-java ] [ -version ] [ -help ]
||The name of the profile to use when starting the SGD Client.
Currently there is only one profile for each SGD server, called Default.
To specify the profile for a particular server, use
Note Profile names are case sensitive.
||The login URL. This overrides the URL defined in the profile.|
||The language to use in any dialogs and messages displayed by the SGD Client.
This overrides the language defined in the profile. The following are the supported languages:
||The directory in which the SGD Client log file is created.|
||Enable the detection of Java technology in the SGD Client.|
||Displays the version number of the SGD Client.|
||Displays help information.|
Note The arguments are case-sensitive.
The command line does not allow you to supply a user name and password. However, the SGD Client can be configured to log a user in automatically.
The command line for the SGD Client can be used to create your own shortcuts and shell scripts. The following are some example commands:
Note If either the Connect on System Login or the Add applications to Start Menu options are enabled in a user's profile, the SGD Client automatically adds shortcuts for itself in the user's desktop Start Menu. The Sun Secure Global Desktop Software Release Notes has details of which desktop systems are supported.
ttatcc -profile server.example.com::Default
server.example.com, available from the user's profile cache.
server.example.com, the SGD Client starts and connects to the last SGD server the user connected to using the profile for that server.
tcc -loginurl URL
The SGD Client also supports the following command-line arguments which are useful only when developing applications with SGD web services:
Note The arguments are case-sensitive.
||The port on which the SGD Client is to connect to the SGD server. Usually this is TCP port 5307 when the user has a secure connection to SGD, otherwise TCP port 3144 is used.|
||Create a secure connection to the SGD server.|
||The base network route the SGD Client is to use to traverse a SOCKS proxy server.|
||Indicates that the SGD server is using firewall forwarding. Connections to the SGD server and the webtop both use the same port, usually port 443/tcp.|
||Supplies the cookie used by the SGD server to identify the user session for which the SGD Client is being used.|
||The name of a file into which the SGD Client writes its listening port number.|
||For use with Mac OS X client devices only. Ensures an X server is running.|
||The fully-qualified DNS name of the SGD server.|
When using a web browser with Java technology enabled, the SGD Client is supported by the Sun Secure Global Desktop Client Helper, which is a Java applet.
The Sun Secure Global Desktop Client Helper performs the following functions:
The Sun Secure Global Desktop Client Helper is optional, see Can I use the webtop without Java technology? for details.
Copyright © 1997-2007 Sun Microsystems, Inc. All rights reserved.