4.8 Tips on Configuring Applications

This section contains tips on configuring applications and documents for use with SGD. This section includes the following topics:

4.8.1 Starting an Application or Desktop Session Without Displaying a Workspace

With SGD, you can start a single application or a full-screen desktop session without displaying the workspace. You can do this in any of the following ways:

  • Use My Desktop – My Desktop enables users to log in and display an application without displaying a workspace. Typically this is used for full-screen desktop applications. See Section 4.5.7, “Using My Desktop” for details.

  • Use SGD web services – Develop your own application for starting a single application from a URL. You can use this method to start an application from a bookmark or a favorite.

4.8.2 Using RANDR for Multiple Monitor Displays

SGD supports the RANDR X extension for multiple monitor displays. Using RANDR is the easiest way to configure SGD to work with multiple monitor displays.

To configure SGD to work with multiple monitors, perform the following configuration steps:

  1. (Optional) Configure the maximum display size.

  2. (Optional) Configure the array to use RANDR.

    By default, using the RANDR extension is enabled for the array.

  3. Configure the application objects to use RANDR.

4.8.2.1 Configure the Maximum Display Size

To avoid problems with clipped windows, you might want to increase the display resolution for the X Protocol Engine.

In the Administration Console, go to the Protocol Engines, X tab for each SGD server in the array and change the Client Window Size settings. In the Maximum Height and Maximum Width fields, enter the highest display resolution you expect to support.

Note

Increasing the Maximum Width and Maximum Height attributes increases the memory requirements for applications on both client devices and SGD servers.

Alternatively, use the following command:

$ tarantella config edit --array \
--xpe-cwm-maxwidth pixels \
--xpe-cwm-maxheight pixels

The following example specifies a maximum display size of 3200 x 2048 pixels.

$ tarantella config edit --array \
--xpe-cwm-maxwidth 3200 \
--xpe-cwm-maxheight 2048

Repeat the configuration for each application that is displayed on multiple monitors.

4.8.2.2 Enable RANDR for the Array

By default, using the RANDR extension is enabled for the array.

Go to the Global Settings, Client Device tab in the Administration Console and select the RandR Extension check box.

You can also use the following command to to enable RANDR for the array:

tarantella config edit --array-xrandr-enabled 1

4.8.2.3 Enable the RANDR Extension for Applications

In the Administration Console, go to the Presentation tab for the application object and select the Window Size: RandR Extension check box.

You can also use the following command to enable RANDR for an application object:

$ tarantella object edit --name app-name --xrandr 1

4.8.3 Configuring Multiple Monitor Displays Without Using RANDR

The easiest way to configure SGD to work with multiple monitor displays is to use the RANDR extension, as described in Section 4.8.2, “Using RANDR for Multiple Monitor Displays”.

In some situations you may not want to or may not be able to use RANDR. This topic describes an alternative configuration method that does not use RANDR.

You can use multihead or dual head monitors with SGD. However, if any of your applications are configured with a Window Type (--displayusing) setting of Client Window Management, Seamless Window, or Kiosk, you might have to change the application and monitor configuration to be able to use multiple monitors.

To configure multiple monitors to work with these applications, perform the following configuration steps:

  1. (Optional) Disable shared resources.

    Sharing resources is not available for Windows applications.

  2. Configure the correct desktop size.

  3. Set up the monitors.

4.8.3.1 Disabling Shared Resources

SGD enables similar applications to share resources, to reduce memory overhead. This feature must be disabled for any applications that you want to display using multiple monitors.

In the Administration Console, go to the Performance tab for the application that is displayed on multiple monitors and deselect the Share Resources Between Similar Sessions check box.

Alternatively, use the following command:

$ tarantella object edit --name obj --share false

Repeat the configuration for each application that is displayed on multiple monitors.

4.8.3.2 Configuring the Correct Desktop Size

You must ensure that the SGD server sends the client device enough space to display all the monitors on the desktop.

Note

This increases the amount of memory used on the client device and on the SGD server.

You must configure SGD so that it sends the size of the entire desktop area to the client device, and not just the size of the primary monitor. The size of the entire desktop area is shown by the "virtual screen" in Figure 4.3, “Virtual Screen Size for Multihead Monitors”.

