Sitecore Foundry · 2019. 3. 6. · Sitecore Foundry can be hosted on a Microsoft Windows 2003...

Sitecore Corporation

Sitecore. www.sitecore.net [email protected]

Content Delivery [email protected] +45 70 23 66 60

Sitecore Foundry Installation Guide

Author: Sitecore Corporation

Date: Thursday, 31 January 2008

Release: Rev. 0.9

Language: English

Sitecore® is a registered trademark. All other brand and product names are the property of their

respective holders.

The contents of this document are the property of Sitecore.

Copyright © 2001-2007 Sitecore. All rights reserved.

Sitecore Sitecore Foundry Installation Guide of 27 Sitecore® is a registered trademark. All other brand and product names are the property of their respective holders. The contents of this document are the property of Sitecore. Copyright © 2001-2007 Sitecore. All rights reserved.

Table of Contents

Chapter 1 Sitecore Foundry Prerequisites 3

Chapter 2 Installation 6 2.1 Installing Sitecore Foundry using Installation Wizard. 6 2.1.1 Introduction 6 2.1.2 Database Setup 6 2.1.3 Solution Root Setup 11 2.2 Installing Sitecore Foundry from zip archive 16 2.2.1 Configuring permissions 17 2.2.2 Configuring the server connection mode 19 2.2.3 Adding cluster indexes to the sql databases. 19

Chapter 3 Post Installation Steps 21 3.1 Tighten MS SQL security 21 3.1.1 Add New Login 21 3.1.2 Add the new user to the database 22 3.1.3 Add new role to the database 22 3.1.4 Grant Execute Rights 24 3.1.5 Add role to db_datareader and db_datawriter 25 3.2 Database Index Tuning 25 3.2.1 Recommended Database Changes to Improve Performance 26 3.2.2 Tuning Indexes in Management Studio 26 3.2.3 Index Maintenance 27 3.2.4 Staging Considerations 27 3.2.5 References 27


Chapter 1 Sitecore Foundry Prerequisites

Sitecore Foundry can be hosted on a Microsoft Windows 2003 server accessed by multiple

clients. For Sitecore server hosts, Sitecore Foundry highly recommends Microsoft SQL Server

2005 running on a separate database server. Microsoft SQL Server Express Edition and Visual

Studio 2005 are recommended for developer workstations hosting Sitecore.

To reduce ASP.NET configuration issues on Sitecore hosts, install IIS before updating the .NET

framework. Some antivirus Software can be detrimental to performance of ASP.NET applications

such as Sitecore. For Sitecore hosts, use only those antivirus scanners certified for the operating

