In this article, I will try to explain the way to install and configure all the software stuffs for a SharePoint & Commerce Server virtual dev environment.
Software Architecture
First, I created two virtual machines, one for my domain controller and the other one for my web front end. Here are the details:
- Domain controller box :
- Windows Server 2008 Standard Core. My domain name is:ALTIPOC.LOCAL
- WFE box:
- Windows Server 2008 Standard
- SQL Server 2008 Standard
- WSS v3 with SP1
- MOSS 2007 with SP1
- Commerce Server 2007 Enterprise (Be careful guys, the Commerce Server Developer edition is not supported by Commerce Server 2009, you have to choose between the standard and the enterprise edition)
- Commerce Server 2009
Users
I’m not explaining the way to setup a domain controller because there are plenty of good articles about it. But I can recommend you an excellent one on Server Core Installation Option of Windows Server 2008 Step-By-Step Guide.
Service accounts you have to create for SharePoint
MOSSfarm (Execute the SharePoint Service – Must be a domain administrator)
MOSSRunTimeUser (Application Pool for the SharePoint Commerce Application)
MOSSsspPool (Application Pool for the Shared Service Provider)
MOSSsearchService (Execute the MOSS search service)
WSSsearchService (Execute the WSS search service)
WSScontentAccess (Get the content outside of the farm)
MOSSsspService (Execute the Shared Services Provider (SSP))
MOSSprofile (Get the profile information in the active directory)
MOSSsspMySite (Execute the SSP My Site)
Service accounts you have to create for SQL Server
SQLservice (Execute the SQL services)
Service accounts you have to create for Commerce Server
CatalogWebSvc (Application Pool for the catalog web service)
CSDMSvc (Execute the Direct Mailer service)
CSHealthMonitorSvc (Execute the Health Monitor service)
CSStageSvc (Execute the Staging service)
CSStagingUser (staging user)
MarketingWebSvc (Application pool for the marketing web service)
OrdersWebSvc (Application pool for the order web service)
ProfilesWebSvc (Application pool for the profile web service)
SQL Server 2008
In order to install SQL Server 2008, you have to check if the required components are installed. For that, you just have to click on the verification tool:

Once the prerequisites are validated, you can run the install:

In my case, I selected all the features, because I would like to use the Commerce Server Data Warehouse (an article about it will coming soon).

For all of my SQL Services accounts, I’m just using one. It’s not best practice, but for a development environment it’s acceptable
.

Beware, it’s important here to use the SQL_Latin1_General_CP1_CI_AS collation

Here we go, our SQL Server 2008 is up and running. We just need to enable the « Named pipes » for SQL Server.

You can install the service pack 1 for SQL as well (next, next,… finish
).
SharePoint 2007
First, install the Microsoft Office SharePoint Server 2007 with the SP1 slipstreamed :

Once MOSS is installed, we can configure the central administration for SharePoint. For that, just follow the wizard steps:

On a first installation, we have to create the SharePoint farm. So, just click “no, I want to create a new farm”:

The service account to use is the one I called “MOSSfarm”. This service account will run my SharePoint farm.

For the authentication, we can select either NTLM or Kerberos for our dev environment. Kerberos is more secure as we know, but I went with NTLM because it is faster to set up
.

Before configuring SharePoint, we need to install those patches in the following order:
- Infrastructure update for WSS
- Infrastructure update for MOSS
- February Cumulative update for WSS
- February Cumulative update for MOSS
Nothing special to do here, just the “Next, next,… finish”. After each patch installation, it’s very important to run the SharePoint configuration wizard (no screenie here, nothing special to do, just wait
).
Configuration
SharePoint
We are now configuring the SharePoint features.
Email
Open the SharePoint Central Administration and click on the tab « Operations » and then « Outgoing e-mail settings ».

In the page « Outgoing E-Mail settings », fill out the fields and click on « OK ».

For information, the pop3 service is no longer available in Windows 2008, to work around it, you can use the ArGoSoft Mail Server tool (it’s a freeware).
Search
Go to the SharePoint Central Administration and click on the tab « Operations » and then « Services on server ».

On the Services list, click on « Start » for the « Windows SharePoint Services Search » row:

Fill out the fields:

On the services list, click on « Start » for the « Office SharePoint Server Search » row:

Fill out the fields:

Shared Services
Search is now configured, we can now install the Shared Service. For that, in the left navigation pane click on « Shared Services Administration » :

click on « New SSP » :

In the next page, we have to create 2 different web applications. One for the SSP itself and one for the « My Site » application. First, click on “Create a new web application”:

Let’s create the first web application for the SSP. Just fill out the fields.

Now, same procedure than the SPP for the « My Site » web application:


The 2 web applications are now created, we just have to fill out the last fields:

The SSP is now up and running.

Commerce Server
In order to install Commerce Server 2009, you have to install first… Commerce Server 2007 ! Commerce Server 2009, will bring you new APIs oriented .Net 3.5 (Linq, Entities,.. ), but no change in the databases structure. If you want to know what is inside the new Commerce Server, have a look at: What’s New in Commerce Server 2009?
The Commerce Server team has released an excellent article on the installation and configuration: Microsoft Commerce Server 2009 RC Installation and Configuration Guide
Commerce Server 2007

The Commerce Server installation is now finished, let’s configure it:

You can now install the Service Pack 2. Pay attention if you want to use the Commerce Server rich client applications. You have to install them before to apply any Commerce Server service pack.
Commerce Server 2009
Installation

How to configure the « SharePoint Commerce Site »


Once Commerce Server 2009 is configured, you can now set up the MOSSRunTimeUser Service Account permissions for SQL:
Configuration
To finish the Commerce Site configuration, you have to provide the catalog name and the default channel. For that, open the web application -> site actions -> view all site content. Then click on the list « Channel configuration », Expand the menu on the « Channel » row and click on the « Edit item » then, fill out the value: "Default". Do the same for the « DefaultCatalog » item with the value: "Adventure Works Catalog".
Your commerce site is now ready 

Gaël Duhamel
Recent Comments