Click Start, point to All Programs, point to Administrative Tools, click Computer Management, and then make sure that the BizTalk service account running SharePoint Adapter is a member of the local SharePoint Enabled Hosts Windows group on the server. For this walkthrough, use the same BizTalk service account for all of the services. For more information about Windows SharePoint Services Adapter, see What Is the Windows SharePoint Services Adapter?

In the Computer Management console, make sure that the HWS Web Service user is member of the local IIS_WPG and STS_WPG windows groups. For this walkthrough, use the same BizTalk service account for all of the services.

Exclude the (root) of the Default Web Site from Windows SharePoint Services Managed Paths as follows: Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Central Administration.

1. Under Virtual Server Configuration, select Configure virtual server settings.
   
   
2. On the Virtual Server List page, click Default Web Site.
   
   
3. On the Virtual Server Settings page, click Define managed paths.
   
   
4. In the Included Paths section of the Defined Managed Path page, select Root and then click Remove selected paths.
   
   
5. At a command prompt, perform an IISReset.
   
   

In the Computer Management console, add the BizTalk service account to the local BizTalk BAS Web Services Group, BizTalk BAS Administrators, BizTalk BAS Managers, BizTalk BAS Users groups, and local Administrators group.

At a command prompt, change the directory to the %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\60\BIN, type the following command, and then press ENTER.

• stsadm.exe -o upgrade -forceupgrade -url http://localhost
  
  

Note
Windows SharePoint Services 2.0 is not compatible with the ASP.NET 2.0 event validation capability. When you configure a Windows SharePoint Services-extended Web application on a server that has ASP.NET 2.0 installed, you must turn off ASP.NET 2.0 event validation.

Log off the computer, and then log on to the computer as the BizTalk service account.

At a command prompt, type the following command, and then press ENTER to set the %BTSSolutionsPath% environment variable to indicate the base folder for the E2E solutions. Then, exit the command prompt.

• setx BTSSolutionsPath "%ProgramFiles%\Microsoft BizTalk Server 2006\SDK\Scenarios"
  
  

  Note
  If you are using a 64-bit computer, use %ProgramFiles(x86)% instead of %ProgramFiles%.

  Note
  For more information about the SETX command, see the Microsoft TechNet Web site at http://go.microsoft.com/fwlink/?LinkId=67831.

Click Start, point to All Programs, point to Microsoft SQL Server, and then click Query Analyzer.

1. On the Connect to SQL Server dialog box, type <Your Computer Name> in the SQL Server text box, select Windows authentication, and then click OK.
   
   
2. Open the Contact.SQL in the %BTSSolutionsPath%\B2B\TPM\SQL folder, and then run the SQL query against the BizTalkMgmtDB database. The script adds three more columns (UserName, Password, keyindex) to the ContactObject table.
   
   

Note
The BizTalk Management database (BizTalkMgmtDB) contains trading partner information.

Note
The next steps use the Profiles Schema Manager snap-in to add additional fields to Trading Partner Management (TPM) customer definition. This walkthrough specifically adds UserName, Password, and keyindex fields. It shows how to maintain one partner definition that supports two channels (B2B and B2C) for taking orders.

Click Start, click Run, type MMC.exe, and then press ENTER.

Note
If you are using a 64-bit computer, run “MMC.exe /32” instead of “MMC.exe”.