Figure 4.3 Virtual Screen Size for Multihead Monitors

Virtual Screen Size for Multihead Monitors

For example, if the dimensions of Monitor 1 in the diagram are 1200 x 768 and the dimension of Monitor 2 are 800 x 600, then the desktop size that needs to be configured is 2000 x 768.

Configuring Desktop Size for Client Window Management and Seamless Window Applications

In the Administration Console, go to the Protocol Engines, X tab for the SGD server. For Client Window Size, enter the dimensions in pixels of the virtual screen in the Maximum Height and Maximum Width fields.

Alternatively, use the following command:

$ tarantella config edit --array \
--xpe-cwm-maxwidth pixels --xpe-cwm-maxheight pixels

Repeat this configuration for each SGD server in the array.

Configuring Desktop Size for Kiosk Mode Applications

X applications can be displayed in kiosk mode on a multihead or dual head monitor.

The desktop size for kiosk mode applications is configured using the Span Multiple Monitors (Kiosk Mode) option in the Client Settings tab on the user's workspace, as follows:

  • When enabled, the kiosk mode display is spanned across all monitors.

  • When disabled, the kiosk mode display uses the primary monitor only. This is the default setting.

To display a kiosk mode application on a single monitor other than the primary, use the <KioskArea> entry in the <localsettings> section of the client profile, profile.xml on the client device. If the <localsettings> section is not present in the client profile, create a new section.

The <KioskArea> entry defines the monitor used by kiosk mode. The available values are as follows:

  • 0 – Uses the primary monitor only.

  • 1 – Uses the secondary monitor only.

  • n – (Multihead monitors only). Uses the nth secondary monitor only.

For example, to display the kiosk mode application on the secondary monitor only:

<KioskArea>1</KioskArea>

4.8.3.3 Setting Up the Monitors

Set up the monitors so that all the secondary monitors are to the right of the primary monitor, as shown in the previous diagram.

You have to do this because the X server cannot handle negative screen coordinates.

4.8.4 Improving the Performance of Windows Applications

When using Windows Remote Desktop Services, the performance of Windows applications might be poor. This is caused by using animation effects and other presentation settings in the Windows session. Performance is affected because these features require more screen updates and can greatly increase the bandwidth used. The problem is more severe on slower connections.

The causes of these problems can include the following:

  • Animated mouse cursors

  • Mouse cursor shadows

  • Screensavers

  • Animated icons in the notification area

  • Animated images in programs

  • Animated wallpaper

  • Images used as wallpaper

  • Font smoothing

By default, the SGD Remote Desktop Client, ttatsc, enables all of these features except for font smoothing.

You can turn off presentation features by configuring one or more attributes for the Windows application object. The attributes you can configure are listed in the following table.

Attribute

Description

Cursor Settings

Disables mouse pointer schemes and customizations.

Cursor Shadow

Disables the shadow on the mouse pointer.

Desktop Wallpaper

Disables the desktop wallpaper. Disabling the wallpaper can reduce the amount of data that is updated when users move items around the desktop.

Font Smoothing

Enables font smoothing for text in the application.

Full Window Drag

Disables the option to show the contents of a window while it is moved.

Menu Animations

Disables transition effects for menus and tooltips.

Theming

Disables desktop themes.

See also Section 4.1.9, “The SGD Remote Desktop Client”.

4.8.5 Improving the Performance of Java Desktop System Desktop Sessions or Applications

This section includes some tips on how to get the best user experience when using SGD with Java Desktop System.

You can improve performance of Java Desktop System desktop sessions and applications in the following ways:

  • Configure the X application object for Java Desktop System

  • Disable some default Java Desktop System settings

4.8.5.1 Configuring the X Application Object for Java Desktop System

For a Java Desktop System desktop session or application, ensure that you specify the correct command path for the X application object. Set the Application Command (--app) attribute to /usr/dt/config/Xsession.jds. Using a path of /usr/bin/gnome-session results in some Java Desktop System configuration parameters being lost and gives a poorer user experience.

To improve the display of animated effects, you can configure performance settings for the X application object. See Section 4.9.12, “An Application's Animation Appears 'Jumpy'”.

