Exit Print View

Oracle Secure Global Desktop Administration Guide for Version 4.6

Document Information


1.  Networking and Security

2.  User Authentication

3.  Publishing Applications to Users

4.  Configuring Applications

Windows Applications

Configuring Windows Application Objects

Creating Windows Application Objects on the Command Line

Configuring Microsoft Windows Terminal Services for Use With SGD

Authentication Settings

Session Resumability and Session Directory

Windows Printer Mapping

Drive Redirection

Encryption Level

Multiple Terminal Services Sessions

Remote Desktop Users

Time Zone Redirection

Audio Redirection

Smart Card Device Redirection

COM Port Mapping

Color Depth

Transport Layer Security

Terminal Services Group Policies

Keep Alive Configuration for Windows Terminal Servers

Licensing Microsoft Windows Terminal Services

Managing CALs From the Command-Line

Microsoft Windows Remote Desktop

Seamless Windows

Notes and Tips on Using Seamless Windows

Key Handling for Windows Terminal Services

Supported Keyboard Shortcuts for Windows Terminal Services

The Windows Key and Window Management Keys

Configuring Windows Keyboard Maps

Returning Client Device Information for Windows Terminal Services Sessions

The SGD Remote Desktop Client

Using a Configuration File

Running Windows Applications on Client Devices

X Applications

Configuring X Application Objects

Creating X Application Objects on the Command Line

Supported X Extensions

X Authorization

X Fonts

Using Your Own X Fonts

Using a Font Directory

Using a Font Server

How to Configure SGD to Use Your Own X Fonts

Keyboard Maps

Character Applications

Configuring Character Application Objects

Creating Character Application Objects on the Command Line

Terminal Emulator Keyboard Maps

Default Mappings

Creating a Keyboard Map

Key Names

Client Device Keys

Application Server Keystrokes

Terminal Emulator Attribute Maps

How to Create Your Own Attribute Map

Editing Character Attributes

Terminal Emulator Color Maps

Examples of Using Color Maps

Dynamic Launch

Dynamic Application Servers

SGD Broker

User-Defined SGD Broker

VDI Broker

Dynamic Applications

How to Create a Dynamic Application

Client Overrides

Using My Desktop

Integrating SGD With Oracle VDI

How to Create a Dynamic Application Server for the VDI Broker

Using SSH

SSH Support

Configuring the SSH Client

How to Set Global SSH Client Options

How to Set Application SSH Client Options

Enabling X11 Forwarding for X Applications

How to Enable X11 Forwarding

Using SSH and the X Security Extension

How to Enable the X Security Extension

Using SSH and X Authorization

Using Advanced SSH Functions

Known Limitation With Client Keys

Application Authentication

Login Scripts

Configuring Application Authentication

The Application Server Password Cache

Managing the Application Server Password Cache

Security and the Password Cache

Windows Domains and the Password Cache

Input Methods and UNIX Platform Applications

Adding Support for System Prompts in Different Languages

Using RSA SecurID for Application Authentication

Tips on Configuring Applications

Starting an Application or Desktop Session Without Displaying a Webtop

Using SGD Web Services

Using Multihead Or Dual Head Monitors

Disabling Shared Resources

Configuring the Correct Desktop Size

Configuring Desktop Size for Client Window Management Applications

Configuring Desktop Size for Kiosk Mode Applications

Setting Up the Monitors

Improving the Performance of Windows Applications

Improving the Performance of Java Desktop System Desktop Sessions or Applications

Configuring the X Application Object for Java Desktop System

Disabling Default Java Desktop System Settings

Documents and Web Applications

Creating a Virtual Classroom

How to Create the Teacher's Application Object

How to Create the Classroom Application Object

Configuring Common Desktop Environment Applications

Configuring a CDE Desktop Session

Configuring a CDE Application

Using CDE and SSH

Configuring VMS Applications

Configuring the Login Script Used for the Application

Configuring the Transport Variable in the Login Script

Disabling X Security

3270 and 5250 Applications

Troubleshooting Applications

An Application Does Not Start

Checking the Configuration of the Application Object

Checking the Launch Details and Error Logs

Increasing the Log Output

Troubleshooting ErrApplicationServerTimeout Errors

Troubleshooting ErrApplicationServerLoginFailed Errors

An Application Exits Immediately After Starting

Applications Fail To Start When X Authorization Is Enabled