1. In the Microsoft Management Console, add the Profiles Schema Manager snap-in.
   
   
   
   
   
   
2. Expand Profiles, right-click Profiles, select Properties, click Edit and then set your SQL connection properties to point to your BizTalkMgmtDB database. Then close Data Link Properties and Profile Properties dialog boxes.
   
   
   
   
   
   
3. Right-click Profiles, click Import Profile Schema, select TPMUserSchemaNotEncrypted.xml file in the %BTSSolutionsPath%\B2B\TPM\TPMSchema folder, and then click OK.
   
   
   
   
   
   
4. On the Profile Schema Import dialog box, expand SQL Source, select SQLSource_Partion1, and then click Edit.
   
   
   
   
   
   
5. On the Data Link Properties dialog box, click Providers, select OLEDB Provider used is for SQL Server.
   
   
   
   
   
   
6. On the Data Link Properties dialog box, click Connection, select <Your Computer Name> in the Select or enter a server name box, select Use Windows NT Integrated security, select BizTalkMgmtDB in the Select the database on the server box, and then click OK.
   
   
   
   
   
   
7. On the Profile Schema Import dialog box, click Import to import the extended profile schema, and then click Yes on the confirmation dialog box.
   
   
8. Expand Profile Catalog, expand Data Sources, expand SQLSource, expand Data Objects to review the extend schemas.
   
   

Click Start, point to All Programs, point to Microsoft BizTalk Server 2006, and then click Business Activity Services Site.

1. On the Home page, click Documents and Lists, and then click Templates on the Documents and Lists page.
   
   
2. On the Templates page, click Upload Document, and then upload the PartnerProfileAdmin.xsn in the %BTSSolutionsPath%\B2B\TPM\InfoPathform folder.
   
   
3. Repeat the same steps with the PartnerProfileAdmin.xsn for uploading PartnerProfileSelf.xsn and PartnerProfileStandard.xsn in the %BTSSolutionsPath%\B2B\TPM\InfoPathform folder.
   
   

At a command prompt change the directory to the %BTSSolutionsPath%\B2B\TPM\Schemas folder, copy the Partner.xsd and PartnerNoWsdl.xsd files to the <BizTalk Install Directory>\Business Activity Services\TPM\Schemas folder.

Note
We recommend backing up the Partner.xsd and PartnerNoWsdl.xsd in the <BizTalk Install Directory>\Business Activity Services\TPM\Schemas folder before overwriting them.

Click Start, click Run, type MMC.exe, and then press ENTER.

In the Microsoft Management Console, add the Certificates snap-in for My user account.

Note
To manage the certificates for My user account of the BizTalk service account, you must log on to the computer as the BizTalk service account. If the account is not the same, the BizTalk Server host will fail to retrieve the certificate from the certificate store and will not be able to process and decode the signed messages.

1. In the Certificates snap-in, expand Certificates -Current User, right-click Personal, point to All Tasks, and then click Import.
   
   
   
   
   
   
2. Using the Certificate Import Wizard, import the myserver.pfx in the %BTSSolutionsPath%\B2B\TPM\Certificate folder. Accept all of the default values including Password.
   
   

   Note
   The default Password is blank.

3. In the Certificates snap-in, expand Certificates - Current User, right-click Trusted Root Certificate Authorities, point to All Tasks, and then click Import.
   
   
   
   
   
   
4. Using the Certificate Import Wizard, import the myserver.pfx in the %BTSSolutionsPath%\B2B\TPM\Certificate folder. Accept all of the default values including Password.
   
   

In the Microsoft Management Console, add the Certificates snap-in for Computer account of Local computer.

Note
To manage the certificates for Computer account, the user account which you log on as must be a member of local Administrators group of the computer.

1. In the Certificates snap-in, expand Certificates (Local Computer), right-click Other People, point to All Tasks, and then click Import.
   
   
   
   
   
   
2. Using the Certificate Import Wizard, import the myserver.pfx in the %BTSSolutionsPath%\B2B\TPM\Certificate folder. Accept all of the default values including Password.
   
   

Click Start, point to All Programs, point to Microsoft BizTalk Server 2006, and then click BizTalk Server Administration.

1. Right-click BizTalk Group, and then click Properties.
   
   
2. On the Group Properties dialog box, click Certificate, click Browse.
   
   
3. On the Select Certificate dialog box, select the certificate that you installed, and then close all of the dialog boxes.
   
   
   

Click Start, point to All Programs, point to Microsoft BizTalk Server 2006, and then click Business Activity Services Site.

On the Home page, click BizTalk Servers.