4.8.5.2 Disabling Default Java Desktop System Settings

The performance of Java Desktop System desktop sessions and applications can be affected by animation effects and other default desktop settings. Performance is affected because these features require more screen updates and can greatly increase the bandwidth used. The problem is more severe on slower connections.

Performance can often be improved by turning off, or modifying, some of the following Java Desktop System desktop features:

  • Anti-aliased fonts

  • Large fonts

  • Login screen, splash screen, About screen, and Logout screen

  • Animations

  • Desktop applets

  • Showing window contents when dragging

  • Desktop wallpaper

  • Themes

4.8.6 Documents and Web Applications

A document object can refer to any URL. This can be any document on the web, including OpenOffice documents, or Adobe Acrobat PDF files. A document can also refer to a web application.

As it is the user's client device that actually fetches the URL, firewalls, or other security measures can prevent a user from accessing a document.

You can use SGD to access web applications. A web application is simply a web page, or any URL, that requires the user to supply a user name and password for access. To give users access to a web application, you create a document object that links to the URL of the web application.

Unlike passwords for application servers, SGD cannot cache the user names and passwords for accessing web applications. However, you can configure web authentication, so that users can access SGD from a web application without having to log in again. See Section 2.6.4, “Web Authentication” for details. Alternatively, you can authenticate SGD users to the web application.

When accessing web applications, use a secure (HTTPS) web server, so that all communication is encrypted using SSL before transmission.

4.8.7 Creating a Virtual Classroom

This section describes how to configure application objects for use in a virtual classroom.

You can use SGD shadowing to create a virtual classroom, where the pupils in the classroom shadow an application being demonstrated by a teacher.

To be able to do this, you have to create a teacher's application object and a classroom application object.

The teacher must start their application first, then the pupils start their classroom application to shadow the teacher. The classroom can only shadow Windows applications or X applications.

Only one person can use the teacher's application at any one time. If more than one person starts the teacher's application, the classroom shadows the application that was started last. For this reason, only give the teacher's application to one user. If you have several teachers, create separate application objects for each of them.

For the best results, configure the classroom application object as follows:

  • The classroom application must have a Color Depth of at least 16-bit.

  • The display size of the classroom application must be at least the size of the teacher's application.

  • Use a Window Type setting of Independent Window. The user experience may be poor if the application has a Window Type of Seamless Window or Client Window Management.

  • Disable the Share Resources Between Similar Sessions attribute for the application object.

When the teacher starts their application, information is stored on the SGD server about which application can be shadowed by the classroom. This information is not copied to the other members of the array. This means that if the classroom application is started on a different SGD server to the teacher's application, the classroom application fails because the information about which application can be shadowed is not available.

You can use load balancing groups to guarantee that the teacher and classroom applications are started on the same SGD server. You must set the load balancing group for the application server and the SGD server. Otherwise, only use classroom shadowing in an SGD array containing a single SGD server.

See also Section 4.9.10, “Using Shadowing to Troubleshoot a User's Problem”.

4.8.7.1 How to Create the Teacher's Application Object

  1. In the Administration Console, create a new Windows application object or X application object.

  2. Go to the Launch tab and enter one of the following in the Login Script field:

    • unixclass.exp – If the application is an X application

    • winclass.exp – If the application is a Windows application

  3. Click Save.

  4. Configure any other settings you want for the teacher's application.

  5. Click the Hosting Application Servers tab and select the application servers that can run the application.

  6. On the Assigned User Profiles tab, assign the teacher's user profile to the application.

4.8.7.2 How to Create the Classroom Application Object

  1. In the Administration Console, create a new X application object.

    Note

    The classroom application is an X application, even if the teacher's application is a Windows application.

    The General tab is displayed.

  2. Go to the Launch tab and configure the application as follows:

    1. In the Application Command field, enter /opt/tarantella/bin/bin/ttashadow.

    2. In the Arguments For Command field, enter -readonly -silent -pointer $SHADOWDISPLAY.

    3. For the Connection Method, select the telnet option.

      Select this option even if telnet is disabled for the SGD server.

    4. In the Login Script field, enter pupil.exp.

    5. In the Environment Variables field, configure the MYCLASS variable.

      The format is MYCLASS="name_of_teacher's_application". For example, MYCLASS=".../_ens/o=applications/ou=Finance/cn=XClaim".

  3. Click Save.

  4. Go to the Presentation tab.

  5. For Color Depth, select 16-bit - thousands of colors and click Save.

  6. Configure any other settings you want for the classroom application.

  7. Go to the Hosting Application Servers tab and select the application servers that can run the application.

    The ttashadow application is only available on servers where SGD is installed.

  8. Go to the Assigned User Profiles tab, assign the user profiles of all users in the class to the classroom application.

