Purpose

This document describes how to set up a standard EPiServer installation so that it can be used in a demo environment.

Table of Contents

Introduction

    - Installing EPiServer

    - Enabling Globalization Support

    - Install EPiFields

    - Set Permissions for Functions

    - Set Up the Unified File System

    - EPiServer Version Control

    - Activate Microsoft Office Add-In

    - Set Up the Statistics Server

    - Portal Framework

    - Mirroring

    - Subscriptions

Testing the Demo Environment

    - Globalization

    - EPiFields

    - Outgoing E-Mail

    - Statistics

    - Version Control

    - Client Tools

    - WSRP – Consuming Portlets

    - Mirroring

Referenced Documentation

Appendix

    - template.xsl

Quick Guide

The following steps must be carried out to set up a demo site. If you have previously installed a demo site, you may know how to set up each step and need a quick overview of which steps should be done.

1. Install EPiServer
2. Set up globalization support
3. Install EPiFields
4. Set permissions for functions
5. Set up the Unified File System (default setting allows upload, searching and version control)
6. Set up version control
7. Activate Microsoft Office add-in
8. Set up the statistics server
9. Set up consumption of WSRP portlets
10. Set up mirroring
11. Set up subscriptions

Setting Up the Demo Environment

Generate a License Key

EPiServer cannot be used without a valid license. If the EPiServer installation is to be used for testing and evaluation purposes, a demo license can be created using the link in the License key window in the installation wizard. 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.

Install an SQL Database Server

Install an SQL Database Server during installation according to the instructions below.

1. In the Databse setup/Creation window of the installation wizard, select a server that the database you intend using is installed on. If the database is local, i.e. on the same machine you intend installing EPiServer, select (local).
2. Select the name of the database you intend using from the Existing Database list or enter the name of a new database.

Note The database must be installed and configured before you start installing EPiServer. Make sure that the specified user has owner rights to the database. Database installation instructions can be found in the Readme file supplied with the installation program.


3. In the User area, select an existing user or create a new user that has owner rights to the database specified above. In the Password box, type the password associated with the specified user.
4. Select the Do not install database check box if you do not wish to install a database for the EPiServer site. Click Next

Setting Up Oracle Server

Setting Up Oracle Database

Follow the instructions below to set up the Oracle database.

1. Log on to the Oracle database server with SQL*Plus, as the SYSTEM user.
2. Create tablespace for the EPiServer database.
   The following names and paths are just examples, adjust as suitable for your environment. The size specifications may need to be adjusted, but should be enough for a medium-sized Web site.

CREATE TABLESPACE EPISERVER_DATA1
LOGGING DATAFILE '/oracle/oradata/epdev/EP_DATA1.ora'
SIZE 50M
EXTENT MANAGEMENT LOCAL;


3. Create a user and give the user basic rights.

CREATE USER EPISERVER IDENTIFIED BY PASSWORD
DEFAULT TABLESPACE EPISERVER_DATA1
TEMPORARY TABLESPACE TEMP;

GRANT CONNECT, RESOURCE TO EPISERVER;


4. Logout from SQL*Plus.
5. Load the database schema.
   This assumes that the database host string is dbserver.company.com and user is defined as above. The SQL files referred to below are provided by support@ep.se .

sqlplus EPISERVER/PASSWORD@dbserver.company.com @EPiServerNET.sql > out.log

6. Verify that the out.log file does not indicate any errors.

Upgrading From Older Versions of EPiServer

Installation with Oracle Database Server

Enabling Globalization Support

1. If globalization is not currently enabled for the Web site, go to System Settings under Admin mode and select the Enable globalization check box.
2. Go to Manage Web Site Languages and change the name of the default language by clicking Default in the Name column and changing the name. Assign an optional icon that will appear in the drop-down lists. Assign a default langauge at the top of the page.
3. Add and enable any other languages that you want to have available on the Web site by following the instructions in the next chapter.
4. Set the "available languages" for the site by selecting a branch in the tree structure in Edit mode and selecting "Language Settings", as described in step 3 below.

Adding New Languages to a Globalized Web Site

Follow the instructions below to add new languages to a globalized Web site.

