The best thing about AppsAnywhere is it lets you define more than one available delivery method for each application, giving you the ability to deliver your applications to a wealth of different devices. In this section, we'll take a look at how delivery methods are managed.
While an "application" is a high-level, abstract concept in AppsAnywhere, delivery methods are more the nitty-gritty, they define exactly how a user can get access to an applications. As there are numerous different ways you can actually get an application to a user, there are numerous different types of delivery method available. You can add as many delivery methods as you want to a single application and which delivery method gets offered to the user is entirely at your discretion and usually depends on the type of device they are connecting with.
Types of Delivery Methods
There are a number of different types of delivery methods, each suited to a particular type of environment or device. These are:
Delivery Method Name
Directs a user to an external website. This is mainly used as a fall-back method for when other options are unavailable and you may want to just point the user at the vendor's website to locate their own options, though It is also useful for pointing users of mobile devices to apps available in the relevant app stores.
Initiates a file download in the user's browser of a file hosted somewhere outside of the AppsAnywhere environment, such as on your own website, content delivery network, or a direct link to an installer or executable hosted on the vendor website.
Initiates a file download in the user's browser of a file that exists locally on the AppsAnywhere server. Such files are provided through the AppsAnywhere portal and are only accessible to users who are authenticated and permitted to access the download. This is great for restricted content or files that you do not wish to make publicly available.
Executes a given command on the user's Windows device. This is useful for initiating the local installation of an application from an installer, or executable file that is located local to the user's device.
Initiates the launch of a Cloudpaging application using the AppsAnywhere client. An external protocol request is sent to the AppsAnywhere client which then requests a Cloudpaging token from AppsAnywhere which is subsequently passed to the Cloudpaging Player which handles the application launch from that point on.
Initiates the launch of a Cloudpaging application in the configured RemoteApp environment and presents it to the end user as a remote session. This enables users to use Windows applications in environments that wouldn't usually be capable of running the application natively, such as under-spec'd machines or devices running OSX or Andriod.
Windows, Mac, Android
Locally Installed (Win)
Launches an application that is installed on the target device outside of the AppsAnywhere environment, for instance, as part of the base image. This means all applications can be launched from AppsAnywhere, regardless of whether or not AppsAnywhere is actually used to deliver them, massively improving the user experience.
Initiates the download of a DMG or PKG file from any public source and manages the deployment of the application on the target device. This is an incredibly quick and easy way of deploying native Mac applications to Mac devices.
Initiates the deployment of an application available to the logged in user in Software Center. The first time the user launches an application using this delivery method, the AppsAnywhere client negotiates with the SCCM client to initiate the delivery of that application through SCCM to the device. Once the application is installed, it is launched for the user and subsequent launches are handled instantly without the deployment being required.
Managing Delivery Methods
All available delivery methods are managed from the application management page, under the Delivery Methods tab.
There are two ways you can get to this page:
When creating a new application (See Defining an application)
When editing an application (See Editing an application)
Once here you can add, edit and delete delivery methods. You can also prioritize them, which is covered in another article (See Prioritizing delivery methods)
Adding a delivery method
As you can see above, there are a number of different types of delivery method you can add to an application and each one is configured slightly differently.
To start, select the type of delivery method you want to add from the dropdown menu near the bottom left of the screen and click the button
Take a look at the relevant page from those listed below to understand about adding each individual type of delivery method
Viewing delivery methods
Once delivery methods have been saved, you will see them in the list on the left hand side of the Delivery Methods tab.
Priority matters! Take a look at Prioritizing delivery methods to see why you should correctly prioritize your delivery methods and how to do it
Editing a delivery method
To change the details of a delivery method, just select it in the list shown above. This will re-load the form you used to create it in the right-hand pane and pre-populate all of the current data
You can then make any changes you need an re-save the form.
Deleting a delivery method
If for any reason you need to delete a delivery method, you will first need to locate and edit that delivery method as described above.
You will then see at the bottom of the form there is a Delete button. Click this to remove the delivery method from the application.
Editing or deleting a delivery method has the potential to affect users currently using the application via that delivery method. Be confident in the changes you are making before modifying delivery methods and if possible, test in advance.