Application Session Load Balancing. Defining the Application Servers to Run the Application. Selecting the Load Balancing Method. Load Balancing Groups. How Application Load Balancing Works. Dynamic Application Servers and Load Balancing. Application Server Availability. The Relative Power of the Application Servers.
Example Relative Power Calculation 1. Example Relative Power Calculation 2. Fewest Application Sessions. How Advanced Load Management Works. Tuning Application Load Balancing. Application Server's Relative Power. Load Balancing Listening Ports. Frequency of the Load Calculation. Frequency of Updates to Array Members. Editing Application Load Balancing Properties. The httpd. Using the Administration Console. Supported Browsers for the Administration Console.
Starting the Administration Console. Administration Console Configuration Settings. Synchronization Wait Period. Securing Access to the Administration Console.
The CA Certificate Truststore. The Client Certificate Store. Binaries, Scripts, and Template Files. Troubleshooting Arrays and Load Balancing. Enabling Array Resilience Logging. Troubleshooting Clock Synchronization Issues. Troubleshooting Advanced Load Management. Users Cannot Relocate Their Sessions. Global Settings and Caches.
Secure Global Desktop Server Settings. User Profiles, Applications, and Application Servers. Third-Party Legal Notices. This section describes the SGD datastore, how to monitor user activity, and how to configure logging. User Sessions and Application Sessions. Using Log Filters for Auditing.
Information about users, applications, application servers, and webtops is stored on disk in the local repository. Information about user and application sessions is stored in memory. The datastore is organized into namespaces which are displayed and used on the command line and log files. The general structure is The namespace indicates the source of the information, such as DNS.
After the namespace, names are written using whichever naming scheme is appropriate to the namespace. Names are written like file system paths slash-separated and top-down. This section describes the differences between user sessions and application sessions in SGD. Using the Administration Console and the command line to monitor and control user and application sessions is also covered.
Anonymous Users and Shared Users. User sessions are hosted by the SGD server the user logs in to. The user name and password they type determine the type of user they are. See Chapter 2, User Authentication for more details about user authentication. If a user logs in and they already have a user session, the user session is transferred to the new SGD server and the old session ends. This is sometimes called session moving , or session grabbing. User sessions can be standard sessions or secure sessions.
Secure sessions are only available when SGD security services are enabled. The User Sessions tab for a user profile shows all the user sessions associated with the user profile. The Sessions tab and User Sessions tab enable you to select and end user sessions.
The User Sessions tab enables you to view further details about the user session. For example, the information that the SGD Client detects about the client device. On the command line, you use the tarantella webtopsession command to list and end user sessions. You can configure an idle timeout period for inactive user sessions.
The timeout is disabled by default for an SGD array. Replace secs with the timeout value, measured in seconds. A setting of 0 turns off the user session idle timeout feature. This is the default setting. An application session begins when a user starts an application and ends when the application exits. Each application session corresponds to an application currently running through SGD.
An application session can be hosted by any SGD server in the array. This might not be the same SGD server that the user logged in to, see Arrays.
The following example stops and then restarts the SGD server, without displaying any messages. The following example adds a link for the Write-o-Win application to the assigned applications for members of the Global Administrators role. All rights reserved. Legal Notices. The tarantella Command Prev Appendix D. Commands Next. Please enable JavaScript to enjoy all the features of this site. Option Description --setting value Previous tarantella config. Up Commands.
Next tarantella config list. Configuring Applications 5. Client Device Support 6. SGD Client and Webtop 7. Global Settings and Caches B. The tarantella config Command The tarantella config command lists and configures global settings, and also server-specific settings for any SGD server in the array. Syntax tarantella config list edit Description The following table shows the available subcommands for this command.
When configuring a server-specific attribute, applies the change to all SGD servers in the array. When configuring a server-specific attribute, applies the change to each named serv in the array. Names an attribute you want to list the value of.
If no --setting is specified, all global and server-specific attributes are listed. Lists server-specific attributes for the specified SGD server in the array. If omitted, lists server-specific attributes for the SGD server where the command is run.
0コメント