| Exit Print View | |
Oracle Secure Global Desktop Administration Guide for Version 4.6 |
|
|
|
|
3. Publishing Applications to Users
7. SGD Servers, Arrays, and Load Balancing
B. Secure Global Desktop Server Settings
Secure Global Desktop Servers Tab
The Secure Global Desktop Server List Table
Maximum Simultaneous User Sessions
Daily Resource Synchronization Time
The Application Session List Table
Use attributes on the X Protocol Engine tab to tune graphical emulator processes.
From the command line, use the 
tarantella config list command to list these settings, and
the tarantella config edit command to edit these settings.
Changes to these attributes take effect for new Protocol Engines only. Existing Protocol Engines are not affected.
Usage: Type a number in the field.
The default monitor resolution, in dots per inch, to assume.
You can override this value using an application’s Monitor Resolution attribute.
Command option: --xpe-monitorresolution dpi
Usage: Replace dpi with the monitor resolution, in dots per inch.
The following example specifies a monitor resolution of 96 dots per inch.
--xpe-monitorresolution 96
Usage: Type path names for the fonts directories in the field.
Directories on the SGD host containing the fonts used by the X Protocol Engine.
Font paths are listed in search order.
Use %%INSTALLDIR%% to represent the SGD installation directory.
You can include font servers, for example, tcp/boston:7000.
Command option: --xpe-fontpath fontpath
Usage: Replace fontpath with a list of font directories. Separate each directory in the font path with a comma “,”.
The following example specifies a list of font directories used by the X Protocol Engine.
--xpe-fontpath %%INSTALLDIR%%/etc/fonts/misc,\ %%INSTALLDIR%%/etc/fonts/TTF,%%INSTALLDIR%%/etc/fonts/Type1
Usage: Type the path name of the RGB database file in the field.
Full path name on the SGD host of the RGB database used by the X Protocol Engine to resolve color names to RGB values.
Use %%INSTALLDIR%% to represent the SGD installation directory.
Command option: --xpe-rgbdatabase file
Usage: Replace file with the full path name of the RGB database file.
The following example specifies the RGB database used by the X Protocol Engine.
--xpe-rgbdatabase %%INSTALLDIR%%/etc/data/rgb.txt
Usage: Select the required keyboard map option. For custom keyboard maps, type a file name in the field.
The default keyboard map to use for graphical applications.
To specify a keyboard map based on a locale, do one of the following:
Select LANG Variable to use the locale of the SGD server
Select Client’s Input Locale to use the locale of the client device
The actual keyboard map used is determined using the /opt/tarantella/etc/data/keymaps/xlocales.txt file.
Note - You can use the * and ? wildcards in the xlocales.txt file to support a wide range of input locales. See the xlocales.txt file for details.
Alternatively, you can type a filename to always use a particular keyboard map.
You can override this for each user with the user profile object’s Keyboard Map
attribute.
Command option: --xpe-keymap lang | client-locale | file
Usage: Specify a valid setting. For custom keyboard maps, replace file with the full path name of the keyboard map file.
In the following example, a keyboard map based on the locale of the client device is used.
--xpe-keymap client-locale
Usage: Type numbers for horizontal and vertical display sizes, in pixels, in the fields.
The maximum expected horizontal and vertical display resolution for client devices connecting to this server.
Use these attributes to tune the Client Window Management value of the Window Type
attribute.
These attributes only apply for applications with Window Type set to Client Window Management. Use them to avoid clipping problems.
Command option: --xpe-cwm-maxwidth pixels
Command option: --xpe-cwm-maxheight pixels
Usage: Replace pixels with a value for maximum display width or maximum display height.
The following example specifies a maximum display size of 1280 x 960 pixels.
--xpe-cwm-maxwidth 1280 --xpe-cwm-maxheight 960
Usage: Type a number in the field.
How long the X Protocol Engine waits for X applications to connect, in seconds.
Command option: --xpe-sessionstarttimeout seconds
Usage: Replace seconds with a timeout value, in seconds.
The following example specifies a timeout value of 60 seconds when starting an X session.
--xpe-sessionstarttimeout 60
Usage: Type a number in the field.
The maximum number of application sessions each X Protocol Engine handles.
More X Protocol Engines are started to meet demand.
Command option: --xpe-maxsessions num
Usage: Replace num with the maximum number of application sessions.
The following example specifies a maximum sessions setting of 20 for each X Protocol Engine.
--xpe-maxsessions 20
Usage: Type a number in the field.
The length of time, in seconds, an X Protocol Engine process continues to run without any active connections.
Command option: --xpe-exitafter secs
Usage: Replace num with the time period, measured in seconds.
In the following example, the Protocol Engine exits after 60 seconds if there are no active connections.
--xpe-exitafter 60
Usage: Type command-line arguments in the field.
Any arguments to the Protocol Engine. For example, the name of a log file.
Only change this setting if Technical Support ask you to.
Command option: --xpe-args args
Usage: Replace args with the arguments to pass to the Protocol Engine.
The following example specifies an error log file for the Protocol Engine.
--xpe-args xpeerror.log
|
|
