Settings on the Communication tab control connections between the client device, the SGD server, and application servers. They also control the resumability behavior for application sessions.
From the command line, use the Section D.17, “tarantella config list” command to list these settings, and the Section D.16, “tarantella config edit” command to edit these settings.
This tab contains the following sections:
Ports
This section contains the following attributes:
Application Sessions
This section contains the following attributes:
Synchronization
This section contains the Section A.4.6, “Resource Synchronization Service” attribute.
User Sessions
This section contains the Section A.4.7, “User Session Idle Timeout” attribute.
Usage: Enter a port number in the field.
Description
The TCP port number used for unencrypted connections between client devices and SGD servers.
Open this port in your firewall to enable connections from users who have standard connections. Standard connections are connections that do not use SSL.
You must restart every SGD server in the array for changes to this attribute to take effect.
The default is TCP port 3144.
Command Line
Command option:
--array-port-unencrypted
tcp-port
Usage: Replace
tcp-port with the port number to use
for unencrypted connections.
In the following example, TCP port 3144 is used for unencrypted connections.
--array-port-unencrypted 3144
Usage: Enter a port number in the field.
Description
The TCP port number used for encrypted connections between client devices and SGD servers.
Open this port in your firewall to enable connections from users who have secure (SSL-based) connections to SGD.
You must restart every SGD server in the array for changes to this attribute to take effect.
The default is TCP port 5307.
Command Line
Command option:
--array-port-encrypted
tcp-port
Usage: Replace
tcp-port with the port number to use
for encrypted connections.
In the following example, TCP port 5307 is used for encrypted connections.
--array-port-encrypted 5307
Usage: Enter a time period, measured in seconds, in the field.
Description
Determines how often a keepalive message is sent to client devices during application sessions. The default value is 100 seconds.
Some HTTP proxy servers close a connection if there is no activity on it. Using a keepalive ensures that a connection stays open.
Set this to 0 to disable keepalive messages.
This attribute is also used keep open connections between the SGD Client and the SGD server for client drive mapping.
You must restart every SGD server in the array for changes to this attribute to take effect.
Command Line
Command option:
--sessions-aipkeepalive
secs
Usage: Replace
secs with the keepalive time period,
measured in seconds.
In the following example, a keepalive message is sent to the client device every 100 seconds.
--sessions-aipkeepalive 100
Usage: Enter a timeout value, measured in minutes, in the field.
Description
For applications configured to be resumable during the user session, the length of time in minutes that a suspended application session is guaranteed to be resumable for if the connection to SGD is lost. Note that if the user logs out, the application sessions end. See the Section C.2.6, “Application Resumability” attribute.
After this period, the SGD server ends the session.
You can override this setting using the Section C.2.7, “Application Resumability: Timeout” attribute of an application.
If an application is terminated because the SGD Client exits unexpectedly or the connection is lost, an additional timeout of 20 minutes applies. See Table 7.1, “Application Resumability Scenarios”.
Changes to this attribute take effect immediately.
Command Line
Command option:
--sessions-timeout-session
mins
Usage: Replace
mins with the timeout value, measured
in minutes.
In the following example, the application session is resumable for 1440 minutes (24 hours).
--sessions-timeout-session 1440
Usage: Enter a timeout value, measured in minutes, in the field.
Description
For applications configured to be generally resumable, the length of time in minutes that a suspended application session is guaranteed to be resumable for after the user logs out or the connection to SGD is lost. See the Section C.2.6, “Application Resumability” attribute.
After this period the SGD server ends the session.
You can override this setting using the Section C.2.7, “Application Resumability: Timeout” attribute of an application.
If an application is terminated because the SGD Client exits unexpectedly or the connection is lost, an additional timeout of 20 minutes applies. See Table 7.1, “Application Resumability Scenarios”.
Changes to this attribute take effect immediately.
Command Line
Command option:
--sessions-timeout-always
mins
Usage: Replace
mins with the timeout value, measured
in minutes.
In the following example, the application session is resumable for 11500 minutes.
--sessions-timeout-always 11500
Usage: Select or deselect the check box.
Description
Whether to enable replication of resources for the array.
If enabled, synchronization starts at a time determined by the Section B.4.5, “Daily Resource Synchronization Time” for each SGD server in the array.
Resource synchronization is enabled by default.
Changes to this attribute take effect immediately.
Command Line
Command option:
--array-resourcesync 1 | 0
Usage: Specify
1 (true) or 0 (false).
The following example disables resource synchronization for the array.
--array-resourcesync 0
Usage: Enter a timeout value, measured in seconds, in the field.
Description
User sessions are ended automatically if there has been no application session or workspace activity for the specified time period. The timeout applies to all SGD servers in the array.
The user session idle timeout is disabled by default. A setting of 0 turns off the feature.
Do not configure an idle timeout that is less than 300 seconds (five minutes).
Activity on the following devices has no effect on the idle timeout period:
Serial ports
Smart cards
Audio
You must restart every SGD server in the array for changes to this attribute to take effect.
Command Line
Command option:
--webtop-session-idle-timeout
secs
Usage: Replace
secs with the timeout value, measured
in seconds.
In the following example, user sessions are ended automatically after being inactive for 1800 seconds, or 30 minutes.
--webtop-session-idle-timeout 1800