4.8.8 Configuring Common Desktop Environment Applications

The configuration required for Common Desktop Environment (CDE) applications depends on whether you want to run a desktop session or an individual application.

For CDE desktop sessions configured with a Connection Method of ssh, problems can occur when a user tries to exit from the CDE session. The CDE session might hang, making it impossible to log out normally from the system. See Section 4.8.8.3, “Using CDE and SSH”.

To avoid font problems when using CDE applications, it is best to use a font server as described in Using a Font Server.

4.8.8.1 Configuring a CDE Desktop Session

To run a CDE desktop session through SGD, create an X application object with the settings shown in the following table.

Attribute

Setting

Application Command

The full path to the Xsession application, for example, /usr/dt/bin/Xsession.

On the command line, use --app pathname.

Maintain Connection

Select the Enabled check box.

On the command line, use --keepopen true.

Session Termination

Select Login Script Exit from the list.

On the command line, use --endswhen loginscript.

Window Type

Select Kiosk from the list.

On the command line, use --displayusing kiosk.

Window Size

Select the Scale to Fit Window check box.

Use this setting only if users suspend and resume the application on displays of different sizes.

On the command line, use --scalable true.

4.8.8.2 Configuring a CDE Application

To run a CDE application directly, rather than from the CDE Front Panel, create an X application object with the settings shown in the following table.

Attribute

Setting

Application Command

The full path to the application you want to run.

On the command line, use --app pathname.

Maintain Connection

Deselect the Enabled check box.

On the command line, use --keepopen false.

Note

This is the default value for this attribute.

Session Termination

Select No Visible Windows from the list.

On the command line, use --endswhen nowindows.

Note

This is the default value for this attribute.

Window Type

Select Client Window Management from the list.

On the command line, use --displayusing clientwm.

Window Manager

Enter the following in the field:

/usr/dt/bin/dtwm -xrm "Dtwm*useFrontPanel: false" -xrm "Dtwm*ws0*backdrop*image: none"

On the command line, use --winmgr '/usr/dt/bin/dtwm -xrm "Dtwm*useFrontPanel: false" -xrm "Dtwm*ws0*backdrop*image: none"'.

Note

If you have problems running an individual CDE application, configure a CDE desktop session as shown in Section 4.8.8.1, “Configuring a CDE Desktop Session” and run the application from the CDE Front Panel.

4.8.8.3 Using CDE and SSH

For CDE desktop sessions configured with a Connection Method of ssh, problems can occur when a CDE desktop user tries to exit from the CDE session. The CDE session might hang, making a proper logout from the system impossible.

The CDE session displays a TT_ERR_NO_MATCH error message.

The workaround for this issue is as follows:

  • Log in to the CDE host as superuser (root) and enter the following commands:

    # mkdir /etc/dt
    # mkdir /etc/dt/config
    # cp /usr/dt/config/sessionetc /etc/dt/config
    # cp /usr/dt/config/sessionexit /etc/dt/config
    # cp /usr/dt/config/sys.dtprofile /etc/dt/config
    # chgrp bin /etc/dt/config
    # chmod 555 /etc/dt/config/*
    # chown bin:bin /etc/dt/config/*
    
  • Add the following lines to the /etc/dt/config/sessionetc file:

    if [ "$SSH_TTY" !="" ]
    then
    SSHPTTY=`echo $SSH_TTY | cut -c6-15`
    ps -ef | grep -v grep | grep $SSHPTTY | grep Xsession | awk '{print $3}' >
    /var/dt/tmp/$DTUSERSESSION/sshd_pid
    fi
    
  • Add the following lines to the /etc/dt/config/sessionexit file:

    if [ -f /var/dt/tmp/$DTUSERSESSION/sshd_pid ]
    then
    /bin/kill -HUP ‘/bin/cat /var/dt/tmp/$DTUSERSESSION/sshd_pid‘
    /bin/rm /var/dt/tmp/$DTUSERSESSION/sshd_pid
    fi
    
  • Add the following line to the /etc/dt/config/sys.dtprofile file:

    dtstart_session[0]="/usr/local/bin/ssh-agent /usr/dt/bin/dtsession"
    

