EPiServer CMS 4.62
Document creation date:
Document last saved:
EPiServer CMS Enterprise Edition is a solution that, among other things, shares the same files and stores all information in the same database. This technical note describes the configuration of, and the technology behind, the Enterprise CMS Edition.
EPiServer CMS Enterprise Edition is a solution that, among other things, shares the same files and stores all information in the same database. Enterprise Edition is mainly intended for environments where several similar Web sites are set up and want to have the possibility to share information. All Web sites can be edited from the same Edit mode and it is possible to link information between the different Web sites.
You need an EPiServer CMS Enterprise license to enable the Enterprise functions. All sites for a single Enterprise license must run on a single server. With the purchase of an EPiServer CMS Enterprise license you can also request up to three load-balancing licenses. Each site running on the “master” Enterprise license can be deployed on up to three additional load-balancing servers.
Note The load-balancing licenses are only valid for sites running on a “master” Enterprise license.
To install EPiServer CMS Enterprise Edition you need to perform a few extra actions compared to the EPiServer CMS Professional installation.
You have now completed installation of the first Web site.
Follow the instructions below to set up multiple Web sites.
If you want to use a different page template for the start page of a new enterprise Web site, you must create a new template file in the root directory and create a new start page type from Admin mode. Finally you need to edit the configuration of the Web site in IIS to make sure that the new page template is the first default page in the list.
The reason for having a file with a different name is because the files are shared between all installations.
The unique site configuration information for each site will be stored in a section in web.config under Enterprise. For example, the site running under IIS instance 1 could have a section like the following:
<add key="EPnStartPage" value="3" />
<add key="EPsHostUrl" value="http://ms11.ep.se" />
<add key="EPsLocalSite" value="desktop" />
This means that all configuration information for this Web site will be read from the common appSettings section, but EPnStartPage, EPsHostUrl and EPsLocalSite will be read from the section above.
If you are running in a load-balanced scenario, you need to make sure that the load-balanced sites receive the same instance ID (the instance attribute as shown above) as the master Web site. If you are running Windows Server 2003, the easiest way to accomplish this is to use the Save Configuration to a File menu option in IIS Manager from the master site, and then create the slave site with the function New > Web Site (from file).
If you are running Windows 2000, you may need to use MetaEdit or a similar tool. MetaEdit can be downloaded from www.microsoft.com.
A feature that the Enterprise Edition has introduced is intelligent local cache updates. From a .NET viewpoint, all your enterprise Web sites are completely separate applications, running in their own appDomains. Since all sites share the same database and therefore may be affected by page updates on other sites, the system needs to be able to update page information between all the enterprise Web sites.
Prior to EPiServer CMS 4.40, you needed to configure remote web sites in EPiServer to let these Web sites update cache information between sites. This process is still needed if you need to communicate with Web sites running on another server, but for local updates, the new local cache update feature takes care of this without requiring any further configuration.
This update process is handled by EPiServer CMS Scheduler Service. The main purpose of this service is to handle jobs that are scheduled to run at a specific time without manual intervention. Now it is also used to notify sites of cache updates.
Each site will register with the scheduler service when the site starts. As part of this registration, the site will identify the database it uses by giving the scheduler service a hash value based on the database connection string. If two sites use the same database connection string, they will have the same hash value and will therefore be notified about updates to pages in that database.
If this cache update does not seem to work, the cause is most likely that the EPiServer CMS Scheduler Service is not started.
A possible misconception regarding authentication in Enterprise solutions is that logging out on one site while being logged in on other sites would log you out from those as well. This is not the case. When logging out from an Enterprise site to, for example, leave the computer, make sure to log out from any other sites as well.