1. Click Edit Language Codes in Admin mode and add the new language that you want to make available. Click Manage Web Site Languages in Admin mode and add the new language as a Web site language. Make sure that the Enabled check box is selected.
2. Go to Edit mode. The drop-down list under the tree structure will include your new language, but you will not be able to create pages in your new language until you have assigned the new language as an "available language".
3. Select the tree branch that you want to be available in your new language, for example if you want the new language to be available for the entire Web site, select the start page. Right-click and select Language Settings, or click the Language Settings icon in the toolbar. In the Available languages area, click Change. Select the check box for your new language and click Save. It will now be possible to create a new version of pages in your new language.

Install EPiFields

How to Add EPiFields Support to Non-EPiFields Page Types

Set Permissions for Functions

Certain functions in EPIServer will not work as designed until you have set the correct access rights. Setting these access rights ensures that you have access to all functions in the Editor, detailed error messages for troubleshooting, advanced upload of files, and view and publish pages from Microsoft Office.

• In Admin mode, click Permissions for Functions from the Config tab. Click Edit for all the listed functions and add your username by clicking Add User.

Set Up the Unified File System

EPiServer Version Control

Activate Microsoft Office Add-In

Set Up the Statistics Server

Installation with EPiServer Manager

Follow the instructions below to install the Log Service with EPiServer Manager.

1. Select the Capabilities node under the Web site for which you want to generate log messages.
2. In the Logging/Statistics group box, click Enable.

Configure the Log Service to use a database

Portal Framework

Mirroring

The following instructions tell you how to setup a remote site and your demo site so that you can publish content from your demo site to the remote site.

Requirements

The following is required to be able to set up a news channel from an intranet site to an extranet site.

• Both sites must run EPiServer 4.50 or later.
• Both sites must have page types with the same name, in this case. Both page types should share at least ”MainBody” so that there is a property to display externally.

Set Up Mirroring to Publish Content to a Remote EPiServer Site

1. Install a new site and name it RemoteSite.
2. Step 2 only applies if your extranet site is using Forms authentication.
   

   Set up the new site with basic authentication. Make sure that the IIS directory security is set to Basic authentication AND that anonymous access is NOT allowed.

   Note By default the user needs to be a Windows administrator on the server that runs the extranet site.

   • Open Internet Information Services Manager on the Web server and select the /WebServices folder on your remote EPiServer Web site.
   • Right-click and select Properties. Under the Directory Security tab, click Edit.
     The authentication options must be configured for Basic Authentication only. Otherwise automatic authentication will not occur.
   • Edit the Web configuration file, web.config, in the EPiServer root directory. Make sure that the Web service account is allowed access in the WebServices folder.
     Replace DOMAIN with the name of the domain or local machine where the user account was created.
   
   
   

   <location path="WebServices">

       <system.web>

           <authorization>

               <allow users="DOMAIN\MyWebServiceUser" />

               <deny users="*" />

           </authorization>

       </system.web>

   </location>

    

   The BasicAuthentication http module will translate basic authentication requests on-the-fly to forms-authenticated cookies. Make sure that web.config has the BasicAuthentication filter defined under the httpModules section.

   <httpModules>

   <add name="BasicAuthentication" type="EPiServer.Security.BasicAuthentication, EPiServer" /> 

    

   Test the setup by opening a Web browser and entering the URL to a Web service on your Web site, for example: http://localhost/RemoteSite/WebServices/DataFactoryService.asmx. You will receive a standard Windows login pop-up window.

   Enter the WebServiceUser account information. If everything is working, you should see the Web Service definition page

3. Go to Admin mode and click the Config tab and then Remote Web Sites.
4. Edit the local site name, enter "RemoteSite" in the field and click Save.
5. Click Create. Enter the name of your demo site in the Name field. Enter “http://localhost/DemoSite” in the URL field. (Replace DemoSite with the name of your demo site.) In the Shared secret for signature field, click Create to the right of the field and verify that a key is generated in the field. Leave the username, password and domain fields and check boxes empty. Click Save.

Update web.config on the Remote Web Site with SOAP Extension Information

Add the following under the <system.web> section in web.config on the RemoteSite:

Set Up Your Demo Site as the Publishing Web Site

(Replace all the occurrences of DemoSite in the instructions below with the name of your demo site.)

