Dynamic launch is the term used to describe runtime changes that are applied when users start applications. Typically, the runtime changes enable users to select the application server that runs the application, or to choose the application that is started, or both. Configuring dynamic launch can involve dynamic application servers, dynamic applications, and client overrides.
This section covers the following topics:
A dynamic application server is an object that represents a virtual server broker (VSB). SGD uses the VSB to obtain a list of application servers that can run an application. If a user can select an application server, a chooser page is displayed that enables the user to specify the application server.
Dynamic application servers are created on the Application Servers tab of the Administration Console, or by using the tarantella object new_host --dynamic command.
The VSB used for a dynamic application server is specified using the Virtual Server Broker Class (--vsbclass) attribute. Any configurable parameters for the VSB are specified using the Virtual Server Broker Parameters (--vsbparams) attribute.
You only need to create one dynamic application server object for each VSB you are using. In general, you only create multiple dynamic application servers for the same VSB if you want to pass different parameters to the VSB.
The following VSBs are supplied with SGD:
SGD. This broker enables users to select an application server from the list of application servers assigned to the application.
See SGD Broker for more details about this VSB.
User-defined SGD. This broker enables users to specify an application server, or to select from the list of application servers assigned to the application.
See User-Defined SGD Broker for more details about this VSB.
VDI. This broker enables SGD to request a desktop from an Oracle Virtual Desktop Infrastructure (VDI) installation.
See VDI Broker for more details about this VSB.
You can develop your own VSB for use with SGD. Your broker must implement the IVirtualServerBroker interface that is included in the sgd-webservices.jar in the /opt/tarantella/bin/java/com/sco/tta/services/proxy directory.
Dynamic application servers are assigned to an application in the same way as conventional application servers, as described in How to Assign Application Servers to Applications.
Caution - Only assign one dynamic application server to an application.
Dynamic application servers override the normal SGD mechanisms for application load balancing because they enable users to choose where an application is run. To prevent application servers from becoming overloaded, you can use the attributes on an application server object to filter the application servers shown on the chooser page. See Dynamic Application Servers and Load Balancing for more details.
When dynamic application servers are used, entries in the SGD password cache are usually stored using the dynamic application server as well as the application server. But this can depend on the VSB and configured client overrides.
The SGD broker lists the application servers that are assigned to an application object. The dynamic application server itself is not listed.
The user experience when using the SGD broker is as follows:
When the user starts an application, a chooser page is displayed that lists the application servers that can run the application. The user must select an application server, and click the Start button to run the application.
If only one application server can run the application, the chooser page is not displayed. The application is automatically run on the application server.
If the application is a dynamic application, the user selects both the application and the application server.
On the command line, the fully-qualified class name (--vsbclass) for the SGD broker, is com.tarantella.tta.webservices.vsbim.SGDBroker.
The SGD broker does not have any configurable parameters.
When you install SGD, a default dynamic application server object called o=appservers/cn=SGD Broker is created automatically. This dynamic application server is used with the My Desktop application. See Using My Desktop for details.
The User-defined SGD broker lists the application servers that are assigned to an application object, and also enables users to specify the name or IP address of any application server. Users can run applications on application servers that do not have a corresponding application server object in the local repository. The dynamic application server itself is not listed.
The user experience when using the User-defined SGD broker is as follows:
When the user starts an application, a chooser page is displayed. The user either types the name or IP address of an application server in the field provided on the chooser page, or selects an application server from the list, and clicks the Start button to start the application.
If no SGD-configured application servers are available to the user, the user must type the name or IP address of an application server.
If the application is a dynamic application, the user must select both the application and the application server.
On the command line, the fully-qualified class name (--vsbclass) for the User-defined SGD broker is com.tarantella.tta.webservices.vsbim.UserDefinedSGDBroker.
The User-defined SGD broker has a one optional parameter. If you specify createAppserver for the Virtual Server Broker Parameters (--vsbparams) attribute, SGD automatically creates new application server objects for any user-specified application servers that do not already exist in the local repository.
The VDI broker enables SGD to request a desktop from a Oracle VDI installation. See Integrating SGD With Oracle VDI for details.
The user experience when using the VDI broker is as follows:
When the user starts an application, a login page is displayed. The user must type a VDI user name and password and click the Login button.
By default the user’s SGD credentials are tried, so the login page might not be displayed. SGD can also be configured to cache the VDI credentials, so that the authentication page only displays once for each user.
If the user is assigned multiple VDI desktops, whether a dedicated desktop or desktop pool, a chooser page is displayed that lists the available desktops. The user must select a desktop, and click the Start button to run the application.
If the user is assigned a single VDI desktop or desktop pool, the chooser page is not displayed. The VDI desktop is run automatically.
On the command line, the fully-qualified class name (--vsbclass) for the VDI broker is com.sun.sgd.vsbim.SunVDIVirtualServerBroker.
The VDI broker has a one mandatory parameter, the host name of a VDI server. When you create an dynamic application server for the VDI broker, specify localhost for the Virtual Server Broker Parameters (--vsbparams) attribute.
A dynamic application represents one or more application objects. When the user starts a dynamic application, a chooser page is displayed that enables the user to select an application to run.
A dynamic application object consists of a set of mappings between type strings and SGD application objects. For example, you could create a dynamic application to enable users to choose between a Windows desktop session or Linux desktop session. Such a dynamic application might use the mappings shown in the following table.
Dynamic applications are created on the Applications tab of the Administration Console, or by using the tarantella object new_dynamicapp command. See How to Create a Dynamic Application.
Type-application mappings for dynamic applications can be configured on the Mappings tab for the dynamic application object, or with the tarantella object add_mapping and tarantella object remove_mapping commands.
The type is a string that is specified when a mapping is added. Because the type is displayed on the chooser page, generally the type identifies the type of application. But it can be any unique string you want.
Dynamic applications are assigned to users in the same way as conventional applications, as described in Publishing Applications. You can assign multiple dynamic applications to a user.
When you install SGD, a default dynamic application object called o=applications/cn=My Desktop is created automatically and is used for the My Desktop application. See Using My Desktop for details.
Ensure that the applications that you want to map to the dynamic application already exist.
Use the navigation tree to select a directory object to contain the dynamic application.
The Create a New Object window is displayed.
The name you type is used for the link on the webtop.
The Create a New Object window closes and the content area is updated with the new object.
The General tab for the dynamic application object is displayed.
The icon is used on the webtop.
The Add a New Mapping window is displayed.
The string can be anything. The string is displayed on the chooser page that is displayed to users. Usually the type identifies the type of application.
Use the Navigation tree to browse for a directory object that contains the application.
You can only select application objects.
The Add a New Mapping window closes and the Mappings tab is updated with the new mapping.
Dynamic applications are assigned to users in the same way as conventional applications. See Publishing Applications.
Client overrides are a comma-separated list of options used to configure dynamic launch. By default, the client override to configure support for dynamic applications and dynamic application servers is enabled.
You use the following command to configure client overrides:
$ tarantella config edit \ --tarantella-config-applaunch-allowclientoverrides opt ...
where opt is a comma-separated list. The following table lists the available options.
For example, to disable all client overrides, use the following command:
$ tarantella config edit \ --tarantella-config-applaunch-allowclientoverrides false
For example, if you are integrating with Oracle VDI and you want SGD to read the password cache for the users’ VDI credentials, use the following command:
$ tarantella config edit \ --tarantella-config-applaunch-allowclientoverrides dynamic,dynamicappserver_pw
My Desktop enables users to log in and display a full-screen desktop without displaying a webtop.
To be able to use My Desktop, a user must be assigned an application object called My Desktop (cn=My Desktop).
A default My Desktop object (o=applications/cn=My Desktop) is created automatically when SGD is installed. This object is a dynamic application object that has the type-application mappings shown in the following table.
By default, this object runs the default desktop application available on the SGD server, as configured for the o=applications/cn=Unix Desktop application object. The windows type-application mapping for My Desktop is configured to run a Windows desktop application. However to be able to use Windows Desktop, you must first assign at least one application server object to the o=applications/cn=Windows Desktop application object. If you do this, users are prompted to choose which desktop application to run. See Dynamic Applications for more details.
You can reconfigure the default My Desktop object to run any application you want, but it works best with full-screen desktop applications. If users require different desktop applications, you can create additional My Desktop objects as required.
Users access My Desktop from their webtop or by using the My Desktop URL, at http://server.example.com/sgd/mydesktop, where server.example.com is the name of an SGD server. This Uniform Resource Locator (URL) displays the SGD Login page. Once the user has logged in, selected an application and application server (if configured), the desktop session is displayed. After the user has logged in, the browser window can be closed.
Alternatively, users can click the My Desktop link on the SGD web server Welcome Page, at http://server.example.com.
Users can be assigned any number of applications, but the My Desktop URL only gives users access to the My Desktop application. To use the My Desktop URL, a user must be assigned only one application called My Desktop.
If the user has paused print jobs, they see a message in the browser window when they log in which enables them to resume printing. You can disable this feature by setting the following value in the mydesktop/index.jsp file, which is located in the /opt/tarantella/webserver/tomcat/tomcat-version/webapps/sgd/ directory.
SGD includes a VDI broker that enables you to give users access to desktops provided by an Oracle VDI server.
The supported versions of Oracle VDI are listed in the Oracle Secure Global Desktop 4.6 Platform Support and Release Notes available at http://docs.sun.com/app/docs/doc/821-1928.
To integrate SGD with VDI, SGD and VDI must be installed on the same host.
Integrating SGD with Oracle VDI involves the following configuration steps:
Create a Windows application object for use with VDI.
SGD connects to VDI using RDP and so you must use a Windows application object.
You could create an application object specifically for VDI integration, or you could adapt the My Desktop application. See Using My Desktop.
Create a dynamic application server for the VDI broker.
For information about dynamic application servers and the VDI broker, see Dynamic Application Servers.
Assign the VDI dynamic application server to the VDI Windows application
Dynamic application servers are assigned to applications in the same way as conventional application servers, as described in How to Assign Application Servers to Applications.
Caution - Ensure that only the VDI dynamic application server is assigned to the application. Remove any conventional application server assignments.
Assign the VDI Windows application object to users.
(Optional) Configure the client override to enable the caching of passwords.
By default, SGD prompts users for credentials every time they connect to a VDI desktop using the VDI broker. See Client Overrides.
Use the navigation tree to select a directory object to contain the dynamic application server.
The Create a New Object window displays.
For example, VDI Broker.
The Create a New Object window closes and the content area is updated with the new object.
The General tab for the dynamic application server object is displayed.
The VDI broker can only be used if SGD and Oracle VDI are installed on the same host.