Applications Disappear After About Two Minutes

An Application Session Does Not End When the User Exits an Application

Checking the Session Termination Setting

Windows Applications Do Not Close Down

UNIX Desktop Sessions Do Not Close Down After Logging Out

Users Can Start Applications With Different User Names and Passwords

Using Windows Terminal Services, Users Are Prompted for User Names and Passwords Too Often

SGD Prompts the User

Terminal Server Prompts the User

Using Shadowing to Troubleshoot a User's Problem

A Kiosk Application Is Not Appearing Full-Screen

An Application's Animation Appears 'Jumpy'

Font Problems with X Applications

Display Problems With High Color X Applications

The X Application Fails With a Color Planes Error

The Colors Appear Strange

The X Application Uses Too Much Bandwidth

8-bit Applications Exit With a PseudoColor Visual Error

Clipped Windows With Client Window Management Applications

Emulating a Sun Keyboard

Display Update Issues When Shadowing Over a Low Bandwidth Connection

Troubleshooting Mouse Drag Delay Issues

Incorrect Time Zone Name Shown in Windows Applications

5.  Client Device Support

6.  SGD Client and 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



Character Applications

This section describes how to configure character application objects. Terminal emulator mappings are also discussed.

This section includes the following topics:

Configuring Character Application Objects

You use a character application object if you want to give a VT420, Wyse 60, or SCO Console character application to users.

In the Administration Console, the configuration settings for character application objects are divided into the following tabs:

The following table lists the most commonly used settings for configuring character application objects and how to use them.

The name that users see.
The icon that users see.
Application Command
The full path to the application that runs when users click the link.

The application must be installed in the same location on all application servers.

See also Configuring VMS Applications for details of how to configure Virtual Memory System (VMS) character applications.

Arguments for Command
Any command-line arguments to use when starting the application.
Connection Method
The mechanism SGD uses to connect to the application server, for example telnet or ssh.
Number of Sessions
The number of instances of an application a user can run. The default is three.
Application Resumability
For how long the application is resumable. The following options are available:
  • Never – The application can never be resumed

  • During the User Session – The application keeps running and is resumable until the user logs out of SGD

  • General – The application keeps running for a time, controlled by a timeout value, after the user logs out of SGD, and can be resumed when the user next logs in

Window Close Action
What happens if the user closes the main application window using the Window Manager decoration. This attribute only applies for applications that use an Independent Window.
Window Type
How the application is displayed to the user.

If Independent Window is selected, you must specify a Height and Width for the Window Size or select the Client’s Maximum Size check box.

Specify the number of Columns and Lines to display in the terminal window.

Emulation Type
The type of character application to emulate. SGD supports VT420, Wyse 60, or SCO Console character applications.
Terminal Type
The application’s terminal type. Accept the default terminal type, or type you own type in the Custom field.
Application Load Balancing
How SGD chooses the best application server to run the application.

See Application Load Balancing for more details.

Hosting Application Servers tab
Use the Editable Assignments table to select the application servers, or group of application servers, that can run the application.

The application must be installed in the same location on all application servers.

Assigned User Profiles tab
Use the Editable Assignments table to select the users that can see the application. Selecting Directory or Directory (light) objects enables you to give the application to many users at once. You can also use an LDAP directory to assign applications. See LDAP Assignments.

To use and display the euro character, the terminal session must be capable of displaying 8-bit characters. To ensure this, enter the command stty -istrip. Also, the client device must be capable of entering the euro character.

Creating Character Application Objects on the Command Line

On the command line, you create a character application object with the tarantella object new_charapp command. You can also create multiple character application objects at the same time with the tarantella object script command. See Populating the SGD Organizational Hierarchy Using a Batch Script.

Character application objects can only be created in the o=applications organizational hierarchy.

Terminal Emulator Keyboard Maps

The SGD terminal emulators associate keys on the user’s client keyboard with keys found on a real terminal. For each type of terminal emulator: SCO Console, Wyse 60, and VT420, there is a default keyboard mapping.

To change the default mappings or define additional mappings for a particular application, you can specify your own keyboard map file using an object’s Keyboard Map attribute.

Default Mappings

The emulators have built-in keyboard maps, which are equivalent to the following sample keymap files in the /opt/tarantella/etc/data/keymaps directory:

Note - Modifying these keyboard maps does not alter the default mappings used by SGD. The only way to do this is to specify a keyboard map in an application object’s Keyboard Map attribute.

Creating a Keyboard Map

To create your own keyboard map, make a copy of one of the sample keyboard map files, and modify it to suit your application. You can modify a keyboard map in any text editor.

The format of a mapping is:


Where ClientKeys is the key, or keys, that the user presses on the client device, and Translation is the keystroke, or keystrokes, sent to the application on the application server. For example:


With this mapping, when the user presses the Page Down key the emulator sends the keystroke Next to the application server.

If a particular key has a user-defined mapping, the default settings are overridden. If no user-defined mapping is present, the default mapping is sent to the application server.

You can send complete strings on a single key press, by surrounding the string in straight quotation marks. For example:

F1="hello world"

To enter non-printable characters when mapping strings, use the code shown in the table below:

Carriage return
Line feed
Straight quotation marks
The character with octal value nnn
The character with hex value HH

To specify modifier keys, such as Shift, Control, and Alt, in a mapping, separate the keys with the plus sign, +. For example:

Key Names

The following are lists of key names that are valid in SGD keyboard maps. The Client Device Keys list shows the key names that represent keys on the user’s client device. These are the keys that can be mapped to the emulator key names given in Application Server Keystrokes, which are the keystrokes ultimately sent to the application on the application server.

Note - The default mappings between these key names are as found in the keyboard maps supplied with SGD. If a key is not in a keyboard map, then it is not mapped.

Client Device Keys

SGD supports the following keys on the user’s client device:

Application Server Keystrokes

The following application server keystrokes are supported for SCO Console applications:

The following application server keystrokes are supported for VT420 applications:

The following application server keystrokes are supported for Wyse 60 applications:

Terminal Emulator Attribute Maps

Terminal emulator attribute maps enable you to change how character attributes such as bold or underline are displayed in the SGD terminal emulators. For example, you can specify that text that normally appears bold and underlined appears red in the SGD terminal emulators, but not red and bold and underlined.

SGD provides a default attribute map /opt/tarantella/etc/data/attrmap.txt. This maps character attributes to the logical color Color_15 (white). You can also create your own attribute map.

How to Create Your Own Attribute Map

  1. As superuser (root), create a copy of /opt/tarantella/etc/data/attrmap.txt to work on.
  2. Edit the new file, so that character attributes map to your chosen colors.
  3. Use the name of the file for the application object’s Attribute Map attribute.
Editing Character Attributes

The SGD attribute maps enable you to map the following attributes:

To map combinations of attributes, separate the attributes with the plus sign +, for example, Bold+Underline.

To display colors in the terminal emulators, SGD maps logical colors to RGB values. For example, the logical color Color_9 maps to the RGB value 128 0 0 (red).

When mapping attributes to colors in your attribute map, specify the logical color name. For example:

For a complete list of logical color to RGB value mappings, refer to the comments in attrmap.txt.

You can change the default color mappings by editing the color map used by the terminal emulators. See Terminal Emulator Color Maps.

Note - Wyse 60 terminals display only black and white colors. However, you can use the SGD Wyse 60 terminal emulator to display colors in your Wyse 60 applications. You can do this by using the attribute map to map character attributes in the Wyse 60 application to colors.

Terminal Emulator Color Maps

SCO Console (ANSI) and VT420 terminals support 16 colors. The SGD terminal emulator uses a color map to determine how these colors are presented in an application session.

Note - Wyse 60 terminals are monochrome. You can only switch the background and foreground colors, black and white, using the color map. However, you can map character attributes such as bold or underline to any of the 16 logical colors supported by the terminal emulator. See Terminal Emulator Attribute Maps.

The color map maps the logical colors Color_0 through to Color_15, inclusive, to colors and the RGB values that SGD uses to represent those colors. The default mappings are as follows:

Logical Color
Terminal Color
RGB Value Used by SGD
0 0 0
Light red
255 0 0
Light green
0 255 0
255 255 0
Light blue
0 0 255
Light magenta
255 0 255
Light cyan
0 255 255
High white
255 255 255
128 128 128
128 0 0
0 128 0
128 128 0
0 0 128
128 0 128
0 128 128
192 192 192

To alter the defaults for a particular application, create your own color map, and specify it in the application object’s Color Map attribute.

A default text-format color map /opt/tarantella/etc/data/colormap.txt is provided.

Examples of Using Color Maps