3. Publishing Applications to Users
Configuring Windows Application Objects
Creating Windows Application Objects on the Command Line
Configuring Microsoft Windows Terminal Services for Use With SGD
Session Resumability and Session Directory
Multiple Terminal Services Sessions
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
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
Running Windows Applications on Client Devices
Configuring X Application Objects
Creating X Application Objects on the Command Line
Configuring Character Application Objects
Creating Character Application Objects on the Command Line
Terminal Emulator Keyboard Maps
Terminal Emulator Attribute Maps
How to Create Your Own Attribute Map
How to Create a Dynamic Application
Integrating SGD With Oracle VDI
How to Create a Dynamic Application Server for the VDI Broker
How to Set Global SSH Client Options
How to Set Application SSH Client Options
Enabling X11 Forwarding for X Applications
Using SSH and the X Security Extension
How to Enable the X Security Extension
Known Limitation With Client Keys
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 Multihead Or Dual Head Monitors
Configuring the Correct Desktop Size
Configuring Desktop Size for Client Window Management Applications
Configuring Desktop Size for Kiosk Mode Applications
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
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 the Login Script Used for the Application
Configuring the Transport Variable in the Login Script
Checking the Configuration of the Application Object
Checking the Launch Details and Error Logs
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
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 X Application Uses Too Much Bandwidth
8-bit Applications Exit With a PseudoColor Visual Error
Clipped Windows With Client Window Management Applications
Display Update Issues When Shadowing Over a Low Bandwidth Connection
Troubleshooting Mouse Drag Delay Issues
Incorrect Time Zone Name Shown in Windows Applications
7. SGD Servers, Arrays, and Load Balancing
B. Secure Global Desktop Server Settings
This section describes how to configure X application objects.
This section includes the following topics:
In the Administration Console, the configuration settings for X application objects are divided into the following tabs:
General tab – These settings control the name and the icon used when creating links for users
Launch tab – These settings control how the application is started and whether application sessions can be suspended and resumed
Presentation tab – These settings control how the application is displayed to users
Performance tab – These settings are used to optimize the performance of the application
Client Device tab – These settings control how the user’s client device interacts with the application
The following table lists the most commonly used settings for configuring X application objects and how to use them.
|
In addition to this configuration, you can also configure the following:
Printing – See Printing.
Client drives – See Client Drive Mapping.
Audio – See Audio.
Copy and paste – See Copy and Paste.
On the command line, you create an X application object with the tarantella object new_xapp
command. You can also create multiple X application objects at the same time
with the tarantella object script command. See Populating the SGD Organizational Hierarchy Using a Batch Script.
X application objects can only be created in the o=applications organizational hierarchy.
The supported X extensions are listed in the Oracle Secure Global Desktop 4.6 Platform Support and Release Notes available at http://docs.sun.com/app/docs/doc/821-1928.
By default, SGD secures X displays using X authorization. This prevents users from accessing X displays that they are not authorized to access.
For information about troubleshooting X authorization for X applications, see Applications Fail To Start When X Authorization Is Enabled.
SGD includes the standard X Window System fonts in compiled and compressed form (.pcf.gz), together with some additional fonts required by different UNIX systems. See Fonts in X11R6.8.2 for details. The fonts are installed in the /opt/tarantella/etc/fonts directory.
The following X fonts and font directories are available with SGD.
|
You can make your own X fonts available through SGD in the following ways:
Use a font directory, see Using a Font Directory
Use a font server, see Using a Font Server
After making the X fonts available, you must configure each SGD server in
the array to use the fonts, see How to Configure SGD to Use Your Own X Fonts.
To use a font directory, copy your fonts in .pcf format to a directory on each SGD server in the array and include a fonts.dir file that maps filenames to X logical font descriptions.
The fonts can be gzipped (.pcf.gz), but fonts compressed using the compress command (.pcf.Z) are not supported. If a font is compressed in a .Z file, decompress it first before copying to the SGD server.
The following is an example line from a fonts.dir file:
COURBO10.pcf -Adobe-Courier-Bold-0-Normal-10-100-75-75-M-60-ISO8859-1
If your font directory does not include a fonts.dir file, you can use a program such as mkfontdir, which is available for most UNIX systems, to create one.
You can also include a fonts.alias file, that specifies aliases for the fonts in the directory. This file maps aliases to X logical font descriptions. For example:
variable *-helvetica-bold-r-normal-*-*-140-*
A font server is a program that makes fonts on a host available on the network. Font servers make font administration easier by centralizing fonts, reducing duplication.
To name a font server in a font path, you need to know the name of the font server and the port on which fonts are being served. For example, if the font server boston uses Transmission Control Protocol (TCP) port 7100, add the font path entry tcp/boston:7100.
Ensure that no users are logged in to the SGD server, and that there are no application sessions, including suspended application sessions, running on the SGD server.
Each SGD server in the array can use a different font path. However, to avoid inconsistent display of applications, ensure that the same fonts, in the same order, are available to all SGD servers.
Use the xset command to see if the font path is set.
$ xset q
SGD uses a keyboard map, or keymap, file to process keyboard input for X applications. A keymap file contains a list of keys for the keyboard and the corresponding characters produced when you press the keys.
By default, an SGD server uses the keymap file corresponding to the locale specified by the Keyboard Map attribute on the Protocol Engines -> X tab for the SGD server in the Administration Console.
The available locale settings are:
LANG Variable – Use the locale of the SGD server. This is the value of the LANG environment variable on the SGD server.
Client’s Input Locale – Use the locale of the client device.
Select Custom Keyboard Map – Specify your own keyboard map.
You can override the locale for a particular user, by setting the Keyboard Map (--keymap) attribute for the user profile object
To prevent an application from changing the default keyboard mappings, set the Keyboard Map: Locked (--lockkeymap) attribute for the application object.
Keymap files are located in the /opt/tarantella/etc/data/keymaps directory on the SGD server. This directory contains keymap files for the most common keyboard layouts. The keymap files in this directory have a file name beginning with x. For example, xuniversal.txt keymap file is used to map the keys of a Universal (English US) keyboard.
SGD uses the /opt/tarantella/etc/data/keymaps/xlocales.txt file to find the keymap file for the specified locale. This file maps locales to keymap files. For example, the xlocales.txt specifies the xuniversal.txt keymap file for a locale setting of en_US.