1. In your demo site, go to Admin mode, click the Config tab and then Remote Web Sites.
2. Edit the local site name, enter "DemoSite" in the field and save.
3. Click Create. Enter "RemoteSite" in the Name field. Enter http://localhost/RemoteSite” in the URL field. In the Shared secret for signature field, copy and paste the key that was created when you created the remote site in the previous step.
4. Enter a valid Web service user, password, and domain. This is the same Web service user you entered in the previous step.
5. Click Save. Click Ping and verify that the connection between the demo (publishing) and remote sites works.

Subscriptions

Set up outgoing e-mail by entering the default SMTP server to be used under EPsSmtpServer in the site's web.config file, e.g.

Testing the Demo Environment

EPiFields

Outgoing E-Mail

Check that outgoing e-mail is working correctly by creating a subscription e-mail.

1. Go to the Subscription page under the Inspiration folder on the site.
2. Enter your e-mail address. (This is pre-stated if you have previously entered your e-mail address in My Settings.) Select As soon as possible in the Interval box and select the News check box. Click Save.
3. Create a news page with some content unde the News folder in the Inspiration tab.
4. Go to Admin mode and select Subscription under Scheduled Jobs. Click Start Manually,
5. A subscription e-mail will be sent to the e-mail address that you stated in the subscription.

Statistics

Version Control

Client Tools

WSRP – Consuming Portlets

Mirroring

Create a Channel and Destination in Your Demo Site

1. In the demo site, go to Admin mode, click the Config tab and then Mirroring Administration.
2. Click Create. Enter DemoChannel in the Name field. Choose a page, from where you wish to publish the tree structure (It should have children).
3. Choose "Tree" in the Mirror Type box.
4. Select Include the start page. Click Save.
5. Click Create Destination. Select “EPiServer” in the Select destination type box. Click OK.
6. Enter EPiServerDest in the name field. Choose your second EPiServer site in the Remote site box. Choose a page at the remote site and enter the page’s ID in the Root page on destination field. Click Save.

Publish a Page to the Remote EPiServer Site

1. In the demo site, edit the page that you selected as the publishing start page above. Save and publish the page.
2. Open the Action Window and click Approve mirroring updates. A list of updated channels appears and “DemoChannel” is listed with the amount of updated pages in parentheses. Click DemoChannel.
3. The currently updated pages are listed and a Publish button appears at the bottom. Click Publish.
4. Go to Mirroring administration on the Config tab in Admin mode. A list of queued jobs is listed under the channel Queue Length (If the scheduled service already executed it will say 0).
5. If the scheduled service does not run, click Mirroring Service under the Admin tab and click Start Manually. Check that the pages were published on the remote site.

Publish a Page to HTML

1. In the demo site, go to Admin mode, click the Config tab and then Mirroring Administration.
2. Click DemoChannel and then Create Destination.
3. Select “HTML” as the destination type and click OK.
4. Enter EPiServerHTML in the name field.
5. Create a directory “C:\episerverhtml” in your file system. Enter C:\episerverhtml in the Target Directory on the server” field. Enter /episerverhtml/ in the Relative root path field if you are to run the remote site from your hard drive. Click Save.
6. Create a new page in the demo site, publish it, and approve the mirroring updates in the Action Window. If the scheduled service does not run, click Mirroring Service under the Admin tab and click Start Manually.
7. Verify that the pages have been written to “C:\episerverhtml”.

Publish a page to XML

1. In the demo site, go to Admin mode, click the Config tab and then Mirroring Administration.
2. Click DemoChannel and then Create Destination.
3. Select “XML” as the destination type and click OK.
4. Enter EPiServerXML in the name field.
5. Create a directory “C:\episerverxml” in your file system. Enter C:\episerverxml in the Target Directory on the server field.
6. Create a file called template.xsl under C:/episerverxml and fill it with the text in the "template.xsl" chapter of the Appendix. (The demo template.xsl is only a basic XSL example.)
7. Enter C:\episerverxml\template.xsl in the Path to XSL template field. Click Save.
8. Create a new page in the demo site, publish it, and approve the mirroring updates in the Action Window. If the scheduled service does not run, click Mirroring Service under the Admin tab and click Start Manually.
9. Verify that the pages have been written to “C:\episerverxml”.

Referenced Documentation

The following documents are used as a reference in this document.

• EPiServer Installation Instructions
• EPiFields Developer Information
• Unified File System
• Version Control in EPiServer
• Log Service Installation Instructions
• Mirroring - Configuration and Operation

Appendix