The Parallels RAS connector adds several new delivery methods to AppsAnywhere. In this section we will take a look at each one, how to set them up and how they can be used.

In this article

Also in this section

There are no sub-sections to this page


 

Overview

The power of providing access to your Parallels resources through AppsAnywhere comes when you combine delivery methods to create a delivery strategy that works best for the user in each of the environments they may be using. To create the best strategy, it's important to understand what tools you have at your disposal and how they relate to the user experience. There are six delivery methods in total made available by the Parallels connector, each of which will be described in detail below. 

Resource Types

There are three main types of resource that you can delivery from a Parallels RAS environment through AppsAnywhere:

  1. Apps that are physically installed on the session hosts and published natively through RAS
  2. Apps that are Cloudpaged to the session hosts on-demand using the AppsAnywhere Client
  3. Virtual Desktops made available through Parallels

Client Possibilities

For each of the three resource types described above, there are two options for how you want that resource to be delivered:

  1. The Parallels Client is available to install on Windows, Mac, iOS, Android and Linux and offers the user an immersive experience when using the resource that is being provided to them. This includes clipboard integration, the ability to connect locally attached devices, link file systems and a whole host of other benefits for the user. This is generally the preferred method for interacting with resources when it is available.
  2. The HTML5 client is a great option to use when either the native client us not available, it's not desiarble to install it on that particular device, or you want to provide the resource in a more locked-down manner. In this instance, the resource runs in any modern browser instead of the user needing to install the client software on their device. 

Useful Tip

Deciding which of these options to use is very much down to personal choice and your specific use cases. With AppsAnywhere you are not limited to choosing one or the other though. There's nothing to stop you defining one of each delivery method and applying them to different types of environments using restrictions and prioritization.

Application Delivery Methods

There are four different delivery methods that you can add to your application that utilize the Parallels RAS integration. You will see these when Adding delivery methods to an app if you select the Parallels category from the left-hand side of the Add New Delivery Method dialog.

Each of the available delivery methods is described in detail in this section.

 

Parallels: Native

The Parallels: Native delivery method triggers the standard (installed) Parallels Client on the user's device to launch a resource that is natively installed on the remote session host(s) (i.e. not Cloudpaged to it).  

The following table describes each field and setting available when creating this type of delivery method, it's intended value and an example for each. 

Field NameDescriptionIntended ValueExample
Display Name A common field across all delivery methods, allowing you to assign a friendly name to the delivery method for your own referenceA name of your choosing to help you identify this delivery method in futureMozilla Firefox
Parallels Environment The environment from which the app will be delivered, as defined in the Manage Parallels Environments sectionThe name of the parallels environment the resource is hosted in, selected from the list of options Production RAS
Resource ID The ID that has been assigned to the published resource in Parallels. This is available through the RAS admin console (see note below)The ID taken from the RAS admin console (see right) 1
ArgumentsAny command line arguments that you want to be supplied to the application when it is runAll required command line arguments written exactly as you would pass them to the app if running it directly"https://www.google.com" 

Useful Tip

The ID of a resource in Parallels can be found in the Parallels RAS Console. Click on Publishing, choose the resource you want to deploy under Published Resources and you will see the resource ID next to Application (between the hashtag and the colon)

Above: The Parallels: Native delivery method details form

Below: The Parallels Resource ID, as seen in the RAS admin console.

Parallels: Cloudpaged

The Parallels: Cloudpaged delivery method triggers the standard (installed) Parallels Client on the user's device to initiate a Parallels session that then triggers the AppsAnywhere Client within that session to launch a Cloudpaged app on the remote session host. If the app has not been launched on that session host before then it will be delivered to it when the user initiates the session. 

This process can be a little bit confusing as the AppsAnywhere Client is involved twice, both on the user's device and on the remote server, so lets break it down:

  1. User clicks launch in the browser and a message is sent to the AppsAnywhere Client running on the user's device
  2. The AppsAnywhere Client on the user's device first of all makes sure that the Parallels Client is installed and then initiates an application session
  3. Once the session is initiated, a messaged is passed from the AppsAnywhere Client on the user's device to the AppsAnywhere Client running on the remote session host with details about which Cloudpaged app needs to be launched
  4. The AppsAnywhere Client on the remote session host Cloudpages the app onto that server and then presents it to the user through the session. 

You will need two things in place before you can create this kind of delivery method:

  1. You will need to have published the AppsAnywhereLauncher as a published resource in your Parallels environment
  2. You will need to have already created a Cloudpaging delivery method for this app which links in the package you want to deliver onto the server

The following table describes each field and setting available when creating this type of delivery method, it's intended value and an example for each. 

Field NameDescriptionIntended ValueExample
Display Name A common field across all delivery methods, allowing you to assign a friendly name to the delivery method for your own referenceA name of your choosing to help you identify this delivery method in futureVLC
Parallels Environment The environment from which the app will be delivered, as defined in the Manage Parallels Environments sectionThe name of the parallels environment the resource is hosted in, selected from the list of options Production RAS
Resource ID The ID that has been assigned to the AppsAnywhereLauncher published resource in Parallels. (see note below)The ID taken from the RAS admin console 2
Cloudpaging Delivery MethodThe Cloudpaging delivery method that AppsAnywhere should use to deliver the app into the remote sessionSelect one of the Cloudpaging delivery methods that is currently defined for the appVLC [License ID]

