The AppDNA server, desktop client, and database install on the same machine. For a small proof-of-concept deployment, that is all you need.
For a production deployment involving multiple users, you must also install the AppDNA desktop client on user desktops.
AppDNA uses Microsoft SQL Server to store and manipulate the application and OS image DNA. As the size of the portfolio of applications grows, so do the demands on SQL Server. Consider the SQL Server architecture that will handle your data. The following diagram shows how various architectures for the SQL Server correspond to AppDNA performance.
For more information about optimizing SQL, refer to Optimize SQL Server.
You can optionally install the AppDNA database on a dedicated SQL Server machine instead of on the machine with the AppDNA server. If the SQL Server machine is outside of your local network, ensure that there is excellent connectivity between the machines so that the communication between them does not impact AppDNA performance.
For non-evaluation versions only, you can install AppDNA on a virtual machine. However, if you plan to use Install Capture with VMware Workstation, be aware that VMware Workstation requires AppDNA to be installed on the virtual machine’s host machine. This is not possible when AppDNA is itself installed on a virtual machine. If you must install AppDNA on a virtual machine, you can work around this limitation by using the AppDNA Self-Provisioning feature for Install Capture tasks.
If you plan to use Install Capture with a virtualization technology that provides full remote control (such as Citrix XenServer, VMware vSphere, and Microsoft Hyper-V), you can install AppDNA on a virtual machine.