system (see http://cert.veritest.com/CfWreports/server). Certain listed products may interfere with

the application such as affecting HTTP data streams; Norton Antivirus is one known culprit.

Sitecore clients are simply browser-based user interfaces; other than Firefox 2 or Microsoft

Internet Explorer 7 or 6 configured as described below, no additional software must be installed

on Sitecore clients accessing Sitecore hosts. All Sitecore host and client systems should meet any

minimum criteria outlined by Microsoft and/or other respective software vendors for the relevant

component configurations such as a Microsoft Windows XP workstation or Microsoft Windows

2003 ASP.NET server.

Microsoft Windows

Sitecore highly recommends Service Pack 2 (or R2) for Microsoft Windows 2003; as a minimum

Service Pack 1 is required.

Microsoft Windows 2000 is not supported by Sitecore Foundry.

As a Windows administrator, use Microsoft Windows Update

(http://windowsupdate.microsoft.com) to patch and reboot Sitecore host and client machines until

Windows Update reports no remaining relevant updates are available excepting any updates

documented by Sitecore to negatively affect the application.

Sitecore supports and tests the CMS product on 32-bit Windows operating systems and on 64-bit

Windows operating systems using 32-bit compatibility mode for web applications (Microsoft

Vista and Microsoft Windows 2003).

Any available updates to the .NET framework should be applied to Sitecore hosts. Windows

console or Remote Desktop access and administrative rights are required to install software such

as Sitecore and Windows Updates.

http://cert.veritest.com/CfWreports/server

http://windowsupdate.microsoft.com/


Internet Explorer

Sitecore Foundry supports Firefox 2 for the WebEdit, Preview, Content Editor and Workbox

Sitecore clients, Microsoft Internet Explorer is not required. Internet Explorer 6 or 7 is required

for the Desktop and DeveloperCenter clients. For Internet Explorer 6, MSXML 4.0 must be

installed either KB918899 (http://support.microsoft.com/kb/923996) must be removed or

KB923996 (http://support.microsoft.com/kb/923996) must be installed; alternatively to obtain

KB923996 which correct the defect in the browser:

Windows XP:

http://www.microsoft.com/downloads/details.aspx?FamilyID=ff9bc431-01f3-48e8-9a58-

d701d2e60c1d&DisplayLang=en

Windows 2003:

http://www.microsoft.com/downloads/details.aspx?familyid=4AE4AA58-97FB-4CCF-

ABA4-F9271A9282E2&displaylang=en

No updates are required for Internet Explorer 7.

Sitecore Host Database

Sitecore hosts require access to a relational database. Options include:

1. Microsoft SQL Server 2005

2. Free Microsoft SQL Server 2005 Express Edition

Minimum Sitecore Client Requirements

Intel Pentium IV at 2GHz or faster processor

512MB RAM minimum, 1GB recommended

Firefox 2.0 or Internet Explorer 6 or 7 for WebEdit, Preview, Content Editor and

Workbox Sitecore clients. For the Sitecore Desktop only Internet Explorer 6 or 7 is

supported. Internet Explorer 7 is supported on Microsoft Windows Vista as a client for

authoring content.

TCP/IP connection at 512Kbps or faster to the Sitecore host

1024x768 or greater screen resolution recommended and required for advanced

operations and specific modules

Minimum Sitecore Development Host Requirements

Includes Minimum Sitecore Client Requirements

1 GB RAM minimum, 2GB recommended

Updated Microsoft Windows operating system with IIS and ASP.NET 2.0 installed. For

information about supported operating systems, see Microsoft Windows section above.

Microsoft SQL 2005 Express Edition running locally highly recommended, SQL Server

2005 optional

Microsoft Visual Studio .NET highly recommended

Minimum Sitecore Server Host Requirements

Includes Minimum Sitecore Client Requirements if the server will also be used as a

Sitecore client

http://support.microsoft.com/kb/923996

http://support.microsoft.com/kb/923996

http://www.microsoft.com/downloads/details.aspx?FamilyID=ff9bc431-01f3-48e8-9a58-d701d2e60c1d&DisplayLang=en

http://www.microsoft.com/downloads/details.aspx?FamilyID=ff9bc431-01f3-48e8-9a58-d701d2e60c1d&DisplayLang=en

http://www.microsoft.com/downloads/details.aspx?familyid=4AE4AA58-97FB-4CCF-ABA4-F9271A9282E2&displaylang=en

http://www.microsoft.com/downloads/details.aspx?familyid=4AE4AA58-97FB-4CCF-ABA4-F9271A9282E2&displaylang=en


Intel Core Duo or faster processor, dual CPUs recommended

2 GB RAM minimum, 4GB recommended

Updated Microsoft Windows operating system with IIS and ASP.NET 2.0 installed. For

information about supported operating systems, see Microsoft Windows section above.

Microsoft SQL Server 2000 or 2005 on a separate machine highly recommended


Chapter 2 Installation

Sitecore Foundry distributive is shipped in two versions:

1. Executable installation wizard (for instance, Sitecore Foundry XXXX.exe)

This distributive version is easier to install but requires a permissions to launch .exe files

on a server.

2. Archive of the clean Sitecore Foundry root folder.

This distributive is a zip archive containing the product‟s root folder with all necessary

databases. Manual setup is required after the solution is extracted from the archive.

The following sections describe each of these installation versions in detail.

2.1 Installing Sitecore Foundry using Installation Wizard.

This section describes the Sitecore Foundry installation wizard which guides you through the

setup process.

2.1.1 Introduction

Sitecore Foundry installation program consists of two separate.exe installation files:

Sitecore Foundry XXXX.exe

Sitecore Foundry XXXX DB.exe

If you wish to setup both the Sitecore SQL databases and the Sitecore Client on the same

machine, you will only need the Sitecore Foundry XXXX.exe file.

If the databases are to be hosted on a separate database server, you should run Sitecore Foundry

XXXX DB.exe on that server first, and then perform the installation of the Sitecore Client on the

client machine.

The following manual describes the correct way of Sitecore Foundry installation.

2.1.2 Database Setup

Below we consider the case when the databases are hosted on a separate database server.

1. Run Sitecore Foundry XXXX DB.exe on the database server.


2. Review the Welcome dialog.

3. The License Agreement dialog.

Read the license terms and select Accept if you agree to continue the installation, or

Decline if you disagree and cancel the installation.


4. The Instance Name dialog.

The Instance Name is a unique folder name for the database files to be stored.

5. The Destination Folder dialog.

This dialog allows changing the default destination folder for the Sitecore databases.

You should also use this path during the installation of the Sitecore Client afterwards.

This path will be written in to the configuration files to specify the database location.


6. The SQL Login Settings dialog.

Provide the connection settings for MS SQL database types here.

By default sa user is used. For information about creating appropriate database users, see

3.1, Tighten MS SQL security.

When you press Next, the installation program will try to establish the connection using

the parameters specified. If the attempt is successful, you will be allowed to proceed.

Otherwise, the program will offer to try again. Note that you should provide the SQL

Server name, which is used on the current server. Otherwise, the installation will not be

performed correctly.


7. Ready to Install dialog.

Press Install to start the installation process or Back if you wish to change something.

8. Installation complete dialog.

This dialog will be displayed when the installation is successfully completed.


2.1.3 Solution Root Setup

1. Start Sitecore Foundry XXXX.exe 2. Review the Welcome dialog.

3. The License Agreement dialog.

Read the license terms and select Accept if you agree to continue the installation, or Decline

if you disagree and cancel the installation.


4. The prerequisites dialog.

The installation checks the prerequisites at the very beginning of the installation. This dialog

shows the results of the check. If your machine satisfies the prerequisites, the green

checkmark is displayed; otherwise you will see a red cross mark. There is also an option to

install ASP.NET 2.0 component on the chosen site.

This option is checked by default. If the last prerequisite from the list is not satisfied, it is

strongly recommended to leave this checkbox checked. If you uncheck it, then you are made

responsible for the web site configuration.

5. The License dialog.

Browse and point the valid Sitecore license. Only in this case you will be allowed to proceed

with the installation. Click Browse button and select the license file, then click Next.


6. The Website name dialog.

Enter the name of the Sitecore website here. Due to the fact that several instances of Sitecore

can be installed on one machine, this name serves as a unique identifier for the rest of the

information related to this particular instance.

7. The Destination folder dialog.

This dialog allows changing the default destination folder for Sitecore.


8. Choose IIS site dialog

If you install Sitecore on Windows 2003 operating system, this dialog lets you specify

whether you wish to create a new IIS website for the new Sitecore instance, or use any

existing one. The checkbox “Create IIS site” is set by default. If you uncheck it, the dropdown

menu with all available sites will appear. Choose a site, and Sitecore will be accessible

through this site after the installation.

9. Choose installation type.

We are trying install Sitecore Foundry on two servers, so you should select the Client only

type and set database folder same as you set in the database installer.


10. The SQL login settings dialog

Provide the connection settings for MS SQL or SQL Express database types here. In case of

MS SQL 2000 or SQL Express / 2005 option and client only installation type, the name of

database server should be entered, where the databases are already installed. When you press

Next, the installation program will try to establish the connection with the parameters

specified. If the attempt is successful, you will be allowed to proceed. Otherwise, the program will offer to try again.

11. Ready to install dialog.

Look through your choices here. There is also an option to switch the IIS root to the newly

created Sitecore instance. Press Install if you agree with the settings or Back, if you wish to

change something.


12. Installation complete dialog.

This dialog will be displayed if the installation is completed successfully. You may check the

Run Sitecore checkbox to run Sitecore after clicking the Finish button.

2.1.3.1 Configure mss.config and ISS.

Change the settings in the mss.config file:

Fill the MainSiteDescription setting in mss.config file with the name of the created site.

This should be the name selected in the Website name dialog.

Fill the MainSiteAddress setting with the URL of the new site.

Perform steps 8-10 from Section 2.2, Installing Sitecore Foundry from zip archive

(404 handler, mail server, add admin right to application pool user).

2.2 Installing Sitecore Foundry from zip archive

This section describes the installation of Sitecore Foundry from a zip archive. The installation

process consists of the following steps.

1. Install and patch Microsoft Windows, IIS, ASP.NET, SQL Server.

2. Extract the .zip distributive of Sitecore Foundry to a folder which is supposed to be the

web site root folder (for example, C:\Inetpub\SitecoreFoundry).

3. Place the appropriate license.xml file in the folder specified by the dataFolder setting in

web.config file. The location of the license.xml file can also be specified by the following

string in web.config:

<setting name="LicenseFile" value="$(dataFolder)/license.xml" />

4. Configure the security permissions as described in the Configuring permissions section.

5. Specify the connection to Sitecore Foundry SQL databases by entering appropriate

attribute values in the /configuration element of

/Website/App_Config/SqlServer/fileConnections.config file.

The attributes have the following meaning:

serverName – the name of SQL server

dataFolder – the folder where the Sitecore Foundry databases reside

prefix – the database prefix

user – SQL sever user

password - SQL sever user password

For example:

<configuration serverName=".\SQLEXPRESS" dataFolder="d:\Sitecore

Foundry\Databases\" prefix="scf53" user="sa" password="12345">

The databases will be attached to SQL server dynamically when Sitecore Foundry starts.

By default Sitecore Foundry runs in file connection mode. If you want to run the product

in server connection mode, please refer to Section 0, Before attaching the databases,

ensure that SQL server has access to the database files at the file level. SQL server runs

in a security context of a given user. In SQL Server 2005 a couple of new windows user

accounts have been created. One of them is

„SQLServer2005MSSQLUser$(servername)$SQL_2005‟, where „(servername)‟ is


replaced by the name of the physical server being installed on. Giving this account full

access ensures that SQL server has necessary security rights to manipulate the database

files.

For instance, on a machine running Windows XP the NETWORK SERVICE user should have

read/write permissions to the database files.

6. Configuring the server connection mode

7. Create a new web site in IIS which will be used as a Sitecore Foundry site.

8. Fill the MainSiteDescription setting in the mss.config file with the name of the created

site. You should also fill the MainSiteAddress setting with the URL of the new site.

9. Point the home directory of the IIS site to the Sitecore Foundry root folder (for instance,

C:\Inetpub\SitecoreFoundry).

10. Add custom error page in IIS. Use the following instructions to do this.

Start IIS Manager by running the inetmgr command from Windows console, select a

Sitecore Foundry web site, right-click on it, select Properties » Custom errors and set the

following value for 404 http error:

Message type: URL

URL: /sitecore/notfound.aspx

11. Change SMTPServer setting in the mss.config file located under the Sitecore Foundry

root folder to your smtp server.

<setting name="SMTPServer" value="server.mail.net" />


12. To allow updating IIS binding the administration rights should be given to the selected

application pool user. If a custom user is used, such user should belong to the

Administrators group.

2.2.1 Configuring permissions

Requests for ASP.NET resources are executed with the permissions of ASP.NET. The default

ASP.NET account on Windows 2003 is local user named NETWORK SERVICE.

In general, if permissions for OS users and roles are not specified in this document, they should

not be defined on the file system, although certain use cases will require expanded permissions.

The IUSR_* user should have Read and Execute access to the Sitecore Foundry root folder and

all descendants.

It‟s generally easiest to grant the ASP.NET user Full Control of the Sitecore Foundry root folder

and Data folders as well as all descendants, but it‟s also possible to further restrict permissions.

The ASP.NET user must have Read and Write access to the following resources under the

specified circumstances:

Directory Situations in which ASP.NET Requires Full

Control

/data All Sitecore Foundry environments in which this

folder is used.

/indexes All Sitecore Foundry environments.

/layouts If Developer Center will be used to create and modify

layouts and sublayouts.

/sitecore/shell/Applications/debug All Sitecore Foundry environments against which

CMS users authenticate (generally everything except

content delivery/runtime servers); create this directory

if it does not exist.

/sitecore/shell/Controls/debug All Sitecore Foundry environments against which

CMS users authenticate (generally everything except

content delivery/runtime servers); create this directory

if it does not exist.

/temp All Sitecore Foundry environments.

/upload Sitecore Foundry environments to which users

interactively upload media.

/xsl If Developer Center will be used to create and modify

XSL renderings.

/sitecore modules/mss For custom Sitecore Foundry XML controls, all


directories specified in the ControlSources section of

web.config must contain a debug folder with

Read/Write access by the ASP.NET user.

Before attaching the databases, ensure that SQL server has access to the database files at the file

level. SQL server runs in a security context of a given user. In SQL Server 2005 a couple of new

windows user accounts have been created. One of them is

„SQLServer2005MSSQLUser$(servername)$SQL_2005‟, where „(servername)‟ is replaced by

the name of the physical server being installed on. Giving this account full access ensures that

SQL server has necessary security rights to manipulate the database files.

For instance, on a machine running Windows XP the NETWORK SERVICE user should have

read/write permissions to the database files.

2.2.2 Configuring the server connection mode

Sitecore Foundry works with SQL Server 2005 in two modes:

File connection mode – all databases are attached to the SQL Server when

Sitecore Foundry is started for the first time

Server connection mode – Sitecore Foundry connects to the predefined databases

on the server. In this mode you should attach databases to the server before you

start Sitecore Foundry.

To use the Server connection mode you should do the following:

1. Attach databases to a server.

To attach SQL databases to the server, use the SQL script which you can download by

following the next link:

http://sdn.sitecore.net/foundry_downloads.aspx

You should change two local variables in the script: @pathToDatabases – path to the

folder with databases, and @databasePrefix – the prefix which will be added to all

databases.

2. Execute the script on your server.

Note: make sure that SQL user has write access to the folder with databases.

3. Change connection mode to Server in the web.config file:

<configuration>

...

<sitecore database="SqlServer">

...

<connections serverMode="Server">

...

4. Change ServerConnection configuration file.

Specify connection to the databases in the ServerConnections.config file located in the

/App_Config/SqlServer/ folder. In the configuration section set server name, database

prefix, user name and user password:

<configuration serverName="_server_" prefix="_sc53_" user="_user_"

password="_password_">



2.2.3 Adding cluster indexes to the sql databases.

Database index tuning can increase the performance of high-volume Sitecore solutions to improve

the user experience. For more information about database index tuning, refer to

Section 3.2, Database Index Tuning.

The SQL script which should help you to add cluster indexes for all databases can be downloaded

from the following page:


To add indexes:

1. Start Sitecore Foundry.

2. Backup all SQL databases. This step is not necessary if you run the script on the clean

installation.

3. Change the database names in the script from SC53ARCHIVE, SC53CORE,

SC53MASTER, SC53RECYCLEBIN, SC53SECURITY, SC53WEB to the names of you

archive, core, master, recyclebin, security, web databases.

4. Execute the script.

The script adds cluster indexes to the specified databases.



Chapter 3 Post Installation Steps

This section describes recommended steps to take after the Sitecore Foundry web root and

databases have been installed.

3.1 Tighten MS SQL security

This section applies to DBO's who want to tighten security on the SQL server.

Instead of giving dbowner rights (full MS SQL rights) to the user on all databases, you can create

roles that have nothing but execute rights on stored procedures and read/write rights on the tables.

3.1.1 Add New Login

Add new Login, e.g. "johnDoe":

Important Note: The following steps must be completed for each database.


3.1.2 Add the new user to the database

Add the new user to the database, by right-clicking Users, New database user…

3.1.3 Add new role to the database

Add a new role, e.g. 'sitecore_user', by right-clicking Roles, New database role…


Add new user (created in step 1) to the new role (created in step 2.a).


3.1.4 Grant Execute Rights

Click OK, and then reopen the new role grant execute rights to all stored procedures and all user

defined functions (not system objects, e.g. prefixed with dt_):


3.1.5 Add role to db_datareader and db_datawriter

To the existing roles, db_datareader and db_datawriter, add the new role:

Using SQL script to create user and role

Alternatively you may run this SQL script, that creates a user “sitecore” with password “sc”, and

adds the role “sitecore_user” to each database.

If you wish to create other user and other role, make appropriate changes to the script.

Download SQL script

3.2 Database Index Tuning

Database index tuning can increase the performance of high-volume Sitecore solutions to improve

the user experience for both editors and the viewing public. This article applies primarily to

Sitecore implementations using SQL Server 2005, though similar techniques could be applied on

solutions using other supported RDBMS technologies. The specific techniques described in this

resource have been shown to improve performance by up to 100 times for certain operations.

Note: this document applies to Sitecore versions through 5.3.1 070924. The database schema

released in subsequent versions contains the index changes suggested below, but the upgrade

process from 070924 and earlier does not apply these changes automatically (they should be

applied manually after the upgrade).

http://sdn5.sitecore.net/SDN5/Resources/Tools/MS%20SQL%20Tighten%20Security%20Script.aspx


3.2.1 Recommended Database Changes to Improve Performance

For the SharedFields table in All Sitecore Databases:

o Change the ndxLookup index from Nonclustered to Clustered

o Configure Fill Factor for the ndxLookup index to between 50% and 75%

o Enable Pad Index for the ndxLookup index

For the VersionedFields table in All Sitecore Databases:

o Create a clustered index named ndxItemIdon the column ItemId

o Configure Fill Factor for the ndxItemId index to between 50% and 75%

o Enable Pad Index for the ndxItemId

For the UnversionedFields table in All Sitecore “Master” databases:

o Create a clustered index named ndxItemId on the column ItemId

o Configure Fill Factor for the ndxItemId index to between 50% and 75%

o Enable Pad Index for the ndxItemId index

3.2.2 Tuning Indexes in Management Studio

Updating the Type of an Existing Index (from Nonclustered to Clustered)

To update properties of an existing index take the following action;

Expand Indexes under the table

Double-click on the index

Change the Index type property on the General tab.

Configuring the Fill Factor or enabling Pad Index for an Existing Index

To set the Fill Factor or enable Pad Index for an existing index take the following steps;

Expand Indexes under the table

Double-click the index

Select the Options tab

Select the Set fill factor checkbox and enter a percentage

Select the Pad index checkbox if appropriate.

Acknowledge the index properties

Right-click on the index and choose Rebuild.

Creating a New Index

To create a new index take the following steps;

Right-click Indexes under the table

Choose New Index.

On the General tab enter the Index name then select the Index type

Press Add and select the column(s) to be indexed.


If specifying a Fill factor or enabling Pad Index, select the Options tab, select the Set fill

factor checkbox and enter a percentage.

Select the Pad index checkbox if appropriate.

3.2.3 Index Maintenance

Sitecore recommends rebuilding clustered indexes daily using T-SQL using the following format

for each index:

DBCC DBREINDEX('<tablename>','IndexName',<FillFactor>)

Where the first parameter specifies a database table (mandatory), the second parameter specifies

which index of that table is to be rebuilt (a blank causes all indexes to be rebuilt) and the third

parameter specifies the fill factor. For instance to rebuild all indexes for the VersionedFields

table using a fill factor of 75 you would use the following string:

DBCC DBREINDEX('VersionedFields',' ',75)

3.2.4 Staging Considerations

Apply indexing as appropriate for all databases including those employed by both Sitecore CMS

(Staging Master) and Content Delivery (Staging Slave) servers.

3.2.5 References

For more information on SQL Server indexing, Fill Factor and Pad Index, please see:

http://www.quest-pipelines.com/newsletter-v4/1203_B.htm

http://msdn2.microsoft.com/en-us/library/ms181671.aspx

http://www.quest-pipelines.com/newsletter-v4/1203_B.htm

http://msdn2.microsoft.com/en-us/library/ms181671.aspx

Sitecore Foundry · 2019. 3. 6. · Sitecore Foundry can be hosted on a Microsoft Windows 2003...

Documents

Transcript of Sitecore Foundry · 2019. 3. 6. · Sitecore Foundry can be hosted on a Microsoft Windows 2003...