Exit Print View

Oracle Secure Global Desktop Administration Guide for Version 4.6

Document Information

Preface

1.  Networking and Security

2.  User Authentication

3.  Publishing Applications to Users

4.  Configuring Applications

5.  Client Device Support

6.  SGD Client and Webtop

The SGD Client

Overview of the SGD Client

Configuring the SGD Client

The SGD Client Helper

Installing the SGD Client

Automatic Installation of the SGD Client

How to Enable Automatic Installation for Roaming User Profiles

Manual Installation of the SGD Client

Running the SGD Client From the Command Line

Command-Line Examples

Starting the SGD Client Without Any Arguments

Connecting to a Particular SGD Server

Overriding the Login URL

Web Services Developer Options

Using SGD Without Java Technology

How to Use SGD Without Java Technology

Client Profiles

Client Profiles and the SGD Client

Managing Client Profiles

How to Configure Client Profile Editing for Users

Client Profile Settings

About the Profile Cache

Microsoft Windows Users With Roaming User Profiles

Integrated Mode

Working in Integrated Mode

Setting Up the SGD Client for Integrated Mode

Authentication Token Authentication

How Authentication Token Authentication Works

User Identity and User Profile

Authentication Tokens and Security

How to Enable Authentication Token Authentication

Administering Authentication Tokens

Troubleshooting Automatic Logins

Configuring the Client Profile for Integrated Mode

Configuring Applications for Integrated Mode

Webtops

Setting the Language for the Webtop

Overriding the Default Language for the Webtop

7.  SGD Servers, Arrays, and Load Balancing

A.  Global Settings and Caches

B.  Secure Global Desktop Server Settings

C.  User Profiles, Applications, and Application Servers

D.  Commands

E.  Login Scripts

F.  Third-Party Legal Notices

Glossary

Index

Webtops

The webtop is a JavaServer Pages (JSP) technology web application. The standard webtop can be customized, or you can develop your own using the SGD web services.

Setting the Language for the Webtop

By default, the SGD web server Welcome Page at http://server.example.com, where server.example.com is the name of an SGD server, is displayed in English.

To change the default language of the SGD web server Welcome Page, amend the symbolic link /opt/tarantella/webserver/apache/apache-version/htdocs/index.html, so that it links to another index page in this directory. For example, to make the default Welcome Page display in Japanese, link to the index_ja.html page.

When users log in using a browser at the http://server.example.com/sgd URL, where server.example.com is the name of an SGD server, the default language used for messages displayed by the login dialog and the webtop is controlled by the defaultlanguage parameter setting in the following file: /opt/tarantella/webserver/tomcat/tomcat-version/webapps/sgd/WEB-INF/web.xml

To change the default language, edit this file and replace the parameter value en with the language identifier for one of the following supported languages:

Language
Identifier
English
en
French
fr
German
de
Japanese
ja
Korean
ko
Simplified Chinese
zh_CN
Traditional Chinese
zh_TW

Save changes to the web.xml file and restart the SGD web server.

The default language is also controlled by the Preferred Language in the user’s client profile. Whenever the SGD Client is started from the command line, for example when the SGD Client is in Integrated mode, the language specified in the profile is used for messages displayed by the SGD Client, the login dialog, and the webtop. SGD Administrators can set the default language by editing the profiles in their organizational hierarchy. See also Client Profile Settings.


Note - To be able to display text for a locale, users must also have appropriate fonts installed on their client device.


Overriding the Default Language for the Webtop

Individual users can override the default language for the webtop in the following ways:


Note - When you override the default language, the login URL specified in the user’s client profile does not need to be changed. This is usually http://server.example.com/sgd, where server.example.com is the name of an SGD server.