Installation procedure 7.0 - 7.2

Smartsite 7 - ...

Important note!

This article is valid from Smartsite 7.0 to 7.2. Starting with Smartsite 7.3, the CmsServer is no longer a separate process. It is now integrated into the new manager.

Installation procedure

Because Smartsite 7 is based on Smartsite 1.4, the installation procedure is pretty much the same. You need to run both the CmsSetup and the PubSetup to install Smartsite 7. There is no extra setup that must be run. You do need to perform some extra configuration if you wish to use the new manager. Make sure you stop IIS before running the setups.

Additional steps you must perform to use the new manager are

Add an IIS Application pool

Add an IIS application pool to your IIS with the following properties:

Set the name to "<sitename>Mgr"
.Net Framework set to 4.0
Under advanced properties
- Set "Idle Timeout" to 0
- Set "Rapid fail protection" to disabled
- Set "Disable overlapped recycle" to true
- Set "Recycling - Regular time interval" to 0

Add an IIS Application

Add an IIS Application with the name "mgr" to your site. It must use the new IIS Application pool you just created and point to the folder "<siteroot>\WWWMgr".

Configure WWWMgr\Web.config

Rename the file "<siteroot>\WWWMgr\Web.example.config" to "Web.config" if you do not already have that file and configure the file.

Check the configuration:

In the "<system.webServer>\<modules>" section several HttpModules are already removed that are defined in the "<siteroot>\WWW\Web.config" file. These HttpModules need to be removed, because they are automatically inherited by Asp.Net but need to be excluded. Check if you have more custom HttpModules in "<siteroot>\WWW\Web.config" that need to be removed.
Apply the above also for the "<system.webServer>\<handler>" section.
In the "<system.serviceModel>" section, check the configuration of the InteropService client endpoint.
In the "<system.serviceModel>" section, add a new client endpoint for the CmsServer

Client endpoint:

<endpoint name="CmsServer" address="http://localhost/services/wcf/cms" binding="wsHttpBinding" bindingConfiguration="CmsServerBinding" contract="Smartsite.Cms.Client.CmsServer"/>

wsHttpBinding:
<binding name="CmsServerBinding" maxReceivedMessageSize="100000000">
    <readerQuotas maxStringContentLength="1000000"/>
    <reliableSession enabled="true"/>
    <security mode="None"/>
</binding>

Configure the CmsServer

Rename the file "<siteroot>\Applications\CmsServer\CmsServer.exe.example.config" to "CmsServer.exe.config" if you do not already have the file "CmsServer.exe.config".

Check the configuration:

Set the "InstanceID" in the AppSettings section.
Check if the MemberschipProvider configuration matches the one in your "<siteroot>\WWW\Web.config". Note that if your site runs on Active Directory, you should not use the Active Directory MembershipProvider but standard SqlMembershipProvider.
Check if the WCF service endpoint matches your outscaling needs. The default should be fine in most cases.

Run SetSiteSecurity

Run the SetSiteSecurity tool to set the security rules needed to run Smartsite 7. The SetSiteSecurity tool is since Smartsite 7.0 part of the PubSetup and no longer has its own setup. The executable is now located in the folder "<siteroot>\Applications\ConfigEditor". Note that IIS will have to be stopped for a moment while running SetSiteSecurity.

Install and start the CmsServer

Open the command prompt and go to "<siteroot>\Applications\CmsServer".

Run the command "CmsServer /install" to install the CmsServer as a Windows service.

Run the command "CmsServer /start" to start the Windows service.