On the BizTalk Servers page, click Register BizTalk Server.

On the BizTalk Servers: New Item page, enter the registration information as the following table, and then click Refresh Host Lists.

Note
Outbox Receive Location Host list box shows the hosts configured as Windows SharePoint Services Adapter Receive Handler. Parameter Services shows the hosts configured as SOAP Adapter Send Handler.

On the BizTalk Servers: New Item page, select BizTalkServerApplication in the Outbox Receive Location Host and Parameter Services Host boxes, and then click Save and Close.

In the BizTalk Server Administration console, expand BizTalk Group, expand Platform Settings, and then expand Host Instances.

Right-click BizTalkServerApplication, and then click Stop.

Right-click BizTalkServerApplication again, and then click Delete.

Expand Hosts, right-click BizTalkServerApplication, and then click Properties. On the Host Properties page, select Authentication Trusted, click OK to close the dialog box.

Right-click BizTalkServerIsolatedHost, and then click Properties. On the Properties page, select Authentication Trusted, click OK to close the dialog box.

Note
Because the B2B solution uses the PartyReceive pipeline and the Party Resolution pipeline component, you must configure the host running the pipeline (BizTalkServerAppplication) as authentication trusted host.

Note
You cannot use the same user group for authentication trusted and non-trusted hosts. For this walkthrough, configure the both of In-Process and Isolated hosts as Authentication Trusted. In a real production scenario, you must use different user groups for trusted and non-trusted hosts.

Right-click Host Instances, point to New, and then click Host Instance. On the Host Instances Properties page, select BizTalkServerApplication in the Host name box, click Configure, enter user information for the BizTalk service, and then close all of the dialog boxes.

Click Start, point to All Programs, point to Microsoft Visual Studio 2005, point to Visual Studio Tools, and then click Visual Studio 2005 Command Prompt.

At the Visual Studio 2005 Command Prompt, change the directory to the %BTSSolutionsPath%\B2B\Utilities\bin\debug folder, and then run the following command to add Utilities component to the Global Assembly Cache (GAC).

gacutil.exe /i Microsoft.Samples.BizTalk.Litware.Utilities.dll

At a command prompt, change the directory to the %BTSSolutionsPath%\B2B\Scripts folder, type Locations.cmd, and then press ENTER. The command file creates the folders in the C drive for the adapters that the B2B solution will use.

In Windows Explorer, browse to the C:\Litware folder, and then make sure that the BizTalk service account has read/write permissions to the following folders:

• BrokerNew
  
  
• BrokerUpdate
  
  
• EDIIn
  
  
• EDIOut
  
  
• GetOrder
  
  
• GetProfile
  
  
• UpdateUserBASRL
  
  
• Vendor1
  
  
• Vendor2
  
  

In the BizTalk Server Administration console, expand BizTalk Group, expand Platform Settings, expand Adapters, and then click SMTP.

1. Right-click BizTalkServerApplication with Send direction, click Properties. On the Adapter Handler Properties dialog box, click Properties.
   
   
2. On the Transport Properties dialog box, type localhost in the SMTP server name text box, and then type administrator@<Your Domain Name> in the From text box. This enables users to receive email notification when messages are processed.
   
   
3. Close all of the dialog boxes.
   
   

In the BizTalk Server Administration console, expand BizTalk Group, expand Platform Settings, expand Host Instances, right-click BizTalkServerApplication, and then click Restart to reflect new settings.

In Windows Explorer, browse to the %BTSSolutionsPath%\B2B folder, and then open the Microsoft.Samples.BizTalk.Litware.sln with Microsoft Visual Studio 2005.

On the Solution Explorer, right-click Microsoft.Samples.BizTalk.Litware, and then click Deploy Solution.

In the Internet Information Services (IIS) Manager, expand Web Sites, right-click the Default Web Site, point to New, and then click Virtual Directory to run Virtual Directory Creation Wizard.

