Product version: |
EPiServer CMS 4.62 |
Document version: |
1.0 |
Document creation date: |
07-06-2006 |
Document last saved: |
04-10-2007 |
Installation and upgrade of EPiServer CMS is carried out with EPiServer CMS Manager. This document describes how to install, upgrade and delete an EPiServer CMS installation and is based on installation with the most recently released version of EPiServer CMS Manager.
Licensing
- MAC Address for Installation
Online Installation and Upgrade
- New EPiServer CMS Installation
- Upgrade EPiServer CMS Installation Online
Offline Installation and Upgrade
- Create Offline Installation
Installing/Upgrading Oracle Versions of EPiServer CMS
- Setting Up Oracle Server
- Setting Up Oracle Database
- Upgrading From Older Versions of EPiServer CMS
- Installation with Oracle Database Server
Deleting an EPiServer CMS Installation
Issues When Upgrading to EPiServer CMS 4.62
- Converting a Multi-Language Database
- Friendly URL
- Portal
- Delayed Loading of Strings
- Unified File System
- Simple Address
Installing ASP.NET 2.0 Templates
- Install EPiServer CMS with the Development Web Server
Installation (both online and offline) and deletion of EPiServer CMS installations is done with EPiServer CMS Manager. The EPiServer CMS software installation program can be found at http://www.episerver.com/.
This document is based on installation with the most recent version of EPiServer CMS Manager.
NOTE: Only EPiServer CMS 4 installations can be upgraded offline. Use online installation to upgrade EPiServer CMS 3 installations.
NOTE: For information on installing EPiServer CMS Enterprise Edition, refer to the technical note, "Configuring EPiServer CMS Enterprise Edition".
EPiServer CMS cannot be used without a valid license. If the EPiServer CMS installation is to be used for testing and evaluation purposes, a demo license can be created using the link in the installation program. Complete the Web form that appears. You can choose whether to bind the system to an IP address or to the MAC address of the network adapter.
If you are using dynamic allocation of IP addresses (DHCP), you might want to register EPiServer CMS to the MAC address instead of the IP address. The MAC address is a unique identifier for the network adapter and a common standard. To find the MAC address, open a command prompt in Windows and type: ipconfig /all.
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Network adapter
Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
Dhcp Enabled. . . . . . . . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
The MAC address is found under Physical Address and is entered when generating the license.
EPiServer CMS is installed using EPiServer CMS Manager. Follow the instructions below to install a new EPiServer CMS installation when your computer has access to Internet.
NOTE: See the "Installing/Upgrading Oracle Versions of EPiServer CMS" chapter for information on how to install Oracle versions of EPiServer CMS.
When the installation procedure is complete, a folder has been created under "Program Files\EPiServer4" named Download. This folder contains files that have been downloaded to allow the tool to be installed. It also contains a text file, upgrade.log, which describes the installation procedure. This file can be sent to Support if an error that you require help with has occurred during the installation or upgrade procedure.
IMPORTANT! If there were no problems during the installation procedure, delete the file "Program Files\EPiServer4\Upgrade.log" from the computer for security reasons. This file contains sensitive information, such as information for connecting to the database.
Follow the instructions below to upgrade an EPiServer CMS installation when your computer has access to Internet.
NOTE: See the "Installing/Upgrading Oracle Versions of EPiServer CMS" chapter for information on how to upgrade Oracle versions of EPiServer CMS.
EPiServer CMS Manager enables offline installation, which means that EPiServer can be installed on machines that are located behind a firewall and do not, therefore, have access to Internet. Offline installation also allows installation on laptop computers that are not connected to Internet.
In order to install and upgrade EPiServer CMS offline, you must first use EPiServer CMS Manager to create a .zip file containing the appropriate files. This step is described in the "Create Offline Installation" chapter.
NOTE: Only EPiServer CMS 4 installations can be upgraded offline. Use online installation to upgrade EPiServer CMS 3 installations.
NOTE: See the "Installing/Upgrading Oracle Versions of EPiServer CMS" chapter for information on how to install and upgrade Oracle versions of EPiServer CMS.
Follow the instructions below to create the .zip file that contains the files used to install and upgrade EPiServer CMS offline.
NOTE: Remember where the .zip file is saved. You cannot install or upgrade an EPiServer CMS installation offline without it.
Installing EPiServer CMS OfflineFollow the instructions below to install a new EPiServer CMS installation when your computer does not have access to Internet.
When the installation procedure is complete, a folder has been created under "Program Files\EPiServer4" named Download. This folder contains files that have been downloaded to allow the tool to be installed. It also contains a text file, upgrade.log, which describes the installation procedure. This file can be sent to Support if an error that you require help with has occurred during the installation or upgrade procedure.
IMPORTANT! If there were no problems during the installation procedure, delete the file "Program Files\EPiServer4\Upgrade.log" from the computer for security reasons. This file contains sensitive information, such as information for connecting to the database.
Follow the instructions below to upgrade an EPiServer CMS installation when your computer does not have access to Internet.
NOTE: Only EPiServer CMS 4 installations can be upgraded offline. Use online installation to upgrade EPiServer CMS 3 installations.
The Oracle version of EPiServer CMS requires a few extra files and a special license file. You can request these from EPiServer Developer Support since these files are not included in the standard installation.
Follow the instructions below to set up the Oracle database.
The files distributed with the Oracle version contain an Upgrade folder. This folder contains several files to upgrade specific versions of the EPiServer CMS database. Check the version number of your current EPiServer CMS installation (see the title bar of Internet Explorer when in Admin or Edit mode) and run the files consecutively to upgrade the database step-by-step to the most current version.
Finally you should run the oracle_proc.sql script to update all procedures and functions.
Note For offline installations, EPiServer CMS Manager must also exist on the machine where EPiServer CMS will be installed.
Follow the instructions below to install EPiServer CMS with Oracle Database Server.
<add key="EPsConnection" value="Data Source=dbserver.company.com;User Id=EPISERVER;Password=PASSWORD;" />
<add key="EPsDatabaseClient" value="Oracle" />
Follow the instructions below to delete an EPiServer CMS installation.
The following issues apply when upgrading EPiServer CMS sites before EPiServer CMS 4.60 to 4.62. These issues do not apply when upgrading from EPiServer CMS 4.60 or 4.61 to 4.62.
Please contact EPiServer Developer Support for further information on converting an existing multi-language database.
When upgrading a Web site to EPiServer 4.62, the friendly URL functionality will not function correctly until the following has been added to web.config.
<httpModules>
<add name="FriendlyUrl" type="EPiServer.Util.FriendlyUrlModule, EPiServer" />
</httpModules>
Add the following code to the header section of all the templates used in the site, normally located in /templates/units/header.ascx.
<%@ Register TagPrefix="EPiServer" Namespace="EPiServer.WebControls" Assembly="EPiServer" %>
...
<episerver:FriendlyUrlRegistration runat="Server" />
ASP.NET Development Server
The built-in Web server in .NET 2.0 (ASP.NET development server) does not support friendly URL in the default configuration. In order for this to work, you must have an extension that is mapped to ASP.NET for the URL. For example:
<add key="EPsFriendlyUrlExtension" value=".aspx" />
In order to register the EPiServerPersonalizationProvider you need to add the following sections to web.config. This will also give WebAdmins, WebEditors and Administrators permissions to enter shared personalization scope.
<connectionStrings>
<add name="EPiServerDB" connectionString="Data Source=SERVERNAME;Database=DATABASE;User Id=USER;Password=PWD;Network Library=DBMSSOCN;" providerName="System.Data.SqlClient" />
</connectionStrings>
…
<system.web>
…
<webParts>
<personalization defaultProvider="EPiServerPersonalizationProvider">
<providers>
<add name="EPiServerPersonalizationProvider" type="EPiServer.WebParts.Core.EPiServerPersonalizationProvider" connectionStringName="LocalSqlServer" />
</providers>
<authorization>
<allow verbs="enterSharedScope" roles="WebAdmins, WebEditors, Administrators" />
</authorization>
</personalization>
</webParts>
…
</system.web>
The web.config additions above define a connection string that preferably points to the EPiServer CMS database. In order to use your EPiServer database for WebPart personalization you need to update its scheme. Use the following command (available under \%windir% \Microsoft.NET\Framework\v2.0.50727) to update the database scheme.
aspnet_regsql.exe /S SERVER /d DATABASE -E -A mc
Sample templates can be imported from the <EPiServerSample dir>\Util\Setup\Portal Templates.ep4.
The delayed loading function is not activated by default, i.e. the previous behavior of loading all strings is still active. To activate delayed loading, add the following text to web.config:
<!--
The number of characters when delayed loading should be activated for large
strings in properties deriving from Long String.
A lower value will decrease memory usage but may increase database usage, the
optimial value depends on the amount of content.
Setting this value to 0 will disable delayed loading of strings.
Setting this value to 1 will effectively always use delayed loading.
-->
<add key="EPnStringDelayedLoadThreshold" value="100" />
For further information about the delayed loading functionality, see the EPiServer CMS 4.60 Release Notes.
From EPiServer CMS 4.60, the following registration in web.config is required for virtual unified file system handlers, i.e. those handled by EPiServer CMS. Registration is done automatically at installation and upgrade. This module is responsible, for example, for making sure that "Documents/MyDocument.doc" is mapped to a file in versioned file system. It should be placed after SpiderSupport, which was previously reponsible for this functionality.
<httpModules>
<add name="SpiderSupport" type="EPiServer.Util.SpiderSupport, EPiServer" />
<add name="UnifiedFileSystem" type="EPiServer.FileSystem.UnifiedFileSystemModule, EPiServer" />
From EPiServer CMS 4.60, the simple address functionality is managed by a separate module and is no longer part of SpiderSupport. In order for simple address to function as in EPiServer CMS versions prior to 4.60, add the following registration to web.config. Registration is done automatically at installation and upgrade.
<httpModules>
<add name="SpiderSupport" type="EPiServer.Util.SpiderSupport, EPiServer" />
<add name="UnifiedFileSystem" type="EPiServer.FileSystem.UnifiedFileSystemModule, EPiServer" />
<add name="ExternalUrl" type="EPiServer.Util.ExternalUrlModule, EPiServer" />
Installing ASP.NET 2.0 Templates
Visual Studio 2005, and Visual Studio 2005 Web Application Projects are required to install the templates for ASP.NET 2.0. The Web Application Project can be downloaded from the following site:
http://msdn.microsoft.com/asp.net/reference/infrastructure/wap/default.aspx.
In order for the EPiServer CMS Manager to handle projects compiled in ASP.NET 2.0, version 1.2 must to be installed.
<pages validateRequest="false" enableEventValidation="false">
<controls>
<add tagPrefix="EPiServer" namespace="EPiServer.WebControls" assembly="EPiServer" />
<add tagPrefix="WebParts" namespace="EPiServer.WebParts.WebControls" assembly="EPiServer.WebParts" />
<add tagPrefix="WebParts" namespace="EPiServer.WebParts.WebControls.Wsrp" assembly="EPiServer.WebParts" />
</controls>
</pages>
Follow the instructions below to install EPiServer CMS with the Development Web Server shipped with Visual Studio 2005.