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:
AppsAnywhere Analytics database
Cloudpaging database (if applicable)
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.
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
3 x Cloudpaging Admin/License servers
3 x Paging servers
3 x Parallels RAS Gateway/Publishing Servers
6 x Parallels RDSH Servers
For most Production environments 2 x Gateway/Publishing servers is enough for most customers with up to 400 concurrent sessions. More servers can be added if required
We work on the basis of a maximum of 50 connections per RDSH server, so if you believe you will be serving large numbers of concurrent you should look to increase the number of back-end RDSH servers.
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 application you will be serving.
Production Pilot Installations
2 x Cloudpaging Admin/License Windows servers
2 x Paging Windows servers
2 x Parallels RAS Gateway/Publishing Servers
2 x Parallels RDSH Servers