1. Using the Virtual Directory Creation Wizard, create the following virtual directory for the proxy Web service for the adapter version:
   
   Alias = TPMAccessWS
   
   PATH = <BizTalk Install Directory>\SDK\Scenarios\B2B\TPMAccessWS
   
   Access Permissions = Read, Run scripts
   
   
2. Expand the Default Web Site, right-click TPMAccessWS, click Properties. On the Properties dialog box, click the Virtual Directories tab, and then in the Application Pool box, select the same application pool that is used by the TPPubWS Web application.
   
   

In the Internet Information Services (IIS) Manager, right-click Default SMTP Virtual Server, and then click Properties.

1. On the Virtual Server Properties page, click Access, and then click Relay.
   
   
2. On the Relay Restriction page, click All except the list below.
   
   
3. Close all of the dialog boxes.
   
   

In the BizTalk Server Administration console, expand BizTalk Group, and then expand Applications.

1. Right-click BTSScn.B2B.Hub application, point to Import, click Bindings, select the PartyPorts.xml in the %BTSSolutionsPath%\B2B\Bindings folder, and then click OK.
   
   
   
   
   
   
2. Right-click BTSScn.B2B.Hub again and select Properties. In the Properties window click References then click Add. Check the checkbox beside BizTalk EDI Application to add a reference to the default EDI application. This will allow the BTSScn.B2B.Hub application to use artifacts deployed in the BizTalk EDI Application.
   
   
   
   
   

Click Start, point to All Programs, point to Microsoft SQL Server, and then click Query Analyzer.

1. On the Connect to SQL Server dialog box, type <Your Computer Name> in the SQL Server text box, select Windows authentication, and then click OK.
   
   
2. Open the Order.SQL in the %BTSSolutionsPath%\B2B\OrderSystem\SQL folder, and then run the SQL query. It creates a database to log the incoming orders.
   
   

Open a command prompt, and then change the directory to the %BTSSolutionsPath%\B2B\Scripts folder.

1. At the command prompt, open the LitWareSSOConfiguration.xml file using Notepad, and then review the contents of the file. This file defines the configuration store application in SSO that the scenario uses to keep configuration parameters. No changes to this file are necessary.
   
   
2. At the command prompt, open the CreateLitwareApplication.cmd file using Notepad, review and change the contents of the file. This command file saves the connection string for the OrderSystemDB into the SSO affiliated application. No changes to this file are necessary.
   
   
3. At the command prompt, type CreateLitwareApplication.cmd, and then press ENTER.
   
   

In Windows Explorer, browse to the %BTSSolutionsPath%\B2B\TPM\PartnerData folder, and then open MyProfile.xml with Microsoft InfoPath 2003.

For this walkthrough, use the local TPM Web services. If the TPM Web services are running on the remote computers, you must change the following nodes in the MyProfile.xml with Notepad to point to the correct Web service URL.

<?ms-tpm url=http://localhost/TPPubWS/TPPubWS.asmx?>
<?ms-tpmgmtws url=http://localhost/TPMgmtWS/TPMgmtWS.asmx?>

On the toolbar, click Contacts, and then type <Your Email Address> in the E-mail address text box.

On the toolbar, click Submit Profile.

In Windows Explorer, browse to the %BTSSolutionsPath%\B2B\TPM\PartnerData folder, and then open TestPartnerExtended.xml with Microsoft InfoPath 2003.

Note
If the TPM Web services are running on the remote computers, you must change the TestPartnerExtended.xml with Notepad to point to the correct Web Service URL.

1. On the toolbar, click Contacts, and then type <Your Email Address> in the E-mail address text box.
   
   
2. On the toolbar, click Submit Profile.
   
   

Click Start, point to All Programs, point to Microsoft BizTalk Server 2006, and then click Business Activity Services Site.

1. On the Home page, click Partner Profiles.
   
   
2. On the Partner Profiles page, click TestPartner that you submitted with the TestPartnerExtended.xml, and then click Deploy Partner.
   
   
3. On the Deploy Partner page, select the registration name that you created in the step "To register BizTalk Server on the BAS site", and then click Deploy.
   
   
   
   
   
   