4.8.9 Configuring VMS Applications

You can use SGD to access X applications and character applications on a VMS application server. A Connection Method (--method) of ssh or telnet can be used for the application.

To configure a VMS application, perform the following configuration steps:

  1. Configure the login script used for the application object.

    In the Administration Console, go to the Applications, Launch tab for the application object you want to configure. In the Login Script box, enter vms.exp.

    Alternatively, use the following command:

    $ tarantella object edit --name obj --login vms.exp
    
    Note

    The vms.exp login script is for legacy application objects only. Note that this login script is untested and unsupported.

  2. (Optional) Configure X11 forwarding for the application object.

    This step is only required when using the ssh Connection Method.

    Configure the Connection Method: SSH Arguments (--ssharguments) attribute for the application object.

    In the Administration Console, go to the Applications, Launch tab for the application object you want to configure. In the Connection Method: SSH Arguments box, enter -X.

    Alternatively, use the following command:

    $ tarantella object edit --name obj --ssharguments "-X"
    

4.8.10 3270 and 5250 Applications

SGD uses the third-party emulator application, TeemTalk for Unix, for 3270 and 5250 applications. See the TeemTalk for Unix User's Guides supplied with SGD for details.

The first time a user runs the 3270 or 5250 emulator, the tta3270.nv configuration file is created in the user's home directory on the SGD server.

4.8.11 Integrating SGD With Microsoft Hyper-V

SGD supports integration with Microsoft Hyper-V by using a Windows application object. See the Oracle Secure Global Desktop Platform Support and Release Notes for details of supported Hyper-V platforms.

Use the following configuration when connecting to a Hyper-V guest:

  • Create a Windows application object for use with Hyper-V.

    SGD connects to Hyper-V using RDP, so you must use a Windows application object.

  • For the Arguments field on the Launch tab, enter the following command-line arguments for the SGD Remote Desktop Client:

    -security direct -source GUID -port 2179

    where GUID is the ID of the virtual machine (VM) you are connecting to on the Hyper-V host.

    You can use Windows PowerShell to obtain the GUID of the VM. For example:

    Get-VM VM-name|Select-Object Id

    where VM-name is the name of the VM.

    See Microsoft TechNet article hh848559 for more details of the available Hyper-V cmdlets.

    See Section 4.1.9, “The SGD Remote Desktop Client” for supported command-line options for the SGD Remote Desktop Client (ttatsc).

  • (Optional) Configure the window size of the application object to match the desktop size of the VM. This ensures that the the display is not clipped.

    This configuration is not required when using enhanced session mode, as the display is resized automatically.

Using Enhanced Session Mode

For supported VMs, the enhanced session mode of Hyper-V can be used. Enhanced session mode provides redirection of local resources such as drives and printers, as described in Microsoft TechNet article dn282274.

To use enhanced session mode, append ;EnhancedMode=1 to the -source setting, as follows:

-security direct -source GUID;EnhancedMode=1 -port 2179

4.8.12 Integrating SGD With Oracle Hypervisor Hosts

SGD can be used with Oracle hypervisor hosts, such as Oracle VM and Oracle VM VirtualBox, to display applications through SGD.

This section describes how to configure SGD to integrate with Oracle hypervisor hosts.

The following topics are available in this section:

4.8.12.1 About Hypervisor Host Objects

To integrate with an Oracle VM or Oracle VM VirtualBox installation you use a type of application server object, known as a hypervisor host object. The following hypervisor host objects are available:

A hypervisor host object represents multiple application servers. Each application server corresponds to a single virtual machine (VM) running on the Oracle VM or Oracle VM VirtualBox installation.

