EPiServer Operator's Guide - EPiServer World

More documents

Recommendations

Info

10 | EPiServer Operator's GuidemetabaseThis section modifies Internet Information Server's underlying database metabase, which is built up of properties.Four different elements can be stated under this section: add, remove, set and collection. "Add" only addsproperties if they do not already exist. "Set" that always allots the values. See the example with syntax below:The inherit attribute above defines whether settings from the parent in the directory structure should beincluded and write over any existing settings on this level. To learn more about which properties IIS saves, werecommend the MetaEdit program, which is available on Microsoft's support site, (see Microsoft KB Q232068).ConstantsThere are certain constants that are automatically translated to the correct values, depending on language andsettings.Name{RootDir}{Administrators}{IUSR}{IWAM}{Everyone}DescriptionThe application's root directory, e.g. / or /MyDirectory/.The name of the local administrator group.The name of the account used by IIS for the application, if it is run in-process.The name of the account used by IIS for the application, if it is run pooled.The name of the local group for anonymous users.DownloadThe latest version of EPiServer Configuration Tool can be downloaded from EPiServer's home page. See theLinks and References chapter.Load BalancingThis chapter is an introduction to EPiServer load balancing. For further information, refer to the white paper, "LoadBalancing and Clustering in EPiServer".FilesDirectories that editors upload files to should be on a central file server. This requires that the account that anapplication runs under has network access to this server.CacheIn order for all servers to be notified about EPiServer's cache updates, each server must recognize all the otherservers within the respective application. In web.config you configure a comma-separated list of site names underEPsCacheListeners. For further information refer to Technical Note, "Configuring the Cache in Multi-ServerScenarios".Copyright © ElektroPost Stockholm AB - www.episerver.com
Performance and Load Measurements | 11State and SessionsEPiServer does not require sessions, but different applications built on EPiServer may do. ASP.NET can eitheruse a state server or a database to save sessions. These settings are done directly in web.config for theinstallation.ASP.NETIn order for authentication and view state to work in a load-balanced environment, all the servers must have acommon machine key. This is configured in machine.config, which contains the main configuration for .NET on amachine. See Microsoft KB Q323744 for further information.Performance and Load MeasurementsEPiServer has good scalability and performance properties, but it is up to administrators and developers to beable to make full use of these. This chapter describes how you can easily check how much an EPiServerapplication stresses the system, and find any "bottlenecks", which can be fixed in due time. The first step is tosimulate workload.Simulating WorkloadWorkload is simulated, for example, by using tools provided by Microsoft. Use either Application Center Test(ACT), which is included in Microsoft Visual Studio Enterprise Edition, or the free tool Web Application Stress(WAS). See Microsoft KB Q313559 for information on download and configuration.As the results from a stress test differ greatly depending on, e.g. how you configure the test, the differenthardware, complexity in the tree and listings, and personalization, the best solution is trial and error. The aim ofthe test is mainly to get an idea of whether the installation will be able to handle the predefined requirements.It is suitable to start by only loading the first page, as this will take the majority of all the incoming requests, and itis often this page that is most complex.You can then continue and record a more complex scenario, where you simulate a typical user's interaction withthe Web site.The following chapter describes the parts that should be monitored during workload.Performance MonitorThe easiest way to see if the system is being loaded to its maximum is to monitor the CPU workload on both theWeb server and database server. The Web server's CPU will normally increase to 100% before the databaseserver, as there are several cache functions in EPiServer that reduce the amount of database requests.EPiServer has several built-in performance counters. See the table below.NameData Factory Reads/SecData Factory Listings/SecDescriptionThe amount of page data reads per second that EPiServer delivers. Acomplex template can display data from several different pages inEPiServer's structure, which is why this value can vary between differenttemplates.The amount of page data listings per second that EPiServer delivers. Acomplex template can display listings from several different pages inEPiServer's structure, which is why this value can vary between differentCopyright © ElektroPost Stockholm AB - www.episerver.com
Page 1 and 2: EPiServer Operator's GuideAbstractT
Page 3 and 4: Introduction | 3IntroductionThe doc
Page 5 and 6: ASP.NET Configuration | 5Util/style
Page 7 and 8: EPiServer Configuration | 7Note tha
Page 9: EPiServer Configuration Tool | 9Mic

EPiServer Operator's Guide - EPiServer World

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?