Overview

AppsAnywhere is an app store-style platform that gives your students and staff easy access to the software they need, on and off-campus, including BYOD.

Multiple delivery methods are supported, to define the best way to deliver individual apps to end-users, based on the device they are using and any app license restrictions.

This section of our documentation is designed to provide all the details you might need when preparing to deploy AppsAnywhere.

AppsAnywhere Cloud

AppsAnywhere Cloud utilizes Microsoft Azure and multiple Microsoft Azure components such as Azure Virtual Machines, Databases, Load Balancers, Networking and Storage.

The selection of locations from Choose the Right Azure Region for You | Microsoft Azure ensures that AppsAnywhere components are hosted in the customer’s local Azure region, are geo-redundant and split across different underlying hosts within an Azure datacenter.

All hosting is in accordance with Azure compliance documentation.

Deployment

During new customer on-boarding, the AppsAnywhere team will discuss your specific requirements and provide a tailored AppsAnywhere Deployment Guide.

A Technical Call will then be arranged to answer any questions. Support is available from a dedicated consultant throughout your initial deployment.

To avoid additional effort, please do not deploy any servers or infrastructure until after you have received your Deployment Guide and discussed it with your Technical Consultant.

Infrastructure Components

AppsAnywhere infrastructure will include servers and services as shown in Infrastructure Diagrams .

AppsAnywhere Servers

AppsAnywhere provide AppsAnywhere servers as a virtual appliance, ready to import to your chosen hypervisor.

  • End-users will connect to your AppsAnywhere Portal to access and launch applications.

  • These servers also provide the Admin Portal where your app and system administrators can configure settings and deploy applications.

Additional servers will be required if Cloudpaging and Parallels RAS are included. Please see the Server Requirements section for more details.

Server backups are not a mandatory requirement as data is held in the database.

Servers should be split across multiple datacenters.

A hybrid model of on premise and cloud hosted servers is possible.

Database

A Microsoft SQL database is required by AppsAnywhere to store configuration details for the applications and delivery methods, as well as usage records.

Please see the Database Requirements section for more details.

Networking and Load Balancing

End-users will need to be able to connect to your AppsAnywhere Portal both on and off-site, from any location.

As there are multiple AppsAnywhere Servers load balancing and fault tolerance/redundancy are required.

Please see the Connectivity Requirements, Load Balancer Configuration and SSL Certificates sections for more details.

Directory

To grant and control access to applications and resources within AppsAnywhere, the system must be connected to a directory.

Please see the Directory Requirements section for more details.

Test Machine

A domain joined machine is required for the AppsAnywhere team to test AppsAnywhere, in particular that single sign on functionality is operational. 

This can also be used as a management machine for Remote Access for AppsAnywhere Support.