Useful Tip

The ID of a resource in Parallels can be found in the Parallels RAS Console. Click on Publishing, choose the AppsAnywhereLauncher resource under Published Resources and you will see the resource ID next to Application (between the hashtag and the colon)

Above: The Parallels: Cloudpaged delivery method details form

Parallels HTML5: Native

The Parallels HTML5: Native delivery method opens up a new tab in the user's browser with the Parallels HTML5 Client and launches a resource that is natively installed on the remote session host(s) (i.e. not Cloudpaged to it) for the user to use from within the browser.  

The following table describes each field and setting available when creating this type of delivery method, it's intended value and an example for each. 

Field NameDescriptionIntended ValueExample
Display Name A common field across all delivery methods, allowing you to assign a friendly name to the delivery method for your own referenceA name of your choosing to help you identify this delivery method in futureMozilla Firefox
Parallels Environment The environment from which the app will be delivered, as defined in the Manage Parallels Environments sectionThe name of the parallels environment the resource is hosted in, selected from the list of options Production RAS
Resource ID The ID that has been assigned to the published resource in Parallels. This is available through the RAS admin console (see note below)The ID taken from the RAS admin console (see right) 1
ArgumentsAny command line arguments that you want to be supplied to the application when it is runAll required command line arguments written exactly as you would pass them to the app if running it directly"https://www.google.com

Parallels HTML5: Cloudpaged

The Parallels HTML5: Cloudpaged delivery method opens up a new tab in the user's browser with the Parallels HTML5 Client and triggers the AppsAnywhere Client within that session to launch a Cloudpaged app on the remote session host for the user to use from within the browser. If the app has not been launched on that session host before then it will be delivered to it when the user initiates the session. 

You will need two things in place before you can create this kind of delivery method:

  1. You will need to have published the AppsAnywhereLauncher as a published resource in your Parallels environment
  2. You will need to have already created a Cloudpaging delivery method for this app which links in the package you want to deliver onto the server

The following table describes each field and setting available when creating this type of delivery method, it's intended value and an example for each. 

Field NameDescriptionIntended ValueExample
Display Name A common field across all delivery methods, allowing you to assign a friendly name to the delivery method for your own referenceA name of your choosing to help you identify this delivery method in futureVLC
Parallels Environment The environment from which the app will be delivered, as defined in the Manage Parallels Environments sectionThe name of the parallels environment the resource is hosted in, selected from the list of options Production RAS
Resource ID The ID that has been assigned to the AppsAnywhereLauncher published resource in Parallels. (see note below)The ID taken from the RAS admin console 2
Cloudpaging Delivery MethodThe Cloudpaging delivery method that AppsAnywhere should use to deliver the app into the remote sessionSelect one of the Cloudpaging delivery methods that is currently defined for the appVLC [License ID]

Something To Note

The setup for the Native and Cloudpaged delivery methods is practically the same for both the standard and the HTML5 client, the only difference is the way in which it is delivered to the user.

Dektop Delivery Methods

In addition to the application delivery methods, there are two delivery methods that you can add to a desktop delivery that utilize the Parallels RAS integration; which offer access to a full desktop to the user using either the installed or the HTML5 client. You will see these when adding delivery methods to a desktop if you select the Parallels category from the left-hand side of the Add New Delivery Method dialog.

Both of the available delivery methods are described in detail in this section, althought they are exactly the same in terms of configuration, the only difference between them being the way in which they are delivered to the user.

Parallels: Desktop

The Parallels: Desktop delivery method triggers the standard (installed) Parallels Client on the user's device to launch a remote desktop that is provided through Parallels.  

The following table describes each field and setting available when creating this type of delivery method, it's intended value and an example for each. 

Field NameDescriptionIntended ValueExample
Display Name A common field across all delivery methods, allowing you to assign a friendly name to the delivery method for your own referenceA name of your choosing to help you identify this delivery method in futureStaff Desktop
Parallels Environment The environment from which the desktop will be delivered, as defined in the Manage Parallels Environments sectionThe name of the parallels environment the resource is hosted in, selected from the list of options Production RAS
Resource ID The ID that has been assigned to the published resource in Parallels. This is available through the RAS admin consoleThe ID taken from the RAS admin console 5

Parallels HTML5: Desktop

The Parallels HTML5: Desktop delivery method opens up a new tab in the user's browser with the Parallels HTML5 Client and loads up a desktop session for the user to use from within the browser. 

The following table describes each field and setting available when creating this type of delivery method, it's intended value and an example for each. 

Field NameDescriptionIntended ValueExample
Display Name A common field across all delivery methods, allowing you to assign a friendly name to the delivery method for your own referenceA name of your choosing to help you identify this delivery method in futureStaff Desktop
Parallels Environment The environment from which the desktop will be delivered, as defined in the Manage Parallels Environments sectionThe name of the parallels environment the resource is hosted in, selected from the list of options Production RAS
Resource ID The ID that has been assigned to the published resource in Parallels. This is available through the RAS admin consoleThe ID taken from the RAS admin console 5

 


 

Some other articles you might find useful:

 

Written By: