Configuration for Production Environment - version 6.0.2

From Sense/Net Wiki
Revision as of 17:37, 6 March 2012 by Dobsonl (Talk | contribs) (Website settings)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
  • 100%
  • 6.0.2
  • Enterprise
  • Community
  • Planned


This page contains production environment configuration for Sense/Net 6.0.2. The following list contains configuration requirements that serve as guidelines when a Sense/Net 6.0.2 site is deployed to a live production environment.

SenseNet 6.0.2 version

System requirements


  • IIS7.5
    • Web Server
      • Common HTTP Features
      • Static Content
      • Default Document
      • Directory Browsing
      • HTTP Errors
    • Application Developement
      • ASP.NET
      • .NET Extensibility
      • ISAPI Extensions
      • ISAPI Filters
    • Health and Diagnostcs
      • HTTP Logging
      • Logging Tools
      • Tracing
    • Security
      • Windows Authentication (Only for AD integrated portals)
      • Request Filtering
    • Performance
      • Static Content Compression
      • Dynamic Content Compression
    • Management Tools
      • IIS Management Console

Windows Features

  • Windows Process Activation Service
    • Process Model
    • .NET Environment
    • Configuration APIs
  • .NET Framework 3.5.1 Features
    • .NET Framework 3.5.1
    • WCF Activation
      • HTTP Activation
      • Non-HTTP Activation

Additional components

  • MVC 2.0
  • .Net Framework 4.0
  • Application Warm-Up 1.0 for IIS 7.5

If NLB or AD sync. is in use, you should install and configure the following components

Additional system requirements for MSMQ:

  • Message Queuing
    • Message Queuing Services
      • Message Queuing Server
      • Directory Service Integration


Application Pool settings

  • .NET Framework version: 4.0
  • Process Model Identity: Network Service / domain user

If the app pool is running in the name of a user created for this goal, the following command is to be executed: c:\windows\Microsoft.NET\Framework64\v4.0.30319 Aspnet_regiis -ga domain\user

  • Process Model Idle Time-Out (minutes): 0
  • Recycling / Disable Overlapped Recycle: true
  • Recycling / Disable Recycling for Configuration Changes: true

Before changing configuration or updating/uploading dll's, the site has to be stopped, and started only after changes have been committed! Updates to configuration or changes in the webfolder bin directory may result in index malfunctioning if the site has not been stopped beforehand!

Website settings

  • Connection String
  • Machine Key (Optional for NLB) :
    • Generate Keys
    • Uncheck all auto generate checkbox
  • Session State : SQL or State Server

If you configure multiple web servers you should take one additional step. In IIS Manager under the Advanced Settings of the web site you should check that the ID of your site is the same on every IIS server. If not, you should change it to match.

  • Application Warm-Up:
    • Enable
    • Request
      • URL: InRepositoryPage.aspx
      • Status Code: 200-399
      • Request Send Mode: Asynchronous
  • Authentication: Anonymous

If Anonymous auth. is selected and a user is specified on the Application Pool Identity, edit the settings of the Anonymous Authentication and select the "Application pool identity".

In some scenarios you need AD integration, so you should select Windows Authentication.

File system settings

  • Grant Modify access to the Application Pool User on the Web folder

Web.config setting

  • Uncomment the following lines (Optional for NLB and AD snyc.):
<add key="ClusterChannelProvider" value="SenseNet.Communication.Messaging.MsmqChannelProvider, SenseNet.Storage"/>
<add key="MsmqChannelQueueName" value="servername\queuename" />

Configurations required

Configure Logging

  • You can find detailed information in the Logging section of our wiki under EventLog (see Logging#EventLog)

Configure MSMQ

  • First you need to create a public queue somewhere.

If you use it only for AD sync. You can create it on the web server localy. If you use it because of a multi server implementation (NLB) we highly recommend that you create the queue on a separated server which is not involved in the NLB.

  • Set the security settings of the queue as follows:
    • Grant full control to:
      • Everyone
      • Anonymous logon
  • In the web.config specify the name of the server and queue

Related links