This topic describes how to deploy Episerver sites through Visual Studio.
You can install Episerver through XCOPY deployment by copying application files. An XCOPY-style file transfer simplifies deployment and maintenance of Episerver sites because no registry entries are created, and no shared components are registered.
The XCOPY architecture in Episerver CMS has no machine- or site-specific information stored in configuration files, so you can use a shared folder for multiple servers. When you develop in a shared environment with source control, you can keep configuration files checked-in and still create a site that you can duplicate in a multi-site deployment.
You can have one single IIS application with multiple sites, or multiple IIS applications pointing to the same physical directory. The machine to which you install additional sites does not need to have Episerver installed.
The following procedure shows how to deploy an Episerver site from development to production. You can automate this using MSDeploy or other tools.
You need three artifacts to bring over to the production server:
Site (the Episerver platform and templates with dependencies and modules). These are normally the root of a Visual Studio project.
SQL Server database (stored content and so on).
Application Data (media BLOBs, search index, geolocation database). These are files normally stored in App_Data for a Visual Studio project. (Versions prior to CMS 7.6 store these files by default in parallel with the Visual Studio project.)
Note: The following steps assume you have an existing site and good knowledge of using Visual Studio, Internet Information Services Manager and SQL Server Management Studio.
Create the deployment artifacts on the development machine to publish a package that can be installed on the target server.
Open a Visual Studio project for the site you are deploying.
Establish NuGet dependencies for the Episerver products used. (This is done by default for CMS 7.6 and later.)
Include all files in modules, modulesbin and App_Data folders in the project. (You also can copy those folders manually to the output folder.)
If Episerver Search is installed, include the IndexingService folder into the project.
Right-click the project in Visual Studio and click Publish. Specify a publish destination of type FileSystem.
Under Settings, make sure Exclude files from the App_Data folder is not checked to restore those files on the destination. (Do not select Precompile during publishing because it disables required functionality such as Virtual Path Providers.)
Note: You should have moved the artifacts created in step 1 to the new server. The web server should have IIS and ASP.NET installed. You also need SQL Server Management Studio to connect to the database server. To use Episerver Search, you also need the Windows feature HTTP Activation (Roles and Features > .NET Framework 4/4.5 Features > WCF Services) installed on the web servers.
Right-click on the Security node and select New > SQL Login.
Select SQL Server Authentication.
Unselect User must change password at next login.
Under User Mapping, select the new database and make sure the user is member of the db_owner group.
On the web server, create a new folder for your site (for example c:\inetpub\Site1), copy the contents of the deployed site.
Set access rights on the App_Data folder so that the group IIS_IUSRS have Change access.
Open Internet Information Services Manager and connect to the web server.
Create a new IIS site.
Right-click the Sites node.
Select Add Website.
Select the wwwroot subfolder as the Physical path for the new site.
Update the EPiServerDB connection string in the configuration file in the site root (such as web.config or connectionStrings.config, depending on setup) with connection details to the new database (server, database, SQL login and password).
If Episerver Search is installed, update the episerver.search section to make sure the baseUri refers to the new IIS site.
Note: For production environments, you should move media BLOBs to a folder outside the application root (as described in the next section). The FileBlobProvider does not delete empty folders for deleted media if it detects BLOBs inside the site root (since CMS 7.6) because ASP.NET has a limitation where a deleted folder triggers an application restart, even though inside the designated App_Data folder.
Add load-balancing support.
To enable load-balancing, configure remote events and external storage of BLOBs (files on a file share). This example uses the default provider for events (WCF over UDP) and the default provider for storage of BLOBs.
Move the Blob subfolder of the App_Data folder to a shared server, such as the database server, and then share the folder. Give access rights for both the share and the folder to the user running the Application Pool for the site in Windows.
Edit EPiServerFramework.config and add configuration for the file BLOB providers. Make sure the path-attribute is valid:
Clear the browser cache and test the setup by browsing the site. Images on the site should work as before but now are delivered from the shared location.
Enable the default provider for remote events by configuring the endpoints RemoteEventServiceClientEndPoint and RemoteEventServiceEndPoint in web.config. This automatically enables the default provider.
If Episerver Search is installed, you cannot load-balanced the search index. You must store it on a master server. Change the service to allow remote callers by setting an access key under the clients list in the episerver.search.indexingservice section in web.config:
The site is ready to be load-balanced. Copy the site folder to a second server and create a new site in IIS with the same settings as the previous server. No configuration changes required.
Test remote events by logging in to one of the servers and publish change to a page. The published changes appear on the other server. Use the search functionality from both servers to verify it was configured correctly.
NOTE: The core parts of Episerver CMS do not use Session State but some functionality does, such as some of the Visitor Groups criteria. There are two approaches to enabling session state that depend on the sticky session feature (also known as session affinity) provided by a load-balancer that makes sure a user is reaching the same server combined with the default in-memory session state provider. You also can use an optimized provider for load-balancing, such as the built-in StateServer.
Do you find this information helpful? Please log in to provide feedback.