Installation instructions for EPiServer Relate Intranet Templates

Prerequisites

  • .Net Framework 4.0
  • EPiServer CMS 6 (6.0.530.0)
  • Relate 2.0
    • EPiServer Community 4 (4.0.517.255)
    • EPiServer Search (1.0.517.262)
  • Intranet template package
    • src.zip - Template files
    • install.zip- Module with configuration

Install a temporary CMS site with Community and Search indexing service

  1. On a temporary location, install a CMS site with SQL database, using the EPiServer Deployment Center. During installation, enter all configurations that would like for you final installation. Don't install any templates during this installation.
  2. Install Community on the site, using EPiServer Deployment Center
  3. Install Search indexing service on the site, using EPiServer Deployment Center

Unpack the template package

  1. Unpack src.zip where you would like to place the template package
  2. Copy all files - except the global.asax file - from the site you created to the web root of the template package (Circuit.RelatePlus.Intranet.Web). Make sure this new folder has the same access rights as the old web root.

Configure IIS

  1. In IIS, point the created site to the web root of the template package (Circuit.RelatePlus.Intranet.Web).
  2. In IIS, change to run .NET 4.0

Configure web.config

  1. In EPiServer Deployment Center for CMS choose "Install a module from a compressed file"
  2. Select install.zip (note: change to view zip-files)
  3. Select your site installed in step 1 (note: you might need to check the "view all" option)
  4. Copy your license files to the web root folder
    1. License.config (CMS)
    2. EPiServerRelateLicense.config (Relate with community)

Set up the page tree

  1. After running install.zip you will now have a file named pagetree.episerverdata_distr in the util/setup folder in the template package's web root.
    1. Rename the file to pagetree.episerverdata
  2. Surf to the EPiServer admin UI of your site (www.yourhostname.com/yoursecretpath/ui/cms/admin/) and login with the admin user created in step 1.
  3. A process for importing the page tree will automatically start. Follow the on-screen instructions. Select English or Swedish language depending on what version you’d like.

Create Community data

  1. All community data except default categories will be automatically installed. If you want example categories (recommended), go to util/setup and run the english or swedish sql script in the community db setup earlier. Please not that you probably, depending on the installation in step 1, have two databases: one for cms and one for community.
    1. setup.medstore.en.sql
    2. setup.medstore.sv.sql
  2. Set access rights on the cms page tree. Only CommunityMembers should have access to to the pages below "Protected" and "Start Page":
    1. CommunityMembers: All access except “Administer” on start page and all pages below and including “Protected”.
    2. CommunityAdmins: Full access on start page and all pages below and including “Protected”.
  3. Go to Community/Admin and make the admin user created in the installation step member of the group CommunityMembers.
  4. Add more users for the intranet by using “Create User” in the admin interface. Make sure the users are members of CommunintyMembers group. If the users should be admin, make them member of CommunintyAdmins group.

Configure Search and URI provider

If you're running several sites on the web server (or if the web site doesn’t listen to “localhost”), make sure the following lines in web.config uses the correct hostname:
<namedIndexingServices defaultService="search">
<services>
<add name="search" baseUri="http://www.yourhostname.com/IndexingService/IndexingService.svc" accessKey="local" />
</services>
</namedIndexingServices>
<add name="CircuitRelatePlusProvider" type="Circuit.RelatePlus.Intranet.Utilities.Urls.UriProvider, Circuit.RelatePlus.Intranet.Utilities.Urls" baseUri="http://www.yourhostname.com" />

Last edited Mar 15, 2011 at 3:58 PM by sunnaster, version 3

Comments

magnusk Jan 15, 2012 at 5:51 PM 
Can anyone confirm they wont work, or even better, describe a valid solution?

Night_dog Dec 15, 2011 at 1:07 PM 
Hi,
This templates however won't work with EPiServer 6 R2 and the next version of Community.