Repeat the same steps as the TestPartnerExtended.xml for submitting and deploying the TestPartner2Extended.xml the %BTSSolutionsPath%\B2B\TPM\PartnerData folder.

In the BizTalk Server Administration console, expand BizTalk Group, and then expand Applications.

1. Right-click BTSScn.B2B.Hub application, point to Import, click Bindings, select the OtherPorts.xml in the %BTSSolutionsPath%\B2B\Bindings folder, and then click OK.
   
   
2. Right-click BTSScn.B2B.Hub application, point to Import, click Bindings, select the BindingOrderSystem.xml in the %BTSSolutionsPath%\B2B\Bindings folder, and then click OK.
   
   
3. Right-click BTSScn.B2B.Hub application, point to Import, click Bindings, select the BindingOrchestration.xml in the %BTSSolutionsPath%\B2B\Bindings folder, and then click OK.
   
   

In the Internet Information Services (IIS) Manager, expand the Web Sites, expand the Default Web Site, right-click HWSMessages, and then click Properties.

On the Properties page, click Directory Security tab, and then click Edit to modify Authentication and access control. Select Enable anonymous access. Close all of the dialog boxes.

At a command prompt, perform an IISRESET.

In the BizTalk Server Administration console, expand BizTalk Group, expand Platform Settings, expand Host Instances, right-click BizTalkServerApplication, and then click Restart to reflect new settings.

In the BizTalk Server Administration console, expand BizTalk Group, expand Applications, expand BTSScn.B2B.HUB, expand Send Ports, right-click SendToOrderSystem_HTTP, click Properties, and then click Configure on the Properties dialog box.

1. On the Transport Properties dialog box, click General tab, and then make sure that Enable chunk encoding is not selected.
   
   
2. On the Transport Properties dialog box, click Authentication tab, and then make sure that Kerberos is selected in the Authentication type box.
   
   
3. Close all of the dialog boxes.
   
   

In Windows Explorer, browse to the %BTSSolutionsPath%\B2B\TPM\PartnerData folder, and then open Agreement.xml with Microsoft InfoPath 2003.

Note
If the TPM Web services are running on the remote computers, you must change the Agreement.xml with Notepad to point to the correct Web Service URL.

On the toolbar, click Submit Agreement. It creates new agreement between the TestPartner and MyProfile.

Click Start, point to All Programs, point to Microsoft BizTalk Server 2006, and then click Business Activity Services Site.

1. On the Home page, click Agreements.
   
   
2. On the Agreements page, click Activate Agreement from the drop-down list for the TestPartner. It opens the agreement with Microsoft InfoPath 2003.
   
   
   
   
   
   
3. On the Activate Agreement page in Microsoft InfoPath 2003, select VendorA_FILE for all seven Operation Ports boxes, and then click Submit Mapping.
   
   
   
   
   
   

In Windows Explorer, browse to the %BTSSolutionsPath%\B2B\TPM\PartnerData folder, and then open Agreement2.xml with Microsoft InfoPath 2003.

Note
If the TPM Web services are running on the remote computers, you must change the Agreement2.xml with Notepad to point to the correct Web Service URL.

On the toolbar, click Submit Agreement. It creates new agreement between the TestPartner2 and MyProfile.

Click Start, point to All Programs, point to Microsoft BizTalk Server 2006, and then click Business Activity Services Site.

1. On the Home page, click Agreements.
   
   
2. On the Agreements page, click Activate Agreement from the drop-down list for the TestPartner2. It opens the agreement with Microsoft InfoPath 2003.
   
   
3. On the Activate Agreement page in Microsoft InfoPath 2003, select VendorB_FILE for all seven Operation Ports boxes, and then click Submit Mapping.
   
   
   
   
   
   

Run the Business-to-Business Solution. For more information about running the solution, see How to Run the Business-to-Business Solution.