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

7.  SGD Servers, Arrays, and Load Balancing

A.  Global Settings and Caches

B.  Secure Global Desktop Server Settings

Secure Global Desktop Servers Tab

The Secure Global Desktop Server List Table

General Tab

External DNS Names

User Login

Redirection URL

Security Tab

Connection Types

SSL Accelerator Support

Firewall Forwarding URL

Performance Tab

Maximum Simultaneous Requests

Maximum Simultaneous User Sessions

Maximum File Descriptors

JVM Size

Daily Resource Synchronization Time

Load Balancing Groups

Protocol Engines Tab

Character Protocol Engine Tab

Maximum Sessions

Exit Timeout

Command-Line Arguments

X Protocol Engine Tab

Monitor Resolution

Font Path

RGB Database

Keyboard Map

Client Window Size

Session Start Timeout

Maximum Sessions

Exit Timeout

Command-Line Arguments

Execution Protocol Engine Tab

Maximum Sessions

Exit Timeout

Login Script Directory

Command-Line Arguments

Channel Protocol Engine Tab

Packet Compression

Packet Compression Threshold

Exit Timeout

Print Protocol Engine Tab

Packet Compression

Packet Compression Threshold

Exit Timeout

Audio Protocol Engine Tab

Packet Compression

IO Protocol Engine Tab

Packet Compression

User Sessions Tab

The User Session List Table

Application Sessions Tab

The Application Session List Table

C.  User Profiles, Applications, and Application Servers

D.  Commands

E.  Login Scripts

F.  Third-Party Legal Notices

Glossary

Index

Execution Protocol Engine Tab

Use the attributes on the Execution Protocol Engine tab to tune application startup 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.

Maximum Sessions

Usage: Type a number in the field.

Description

The maximum number of application sessions each Execution Protocol Engine handles.

More Execution Protocol Engines are started to meet demand.

Command Line

Command option: --execpe-maxsessions num

Usage: Replace num with the maximum number of application sessions.

The following example specifies a maximum sessions setting of 10 for each Execution Protocol Engine.

--execpe-maxsessions 10

Exit Timeout

Usage: Type a number in the field.

Description

The length of time, in seconds, an Execution Protocol Engine process continues to run without any active connections.

Command Line

Command option: --execpe-exitafter secs

Usage: Replace secs with the time period, measured in seconds.

In the following example, the Protocol Engine exits after 60 seconds if there are no active connections.

--execpe-exitafter 60

Login Script Directory

Usage: Type a directory path name in the field.

Description

The directory on the SGD host where login scripts are stored.

Use %%INSTALLDIR%% to represent the SGD installation directory.

If an application object’s Login Script attribute uses a relative path name, for example unix.exp, this directory is assumed.

Only change this setting if Technical Support ask you to.

Command Line

Command option: --execpe-scriptdir dir

Usage: Replace dir with the path name for the login script directory.

In the following example, the login script directory for a default SGD installation is /opt/tarantella/var/serverresources/expect.

--execpe-scriptdir %%INSTALLDIR%%/var/serverresources/expect

Command-Line Arguments

Usage: Type command-line arguments in the field.

Description

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 Line

Command option: --execpe-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.

--execpe-args execpeerror.log