Login Scripts Supplied With SGD
All login scripts supplied with SGD are stored in the /opt/tarantella/var/serverresources/expect directory.
SGD login scripts are written in Tcl (version 8.4) and Expect (version 5.43).
Expect extends Tcl and provides additional commands for interacting with programs.
For more information about Tcl, see the Tcl Developer Exchange.
For more information about Expect, see The Expect Home Page.
The login scripts can be divided into the scripts that can be used
when configuring applications and the scripts that contain common code. The available scripts
are described in the following sections.
Login Scripts Used When Configuring Applications
You configure the login script that is used for an application as follows:
-
In the Administration Console, use the Login Script script attribute on the Launch tab for the application object.
-
On the command line, use the --login script command option with the tarantella object commands.
The following table lists the login scripts supplied with SGD that you can
set as the Login Script attribute for an application object, and a description
of what they are used for.
|
|
|---|
unix.exp |
The standard login script for character and
X applications. If the Login Script attribute is blank, this script is used by
default. Can be used with all application Connection Methods. |
securid.exp |
|
windows.exp |
The standard login script for
Windows applications If the Login Script attribute is blank, this script is used by default. |
3270.exp |
The
standard login script for 3270 applications. If the Login Script attribute is blank,
this script is used by default. Can be used with all application Connection Methods. The
script builds a command to run the TeemTalk for UNIX platform terminal emulation
software. |
5250.exp |
The standard login script for 5250 applications. If the Login Script attribute is
blank, this script is used by default. Can be used with all application Connection
Methods. The script builds a command to run the TeemTalk for UNIX platform
terminal emulation software. |
vms.exp |
Used for X or character applications running on Virtual Memory System (VMS)
application servers. Can be used for all application Connection Methods except rexec. See  Configuring VMS Applications. |
vmsrexec.exp |
Used
for X or character applications running on VMS application servers. Can only be used
if the application Connection Method is rexec. See Configuring VMS Applications. |
unixclass.exp |
|
winclass.exp |
|
pupil.exp |
|
|
Login Scripts Containing Common Code
The following table lists the login scripts supplied with SGD that contain common
code and a description of what they are used for. These scripts must
not be set as the Login Script attribute for an application object.
|
|
|---|
runsubscript.exp |
The
standard wrapper login script used to call all the other SGD login scripts. Sets
the environment variables the login scripts are allowed to use. |
procs.exp |
Called by other scripts. Defines
common Tcl procedures. |
vars.exp |
Called by other scripts. Defines the variables, messages, and timeouts used
by the other login scripts. |
securid-vars.exp |
Called by securid.exp. Defines additional variables and messages needed for
SecurID authentication. |
xauth.exp |
Called by procs.exp and classroom.exp. Used to handle the X authorization process,
including the X authorization permissions for shadowing. |
classroom.exp |
Called by unixclass.exp, winclass.exp, and pupil.exp. Defines common procedures
for retrieving the X display to shadow. |
unixwin.exp |
Used for Windows applications configured to use the
Citrix Independent Computing Architecture (ICA) protocol. This script assumes that the user’s PATH
includes the directory where the Merge or ICA UNIX client software is installed. Although
SGD no longer supports the SCO Merge or Citrix ICA protocols, legacy Windows
application objects can continue to use them. |
wcpwts.exp |
Called by windows.exp for Windows applications configured
to use the Microsoft Remote Desktop Protocol (RDP) protocol. |
wincenter.exp |
Used for Windows applications configured to
use the WinCenter or Citrix UNIX Integration Services protocol. Although SGD no longer
supports the WinCenter and Citrix UNIX Integration Services protocols, legacy Windows application objects
can continue to use them. |
|
