Installing BizTalk Server 2004 sometimes entails installing Windows Sharepoint Services, specifically if you want to use Business Activity Services (Trading Party Mgmt, BAM portal, etc..). However, I see more and more folks configuring it improperly, hence the BizTalk Server installation fails when trying to install our BAS site or updating the infopath templates.
The product group is pretty good about updating the Installation Guide for BizTalk Server 2004. In fact, you can find the latest published guide (February 05) at http://www.microsoft.com/technet/prodtechnol/biztalk/biztalk2004/deploy/install_guide.mspx.
In the guide it reads:
To configure Windows SharePoint Services
- If it is not already open, open SharePoint Central Administration. On the Start menu, point to Programs, point to Administrative Tools and then click SharePoint Central Administration.
- On the SharePoint Central Administration page, under Server Configuration, select Configure virtual server for central administration.
- On the Configure Administrative Virtual Server page, select Use an existing application pool if one already exists. If this is your first Windows SharePoint Services configuration, select Create a new application pool. Enter an application pool name. For example, SpsAdminAppPool.
- Select a Configurable security account and use a local administrator. Click OK. You will be prompted to restart IIS at this point. Click OK.
- After IIS restarts, open SharePoint Central Administration. On the SharePoint Central Administration page, under Server Configuration, select Set configuration database server.
- On the Set Configuration Database Server page, enter values for Database server name and SQL Server database name. Next, specify your database connection type. Click OK.
- On the SharePoint Central Administration page, under Virtual Server Configuration, select Extend or upgrade virtual server. The Windows SharePoint Services Virtual Server List page appears.
- On the Windows SharePoint Services Virtual Server List page, if there are no servers in the list, click the Go to the complete list link. The complete list appears.
- Select the server you want to extend.
- Click Extend and create a content database.
- On the Extend and Create Content Database page, under Application Pool enter an Application pool name. For example, SpsWebSiteAppPool.
- Select a Configurable security account and use a local administrator.
- Click OK.
By default, Windows SharePoint Services includes the root of the IIS default Web site as a managed path. To create a virtual directory on a Windows SharePoint Services-extended virtual server for your own use (for example, for a BizTalk Server receive location or for a Web service application), you must exclude the URL for your virtual directory from the Windows SharePoint Services managed paths. Alternatively, if you have not configured a top-level Windows SharePoint Services site on the root of the IIS Web site, you may remove the root as a managed path.
To configure Managed Paths in Windows SharePoint Services
- If it is not already open, open SharePoint Central Administration. On the Start menu, point to Programs, point to Administrative Tools and then click SharePoint Central Administration.
- Click the Configure virtual server settings link.
- Click on the server that you extended.
- Under Virtual Server Management, click on Define managed paths.
- Under Included Paths select the (root) checkbox and click the Remove selected paths link.
- Click the Windows SharePoint Services link to return to the SharePoint Central Administration site.
For information about how to configure managed paths from the command line, see the topic “Managing Paths” in Microsoft Windows SharePoint Services Administrator’s Guide at http://go.microsoft.com/fwlink/?LinkId=18110.
So, you can see, there’s a few things you have to do to configure it properly. In the past, I’ve taken all this and just put it in a batch file to simplify the process. You’ll find the text of the batch file below. I literally just run this instead of running the setup independently and doing all the configuration manually. I avoid common mistakes this way.
You’ll see I declare some variables at the top of the batch file. These set the path of the WSS installation executable, the server and port which WSS is being installed on, the user id, password and email address that the WSS service will run under (make sure they are members of the local IIS_WPG group), the database server in which to create the content and configuration database, ports and the name of the configuration database to create.
Next, I basically execute the following steps:
1. Install WSS using the remote Sql option
2. Remove front page extensions from the web site I’m installing WSS on
3. Configure the WSS admin site and the application pool for it, including the credentials it runs under
4. Create the WSS configuration database
5. Extend the virtual server on the default site and set credentials
6. Lastly, I delete the root as a managed path under WSS.
Cheers!
@SET WSSEXE = C:\WUTemp\Platform\WSSV2\STS2Setup_1033
@SET WSSSERVER = bts04dev01:80
@SET WSSUSERID = waz-msft\WSSAdminSvc
@SET WSSPWD = pass@word1
@SET WSSEMAIL = WSSAdminSvc@waz.msft.com
@SET DBSERVER = BTS2004sql01
@SET FPPORT = 80
@SET ADMINPORT = 8080
@SET WSSCONFIGDB = WSSConfig
%WSSEXE%\SETUPSTS.EXE remotesql=yes /qb
“c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\50\BIN\owsadm.exe” -o fulluninstall -p %FPPORT%
“c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\BIN\stsadm” -o setadminport -p %ADMINPORT% -admapcreatenew -admapidname adminvs -admapidtype configurableid -admapidlogin %WSSUSERID% -admapidpwd %WSSPWD%
“c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\BIN\stsadm” -o setconfigdb -ds %DBSERVER% -dn %WSSCONFIGDB%
“c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\BIN\stsadm” -o extendvs -url http://%WSSSERVER% -ownerlogin %WSSUSERID% -owneremail %WSSEMAIL% -apcreatenew -apidname defaultvs -apidtype configurableid -apidlogin %WSSUSERID% -apidpwd %WSSPWD%
“c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\BIN\stsadm” -o deletepath -url http://%WSSSERVER%