Installing Server Roles as .NET Web applications
To install a Server Role as a .NET Web application, choose a Server Role to install and follow the instructions.
- Installing the Content Deployer (HTTP or HTTPS) as a .NET Web application
Install the Content Deployer (HTTP or HTTPS) Server Role, to enable transport over the HTTP(s) protocol. - Installing the Experience Manager Web service as a .NET Web application
As part of installing Experience Manager, install the Experience Manager Web service Server Role. Note that this Web application also contains the Content Delivery Web service Server Role. Note also that if you have a classic ASP Web site, you can skip this task. - Adding the Experience Manager Web site extension to a .NET Web site
To add Experience Manager to your existing staging Web site in IIS, install the Experience Manager Web site extension as a .NET Web application in the staging Web site. Note also that if you have a classic ASP Web site, you can skip this task. - Installing the API Server Role as a .NET Web application
Installing the API server role involves registering .NET Server Controls, configuring Profiling & Personalization, and setting up the Ambient Data Framework. The API Server Role is typically installed on the staging or live Web site, and takes care of resolving dynamic links between content items.