By default, the VM used to host the application is selected automatically from the available VMs on the hypervisor host. The VM is selected using SGD application load balancing, as described in Section 7.2.3, “Application Load Balancing”.

However, you can configure VM selection filters, to ensure that SGD uses a specific VM or group of VMs. See Section 4.8.12.4, “Using Filters to Select Virtual Machines”.

4.8.12.2 Integrating with Oracle VM

Use the following steps to integrate SGD with an Oracle VM installation.

  1. Create an application object for use with Oracle VM.

    For example, a Windows desktop application object. You could create an application object specifically for Oracle VM integration, or you could adapt the Windows Desktop application.

  2. Create an application server object for the Oracle VM hypervisor host.

    1. In the Administration Console, go to the Application Servers tab.

    2. In the content area, click New.

      The Create a New Object window is displayed.

    3. In the Name field, enter the name of the application server.

      For example, ovm1.

    4. Ensure the Oracle VM Hypervisor option is selected and click Create.

      The Create a New Object window closes and the content area is updated with the new object.

  3. Configure the Oracle VM hypervisor host object.

    1. Enter the Protocol, Hostname, and Port for the Oracle VM Manager host.

      • If you are using secure connections to the host, select the HTTPS protocol option.

      • For the hostname, use the fully qualified domain name of the Oracle VM Manager host.

      • For an Oracle VM Manager host, the default port is 7002.

    2. In the Path field, enter the web services path name for the Oracle VM Manager host.

      For most Oracle VM Manager hosts, you can accept the default setting.

    3. In the Hypervisor Credentials field, click New and enter the user name and password used to authenticate to web services on the Oracle VM Manager host.

    4. (Optional) Specify selection criteria for the returned VMs.

      Enter a comma-separated list of strings in one or more of the Virtual Machine Selection Criteria fields.

      This feature is used to filter the VMs returned from the hypervisor host. See Section 4.8.12.4, “Using Filters to Select Virtual Machines”.

    5. (Optional) Specify a subnet to use for connections to VMs.

      Perform this step if your VMs have multiple network interfaces, and you want SGD to connect to a specific interface.

      Enter settings in the Address and Netmask fields. For example, 192.168.0.0/24.

  4. Assign the Oracle VM hypervisor host object to the Oracle VM application object.

    This is described in Section 3.2.1.1, “How to Assign Application Servers to Applications”.

  5. Assign the Oracle VM application object to users.

    See Section 3.2, “Publishing Applications”.

4.8.12.3 Integrating with Oracle VM VirtualBox

Use the following steps to integrate SGD with an Oracle VM VirtualBox installation.

  1. Ensure that the VirtualBox web server, vboxwebserv, is running on the Oracle VM VirtualBox host. This is required to enable SGD to access the VirtualBox web services on the host.

    See the Oracle VM VirtualBox documentation for details of how to start the VirtualBox web server.

  2. Create an application object for use with Oracle VM VirtualBox.

    For example, a Windows desktop application object. You could create an application object specifically for Oracle VM VirtualBox integration, or you could adapt the Windows Desktop application.

  3. Create an application server object for the Oracle VM VirtualBox hypervisor host.

    1. In the Administration Console, go to the Application Servers tab.

    2. In the content area, click New.

      The Create a New Object window is displayed.

    3. In the Name field, enter the name of the application server.

      For example, vbox1.

    4. Ensure the VirtualBox Hypervisor option is selected and click Create.

      The Create a New Object window closes and the content area is updated with the new object.

  4. Configure the VirtualBox hypervisor host object.

    1. Enter the Protocol, Hostname, and Port for the VirtualBox hypervisor host.

      • If you are using secure connections to the host, select the HTTPS protocol option.

      • For the hostname, use the fully qualified domain name of the host.

      • For a VirtualBox hypervisor host, the default port is 18083.

    2. In the Hypervisor Credentials field, click New and enter the user name and password used to authenticate to web services on the VirtualBox hypervisor host.

    3. (Optional) Specify selection criteria for the returned VMs.

      Enter a comma-separated list of strings in one or more of the Virtual Machine Selection Criteria fields.

      This feature is used to filter the VMs returned from the hypervisor host. See Section 4.8.12.4, “Using Filters to Select Virtual Machines”.

    4. (Optional) Specify a subnet to use for connections to VMs.

      Perform this step if your VMs have multiple network interfaces, and you want SGD to connect to a specific interface.

      Enter settings in the Address and Netmask fields. For example, 192.168.0.0/24.

  5. Assign the VirtualBox hypervisor host object to the VirtualBox application object.

    This is described in Section 3.2.1.1, “How to Assign Application Servers to Applications”.

  6. Assign the VirtualBox application object to users.

    See Section 3.2, “Publishing Applications”.

