Enterprise Server for .NET can be hosted in Windows Azure using virtual machines running Windows Server and SQL Server, in an Infrastructure as a Service (IaaS) deployment. It can also be deployed to Windows Azure as a set of distinct worker roles with SQL Azure, which is a Platform as a Service (PaaS) deployment.
IaaS has the advantage of providing the same environment as an on-premises installation of Enterprise Server for .NET. PaaS may provide easier scalability with less overhead, since worker roles are simpler than full OS installations, and better integration with other Azure features.
In earlier versions of Enterprise Server for .NET, Micro Focus recommended the PaaS deployment approach. At this time, Micro Focus does not recommend either type of deployment over the other. Customers should determine which better fits their needs.
It is not currently possible to perform dynamic debugging in an Azure PaaS deployment. Debugging is limited to CTF tracing and event logs. The recommended practice is to deploy and debug to an on-premises Enterprise Server for .NET and debug there. Only deploy production-ready applications to Azure.
Use the Enterprise Server for .NET Azure deployment and configuration wizard in the Enterprise Server for .NET Administration console system to deploy to Windows Azure.
The success of any Enterprise Server for .NET deployment into Azure relies on an on-premises deployment having been done successfully. Having an on-premises deployment to work with also gives an on-premises test system for the deployed production system. If a system works in the on-premises test system, it is more than likely to work in Azure.
This section briefly describes the Azure worker roles in Enterprise Server for .NET.
Each of the four key components of Enterprise Server for .NET is represented as a worker role in Windows Azure.
See the Enterprise Server for .NET product documentation for details about each of these components.