Use the attributes on the Execution Protocol Engine tab to tune application startup processes.
From the command line, use the Section D.16, “tarantella config list” command to list these settings, and the Section D.15, “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 maximum number of application sessions each Execution Protocol Engine handles.
More Execution Protocol Engines are started to meet demand.
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
Usage: Type a number in the field.
The length of time, in seconds, an Execution Protocol Engine process continues to run without any active connections.
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
Usage: Type a directory path name in the field.
The directory on the SGD host where login scripts are stored.
Use %%INSTALLDIR%%
to represent the
SGD installation directory.
If an application object's Section C.2.73, “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 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
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:
--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