4.8.12.4 Using Filters to Select Virtual Machines

You can filter the VMs returned from a hypervisor host, by specifying matching criteria for one or more VM properties. The VM properties you can match on vary according to the type of hypervisor host object, as described in Section C.2.118, “Virtual Machine Selection Criteria”.

Enter a comma-separated list in one or more Virtual Machine Selection Criteria fields in the General tab for the hypervisor host object. Alternatively, use the Section D.45, “tarantella object new_host” command.

Examples of Virtual Machine Selection Criteria

The following command-line examples show how to specify filters for selecting VMs.

  • To select VMs with an Oracle VM tag of sales or marketing:

    --ovmtags "sales,marketing"
  • To select VMs from the Oracle VM server pool dev02:

    --ovmpools "dev02"
  • To select VMs hosted by the Oracle VM Server ovm1.example.com:

    --ovmservers "ovm1.example.com"
  • To select VMs with a VM name of sales04 or sales05:

    --vmnames "sales04,sales05"
  • To select VirtualBox VMs running on a 64-bit Oracle Linux operating system:

    --vmostypes "Oracle (64-bit)"

    Enter the OS string used by the hypervisor host.

  • To select Oracle VM Server VMs running on the Oracle Linux 7 operating system:

    --vmostypes "Oracle Linux 7"

    Enter the OS string used by the hypervisor host.

  • To select VMs in the Oracle VM VirtualBox group called projects:

    --vboxgroups "projects"
  • To select VMs in the subgroup internal of the Oracle VM VirtualBox group called projects:

    --vboxgroups "projects/internal"
  • To select Oracle Linux 6 VMs with an Oracle VM tag of sales, hosted by the Oracle VM Server ovm1.example.com:

    --vmostypes "Oracle Linux 6" --ovmtags "sales" --ovmservers "ovm1.example.com"

4.8.12.5 Troubleshooting Tips for Hypervisor Host Deployments

The following are some troubleshooting tips for configuring and using hypervisor hosts.

  • SGD uses web services running on the hypervisor host to retrieve information about the available VMs.

    • For an Oracle VM VirtualBox installation, ensure that the VirtualBox web server, vboxwebsrv, is running on the host.

    • For an Oracle VM installation, ensure that Oracle VM Manager is running.

  • SGD will only detect VMs on the hypervisor host that are in running mode. Ensure that you start the required VMs on the hypervisor host before starting the hypervisor application on the SGD workspace.

  • If VM selection criteria filters are not specified, SGD automatically selects one of the available VMs on the hypervisor host. This may cause problems if the operating system of the selected VM is incompatible with the application object. For example, if you have configured a Windows application and a Linux VM is selected. The following workarounds are available:

  • A VM might have multiple network interfaces, some of which may be on a different subnet to the SGD server and therefore not contactable by the SGD server. Because SGD attempts to connect to the first available IP address for a VM, starting of applications hosted by such a VM may sometimes fail.

    Use the Connection Address (--vmsubnet) attribute to configure a range of IP addresses that SGD can use when connecting to the hypervisor host. VM interfaces not on this subnet are then ignored by SGD.

  • Extra configuration may be required if you are using secure HTTPS connections to a hypervisor host, and the SSL certificate for the hypervisor host is signed by an unsupported CA, or by an Intermediate CA. In this case, you may need to import CA certificates into the SGD CA truststore, as described in Section 7.5.1.1, “How to Import CA Certificates or Certificate Chains into the CA Certificate Truststore”.

  • If you copy or rename a hypervisor host object, the hypervisor credentials are not copied. You must reconfigure the Hypervisor Credentials attribute for the new object.