4.2. X Applications

This section describes how to configure X application objects.

This section includes the following topics:

4.2.1. Configuring X Application Objects

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.

Attribute

Description

Name

The name that users see.

Icon

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.

The following are commonly used commands for desktop sessions:

  • /usr/dt/config/Xsession.jds – For a Java Desktop System (JDS) desktop

  • /usr/bin/gnome-session – For a Gnome desktop

  • /usr/bin/startkde – For a K Desktop Environment (KDE) desktop

See also Section 4.8.8, “Configuring Common Desktop Environment Applications”, and Section 4.8.9, “Configuring VMS Applications”.

Arguments for Command

Any command-line arguments to use when starting the application.

Note

Never specify a -display argument. This is set by SGD.

Connection Method

The mechanism SGD uses to connect to the application server, for example ssh or telnet.

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 the Timeout setting, after the user logs out of SGD, and can be resumed when the user next logs in

Session Termination

The circumstances when the SGD server ends the application session.

Window Type

How the application is displayed to the user.

Use Kiosk for full-screen desktop sessions. Selecting the Scale to Fit Window check box for the Window Size enables SGD to scale the application window to fit the client device display.

Use Client Window Management to display the application as though it is running on the client device.

For other window types, you must specify a Height and Width for the Window Size or select the Client's Maximum Size check box.

Color Depth

The application's color depth.

SGD supports X applications with multiple color depths. So you can run an 8-bit application within a 24-bit desktop session by selecting 24/8-bit, for example

Application Load Balancing

How SGD chooses the best application server to run the application.

See Section 7.2.3, “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 Section 3.2.2, “LDAP Assignments”.

In addition to this configuration, you can also configure the following:

4.2.1.1. Creating X Application Objects on the Command Line

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 Section 3.1.5, “Populating the SGD Organizational Hierarchy Using a Batch Script”.

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

4.2.2. Supported X Extensions

The supported X extensions are listed in the Oracle Secure Global Desktop Platform Support and Release Notes for Release 4.7 available at http://www.oracle.com/technetwork/documentation/sgd-193668.html.

4.2.3. X Authorization

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 Section 4.9.3, “Applications Fail To Start When X Authorization Is Enabled”.

4.2.4. X Fonts

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 X11R7.6 for details. The fonts are installed in the following directories:

  • /opt/tarantella/etc/fonts. Terminal emulator fonts used by SGD.

  • /opt/tarantella/etc/data/share/fonts/X11. Standard X Window System fonts.

The following X fonts and font directories are available with SGD.

Directory

Description

75dpi

Variable-pitch 75 dpi fonts

100dpi

Variable-pitch 100 dpi fonts

cyrillic

Cyrillic fonts

encodings

A set of encoding files used by the Type1 and TrueType font handlers

misc

Fixed-pitch fonts, cursor fonts, and fonts for compatibility with older versions of X

OTF

OpenType fonts

TTF

TrueType fonts

Type1

PostScript™ Type 1 fonts

util

ISO to Unicode mappings

4.2.4.1. Using Different X Fonts

You can use different X fonts with SGD in the following ways:

4.2.4.1.1. Using a Font Directory

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-*

See Section 4.2.4.1.3, “Using a Font Alias” for more details about using a font alias.

4.2.4.1.2. Using a Font Server

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 TCP port 7100, add the font path entry tcp/boston:7100.

4.2.4.1.3. Using a Font Alias

Instead of installing a specific font, you use a fonts.alias file to map to a similar font.

For example, if your X application uses the LucidaSans-TypewriterBold-14 font, which is not included with SGD, you might see error messages such as the following.

Unable to load font-name defaulting font to variable

To avoid these error messages, create an alias to map to a similar font, such as lucidasanstypewriter-bold-14.

Add the following entry to the fonts.alias file in the /opt/tarantella/etc/data/share/fonts/X11/100dpi directory on each SGD server in the array.

LucidaSans-TypewriterBold-14 \
-b&h-lucidatypewriter-bold-r-normal-sans-20-140-100-100-m-120-iso8859-1

Restart the SGD server after making changes.

4.2.4.1.4. How to Configure SGD to Use Your Own X Fonts

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.

  1. In the Administration Console, go to the Secure Global Desktop Servers tab and select an SGD server.

  2. Go to the Protocol Engines → X tab.

  3. In the Font Path field, type the path to the directory containing your X fonts, or the location of the font 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.

  4. Click Save.

  5. Restart the SGD server.

  6. Check the validity of the font path.

    Use the xset command to see if the font path is set.

    $ xset q

4.2.5. Keyboard Maps

SGD uses the XKB (X keyboard) X extension to process keyboard input for X applications.

SGD uses a rules file to process keyboard input for X applications. A rules file contains the required configuration to map keys on the keyboard to the corresponding characters produced when you press the keys.

Files for the XKB implementation used by SGD are located in the /opt/tarantella/etc/data/share/X11/xkb directory.

See the XKB documentation for more details about configuring and using XKB.

4.2.5.1. Configuring Keyboard Layouts

The XKB implementation supplied with SGD includes support for many popular keyboard layouts and locales.

By default, SGD selects a keyboard layout automatically, based on the locale and keyboard type used by the client device. If the selected keyboard layout is not appropriate for the client device, users can configure the keyboard layout using the Try to Match the Client Keyboard Layout client profile setting. See Section 6.2.4, “Client Profile Settings”.

Note

By default, the Try to Match the Client Keyboard Layout setting is enabled and should work well with most keyboards. Contact Oracle Support if you encounter issues when using the default setting.