Installation Guide

This guide expects that SharePoint Server 2010 is also set in server(s) where portal is run. You can find some guides SharePoint 2010 installation and security guides here:

1. Creating web applications

The suggested setup of portal contains two web applications. One of them is public web site and the other is extending web application that works in local network and uses NTLM to authenticate users. Second application can be also accessible only from local machine as it is used for administrative purposes. Of course, if you need you can make it also visible externally.

You don’t have to create site collection on web application because deployment script clears web application before installing packages and making modifications to created sites and site collection.

2. Configure Windows Live ID support

Web applications need Live ID and portal URL-s settings to work properly. There are four web applications that need settings to be specified:
  • public portal,
  • internal portal,
  • SharePoint Central Administration site,
  • SharePoint authentication service site.

Before going to change web.config files you need Windows Live ID service account in Windows Azure. You can start here. You need Windows Live ID service account only for the web application that is serving your community users. For internal portal you don’t need Live ID support.

NB! When registering Windows Live ID service account you are asked for return page. Return page that handles Live ID authentications is located at:

http://your-domain/_layouts/eneta.portal.authentication/LiveAuthHandler.aspx

Open web.config files of public and internal portal and replace authentication, membership and rolemanager blocks with blocks given below.

<authentication mode="Forms">
    <forms loginUrl="/_layouts/Eneta.Portal.Authentication/LiveAuthHandler.aspx?action=login" />
</authentication>
<membership defaultProvider="i">
    <providers>
        <add name="i" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthMembershipProvider, 
Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c
" /> <add name="LiveID" type="Eneta.Portal.Authentication.Live.LiveMembershipProvider,
Eneta.Portal.Authentication, Version=1.0.0.0, Culture=neutral, PublicKeyToken=53d887a3f906cc2b
" /> </providers> </membership> <roleManager defaultProvider="c" enabled="true" cacheRolesInCookie="false"> <providers> <add name="c" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthRoleProvider,
Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c
" /> <add name="LiveRoles" type="Eneta.Portal.Authentication.Live.LiveRoleProvider,
Eneta.Portal.Authentication, Version=1.0.0.0, Culture=neutral, PublicKeyToken=53d887a3f906cc2b
" /> </providers> </roleManager>

Save web.config files.

Open web.config file of Central Administration web site and replace membership and rolemanager blocks with the following blocks.

<roleManager defaultProvider="AspNetWindowsTokenRoleProvider">
    <providers>
        <add name="LiveRoles" type="Eneta.Portal.Authentication.Live.LiveRoleProvider, 
Eneta.Portal.Authentication, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=53d887a3f906cc2b
" /> </providers> </roleManager> <membership defaultProvider="LiveID"> <providers> <add name="LiveID" type="Eneta.Portal.Authentication.Live.LiveMembershipProvider,
Eneta.Portal.Authentication, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=53d887a3f906cc2b
" /> </providers> </membership>

Save web.config file.

Open token service web.config file. It is usually located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\SecurityToken. Add the following blocks to system.web section.

<membership defaultProvider="i">
    <providers>
        <add name="i" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthMembershipProvider, 
Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c
" /> <add name="LiveID" type="Eneta.Portal.Authentication.Live.LiveMembershipProvider,
Eneta.Portal.Authentication, Version=1.0.0.0, Culture=neutral, PublicKeyToken=53d887a3f906cc2b
" /> </providers> </membership> <roleManager defaultProvider="c" enabled="true" cacheRolesInCookie="false"> <providers> <add name="c" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthRoleProvider,
Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c
" /> <add name="LiveRoles" type="Eneta.Portal.Authentication.Live.LiveRoleProvider,
Eneta.Portal.Authentication, Version=1.0.0.0, Culture=neutral, PublicKeyToken=53d887a3f906cc2b
" /> </providers> </roleManager>

Save web.config file.

As all web applications communicate with at least portal authentication module you need to insert portal configuration parameters to all of web.config files mentioned above. Add the following parameters to appSettings section of all web.config files.

    <add key="WLA_ApplicationAlgorithm" value="wsignin1.0" />
    <add key="WLA_ApplicationId" value="YOUR_LIVEID_APPLICATION_ID" />
    <add key="WLA_ApplicationKey" value="YOUR_LIVEID_APPLICATION_ID" />
    <add key="WLA_ApplicationMode" value="http" />
    <add key="WLA_LockedUrl" value="http://yourdomain/Pages/AccountLocked.aspx" />
    <add key="WLA_ProfileList" value="ProfileList" />
    <add key="WLA_ProfileSiteUrl" value="http://yourdomain/" />
    <add key="PortalProfilePageUrl" value="http://yourdomain/Pages/profile.aspx" />
    <add key="PortalProfileEditPageUrl" value="http://yourdomain/Pages/editprofile.aspx" />
    <add key="PortalForumSiteUrl" value="http://yourdomain/forum/" />
    <add key="PortalForumPageUrl" value="http://yourdomain/forum/Pages/default.aspx" />
    <add key="PortalBlogEditPageUrl" value="http://yourdomain/news/blogs/Pages/add.aspx" />
    <add key="PortalBlogSiteUrl" value="http://yourdomain/news/blogs/" />
    <add key="PortalAnnouncementsSiteUrl" value="http://yourdomain/news/announcements/" />
    <add key="PortalAnnouncementsEditPageUrl" value="http://yourdomain/news/announcements/Pages/add.aspx" />
    <add key="PortalCompaniesSiteUrl" value="http://yourdomain/companies/" />
    <add key="PortalApproverRoleName" value="Approve" />
    <add key="PortalNewsSiteUrl" value="http://yourdomain/news/" />
    <add key="PortalEventsSiteUrl" value="http://yourdomain/events/" />
    <add key="PortalEventsEditPageUrl" value="http://yourdomain/events/Pages/NewEvent.aspx" />
    <add key="PortalCompanyEditPageUrl" value="http://yourdomain/companies/Pages/add.aspx" />
    <add key="PortalModeratorEmail" value="moder@yourdomain" />

Save web.config files.

3. Installing portal

NB! Don't apply installation package before creating and configuring web applications!
  1. Download latest installation archive from portal home page @ CodePlex.
  2. Unzip installation archive to some folder in server where portal will be run.
  3. Run the following command on command line when you are in deployment package folder:

    gacutil /i Eneta.Portal.Common.dll
    gacutil /i FredCK.FCKeditorV2.dll
     
  4. Open SharePoint PowerShell console and move to installation folder.
  5. Type the following command to PowerShell console (NB! No trailing slash!)

         .\install.ps1 http://yourdomain

    and press Enter.

You may see some errors (red) but don’t you can ignore them. These errors are given because there is no portal features and packages installed yet. Installation process starts with creating site collection by deployment script. From this step on all red errors you get refer to some problem with your SharePoint installation, permissions or other parts of your technical environment. To get help please post your questions to our discussions here.

4. After installation configuring

When portal packages are successfully deployed by deployment script there are some changes required in web.config file of public web application.

  • open web.config file of public web application,
  • look for SafeControl blocks where assembly names are starting with Eneta.Portal,
  • set SafeAgainstScript attribute value to true for all these blocks,
  • save web.config file.

Copy resource files from deployment package resources folder to App_GlobalResources folder of public and internal web application.

Try out if portal works and try to join it using your Windows Live ID!

Last edited Feb 16, 2011 at 5:20 PM by gpeipman, version 8

Comments

No comments yet.