Introduction

AppsAnywhere is intended to be the primary method of deploying applications and resources to end-users, so every installation is built with redundancy and failover.

During the implementation phase, an Implementation Consultant will advise if more servers are required.

All installations require a minimum of:

Further information can be found on the linked articles above and Database Requirements.

AppsAnywhere always recommend that all the servers provisioned for the server license count are switched on at all times.

If it is decided that not all the servers are to be switched on (e.g. when hosting in the Cloud), customers should monitor the number of users logging into AppsAnywhere via Analytics and determine the thresholds for switching on or adding more servers.

Server numbers

Production Installations

When deploying a production system, an N+1 model is used, meaning a minimum of three end user facing services.

As Analytics is a reporting system, is not end user facing and all data is stored in the SQL database, redundancy is not required

AppsAnywhere

Cloudpaging

  • 3 x Cloudpaging Admin/License servers

  • 3 x Paging servers

Parallels RAS

  • 2 x Parallels RAS Gateway/Publishing Servers

  • 6 x Parallels RDSH Servers

This is sufficient as a starting point for most Production environments  for  up to 300 concurrent sessions, with a maximum of 50 connections per RDSH server. The Hardware requirements are divided by the expected number of concurrent users and the resources required per the applications in each Remote Desktop session.

As with any VDI based environment, the number of users and the performance will vary greatly depending on the server resources and the types of applications being delivered.

Production Pilot Installations

AppsAnywhere

Cloudpaging

  • 2 x Cloudpaging Admin/License Windows servers

  • 2 x Paging Windows servers

Parallels RAS

  • 2 x Parallels RAS Gateway/Publishing Servers

  • 2 x Parallels RDSH Servers