BizTalk 2010 Installation and Configuration – Install and Configure Windows SharePoint Services (Part 6)

Posted: October 23, 2010 in BizTalk
Tags: , ,

Windows SharePoint Services is a collection of services for Windows Server which enable you to share information, collaborate with other users on documents, and create lists and Web part pages. For information and procedures on installing Windows SharePoint Services, see Appendix A.

Note

You do not need to install WSS if you do not also plan to install the WSS adapter. However, if you are installing WSS, you must do it before continuing with the rest of the BizTalk Server prerequisites.

BizTalk Server 2010 supports these two versions of WSS:

  • SharePoint Foundation 2010
  • Windows SharePoint Services 3.0 with SP2

Installing and configuring Windows SharePoint Services consists of the following procedures:

  • Install Windows SharePoint Services
  • Configure Windows SharePoint Services
  • Extend the Default Web Site as a virtual server

I chose to install WSS 3.0 with SP2 for no particular reason.

Install Windows SharePoint Services 3.0 with SP2

In the following procedure you install Windows SharePoint Services 3.0.

  1. Windows SharePoint Services 3.0 requires Microsoft .NET Framework 3.0, which must be installed before beginning installation of Windows SharePoint Services 3.0. The .NET Framework is available for download at http://go.microsoft.com/fwlink/?linkid=75053.
  2. Browse to http://www.microsoft.com/downloads/en/details.aspx?FamilyId=EF93E453-75F1-45DF-8C6F-4565E8549C2A&displaylang=en. Download the installation package to a location on your hard disk.
  3. Locate the package you just downloaded (SharePoint.exe), and then double-click the package to start the setup.
  4. On the End User License Agreement screen, select I accept the terms in the License Agreement. On this screen and several others that follow, the setup wizard will automatically move to the next screen when you have made your selection.
    wss-agreement-screen
  5. Under Type of installation, choose the Advanced button.
    wss-installation-type-screen
  6. On the Server Type tab, select Web Front End, then click Install Now.
    wss-server-type-screen
  7. Ensure the configuration checkbox is clicked and click the “Close” button.
    wss-complete-screen
Configure Windows SharePoint Services
  1. On the Welcome screen, click “Next”
    wss-configuration-welcome-screen
  2. In the Warning screen, Click “Yes”
    wss-configuration-warning-screen
  3. On the Server Farm screen, select the option “No, I want to create a new server farm” and click “Next”
    wss-configuration-server-farm-screen
  4. On the Configuration Database screen, provide a Database server name and credentials and click “Next”.
    wss-configuration-database-screen
  5. On the Configure SharePoint Central Administration WEB Application screen, use the Default values and click “Next”.
    wss-configuration-Web-Application-screen
  6. On the Completing the SharePoint Products and Tecnologies Configuration Wizard screen, leave the default values and click “Next”
    wss-configuration-completing-screen
    wss-configuration-completing-2-screen
  7. On the Configuration Successfull screen, click “Finish”.
    wss-configuration-successful-screen
Extend the Default Web Site as a virtual server
  1. Open SharePoint Central Administration, and click “Application Management”
    SharePoint-admi-application-Management
  2. On the Application Management Tab, click on “Create or extend Web application”
    SharePoint-admi-create-extend-web-app
  3. At this point, normally I extend an existing Web application, this time I chose to follow Kent Weare suggestion and create a new one using the port 90, so click on “Create a new Web application”
    SharePoint-admi-create-extend-web-app-2
  4. I have decided to create my Web Application in a new IIS Web site called “SharePoint – 90”. I have done this so that I don’t overwrite or break anything that may be living in my Default Web Site. I also have modified the port to be “90” which means any requests to my WSS Site will need to have “:90” in the url. If you do this then when you post or retrieve documents to/from SharePoint from BizTalk that you will need to include this port number in your Receive Location/Send Port configuration.
    1. On IIS Web Site options, select “Create a new IIS web Site”, set a description and change Port to 90
    2. On Security Configuration options, set Authentication provider as NTLM
      SharePoint-admi-create-new-application
    3. On Load Balanced URL options, check if the URL as “:90”
    4. On Application Pool options, create a new application pool “Sharepoint – 90”
      SharePoint-admi-create-new-application-2
    5. On Database Name and Authentication options, appended “99” onto the Database Name that will be used for storing Content and chose “Windows authentication” option
    6. Click “Ok”
  5. You have now created the “shell” for this Web Application, but you still don’t have any content in this Web Application. Click on the “Create Site Collection” link. Remember to issue an “iisreset /noforce” command to complete the Web Application creation process.
    1. Open cmd and execute “iisreset/noforce”
    2. Click “Create Site Collection”
      SharePoint-create-site-collection
  6. On Title and Description option, give your Site a Title, Description(if so desired), on the Web Site Address option create a URL, and in the Template Selection option select “Team Site” (Team Sites are generally a place where team members can collaborate by publishing documents, but other features exist such as Team Calendars, surveys, links etc).
    SharePoint-create-site-collection-2
  7. On Primary and Secondary Site Collection Administrator option set an user. And click “Ok” to finish.
    SharePoint-create-site-collection-3
  8. Team site has now been created.
    SharePoint-create-site-collection-finish

Related links

Tags: BizTalk 2010 | Installation | Configuration

Comments
  1. Michael Jang says:

    Sandro,

    Great job in detailing the step by step instructions with screen shots.
    For those who may be interested to know the decision factors of WSS 3.0 and SharePoint Foundation 2010, other than the considerations described in Installation Guide, my lesson-learned is to install SharePoint Foundation 2010 only if your environment has:
    - enough of horse power(CPU/free Disk space/RAM)
    - Domain user Account with certain privilege for configuring SharePoint Foundation 2010 service in Server Farm installation type.
    This is especially true if you are building a standalone sandbox, like VPC or VM Player, without connection to any domain. Per BizTalk 2010 Installation Guide, you “must” install Windows SharePoint Services as Server Farm type in order to specified particular SQL Server database. I assume that requirement applies to SharePoint Foundation 2010, though no word about it was mentioned in the installation guide. Without Domain Account, SharePoint Foundation Configuration wizard will complain about it and will not let you continue the configuration. I have tried different local user accounts, even administrator of local box, without luck. If someone know how to work around this, please kindly post the right direction here.
    - Michael

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s