About BizTalk Server

BizTalk Server provides a gateway for sending business documents between your company and your trading partners (also known as vendors). For example, if your company uses BizTalk Server, you can trade catalogs, orders, documents, and other electronic forms with your trading partners. BizTalk Server manages the data translation, encryption, digital signatures, and document tracking services for many different transport mechanisms.

You can use BizTalk Server and Commerce Server together to process orders that users place on your Commerce Server Web site. For example, assume you are selling computer hardware on your site. Your company manufactures some of this hardware, and some of it is supplied to you by trading partners. Using BizTalk Server, you can create a trading agreement for each trading partner who supplies the hardware that you sell on your site. When a user visits your site and places an order for one of the products supplied by a trading partner, Commerce Server processes the order and sends it to BizTalk Server, and then BizTalk Server sends the order to the trading partner to be filled.

The Solution Sites for Microsoft Commerce Server are designed to integrate with Microsoft BizTalk Server in the following two ways:

• Import/export of product catalogs
• Multi-vendor order form processing

BizTalk Server integration is configured by using Commerce Server Manager. These configuration settings are used to conditionally execute code within the Solution Sites that implements the integration with BizTalk Server.

If you are integrating Commerce Server and BizTalk Server for developmental purposes, install Commerce Server and BizTalk Server on the same computer. However, if you are integrating Commerce Server and BizTalk Server for production, it is recommended that you install BizTalk Server on a separate computer. For detailed deployment information about integrating Commerce Server and BizTalk Server, see Commerce Server Solution Sites.

If you are running Commerce Server and BizTalk Server on the same computer, you must run BizTalk Server setup on the Commerce Server computer to install the BizTalk tools. For information about installing the BizTalk Server tools, see BizTalk Server Help.

The Commerce Server 2002 International Retail site package contains a Commerce Server business-to-consumer sample site that can send orders to the included sample business-to-business Web service by using BizTalk Server. For detailed deployment information, see the file <%systemdrive%>\Program Files\Microsoft Commerce Server 2002\SDK\Samples\ASPNET\Retail2002\Retail2002_BizTalk Deployment.doc. This file is also available in the <%systemdrive%>\Inetpub\wwwroot\Retail2002B2B folder after the site has been unpacked.

Important

• We recommend that you do not develop a production-quality site based on the Retail2002 Site. We recommend that you use the Commerce Server 2002 Starter Site to develop a production quality site. You can download the Starter Site from https://go.microsoft.com/fwlink/?linkid=37800.

Catalogs for Multiple Vendors

Vendor ID

Using BizTalk Server to Exchange Catalogs

Sending Orders to BizTalk Server

Processing Received Orders

Catalogs for Multiple Vendors

Before you can use BizTalk Server to transmit orders to your trading partners, you must first organize the catalogs of those trading partners whose products will appear on your site. Each of your trading partners can send you one or more catalogs of their products. Depending on how you set up your site, you can present these catalogs on your Web site as one catalog, or as multiple catalogs. Maintaining multiple catalogs is helpful when, for example, you are targeting several groups of users with different catalog content, such as senior operations management and hobbyists.

Vendors send you their catalogs by using e-mail or BizTalk Server, and then you import the catalog to your Commerce Server Catalogs database by using the Catalog Editor module in Commerce Server Business Desk. For information about importing catalogs, see Importing an XML Catalog File and Importing a CSV Catalog File.

Vendor ID

When you set up an agreement with a vendor, the vendor ID is automatically made available to Commerce Server. The vendor ID is the organization name that you specify for the vendor when you create a destination organization for the source server. For more information, see Creating Source and Destination Organizations on the Source Server.

Commerce Server displays the vendor ID in Business Desk. It displays those trading partners (organizations) that support the same document type as your organization, and thus have compatible document routing. You can then use Business Desk to associate the vendor ID with the catalog.

More than one catalog can be associated with a given vendor. You can also specify a vendor at the product level; however, if you do this you must also customize the _additem.asp page (if you are developing with the Retail Solution Site).

If you name a vendor "Default," Commerce Server recognizes your own site as the vendor. For instructions about adding the vendor ID to a catalog, see Setting Up Your Catalogs for BizTalk Server.

Notes

• When a user orders an item from your Web site, the item must exist in the catalog of the destination organization. If the destination organization does not have the item in its catalog, BizTalk Server will not be able to process the purchase order on the destination server. It will write an error message to the event log on the destination server.
• Commerce Server Solution Sites are available at https://go.microsoft.com/fwlink/?linkid=6491.

Using BizTalk Server to Exchange Catalogs

Using BizTalk Server, you can exchange catalogs that are used by Commerce Server with your trading partners. After a catalog is converted to an Extensible Markup Language (XML) document, it is processed by BizTalk Server to save the XML catalog file in a shared folder on the destination computer on which Commerce Server is installed.

After an XML catalog file is saved on the destination computer, you use Business Desk to import the catalog from the shared folder on the destination computer and then publish the catalog to the Web site. You can edit the newly imported catalog, if necessary, by using the Catalog Editor module in Business Desk to make any changes. For information about importing a catalog by using Business Desk, see Importing an XML Catalog File and Importing a CSV Catalog File.

You can set up BizTalk Server to automatically incorporate an incoming catalog to Commerce Server. For information about automating this process by using a BizTalk Server Application Integration Component (AIC), see BizTalk Server Help.

The following figure shows how an XML catalog file is processed.

Sending Orders to BizTalk Server

The following figure shows how Commerce Server processes an order and then sends it to BizTalk Server.

Users perform the following steps to create and process an order:

1. Users add items to their baskets.

   Commerce Server reads the Commerce Server database and retrieves the vendor name for the products.

2. Users proceed to checkout, and the Commerce Server Checkout pipeline processes the order.

   For each line item (product) in the order, the Splitter component indicates whether that product is supplied by your company or by a vendor with whom you have a trading agreement. The Splitter component creates a list of the vendors, and attaches it to the order form.

3. Commerce Server determines whether the BizTalk Options property (in the App Default Config resource) is set to 1.

   If the BizTalk Options property is set to 1, Commerce Server reads the list of vendors and bundles the line items for each vendor.

4. Commerce Server converts the order form into one or more XML documents to be sent to BizTalk Server.

   When Commerce Server converts the order form (using the XMLTransforms process), it creates one XML document for each vendor.

   To convert the order, Commerce Server uses the schema called POSchema.xml, which is associated with the site. If you add one or more fields to the order form, by default Commerce Server does not include the new fields in the XML document that is sent to BizTalk Server. To add the new fields on the order form, you must edit POSchema.xml, an XDR (XML Data-Reduced) format file, and re-associate the XML file with the document in BizTalk Server. You must also transfer the XML file to BizTalk Server and re-associate it. You can edit POSchema.xml by using BizTalk Editor.

5. Commerce Server sends the XML documents to BizTalk Server.

Processing Received Orders

You can submit orders to BizTalk Server in several different ways, depending on your needs. You can use mapping to submit orders, you can use a variety of protocols to submit orders, or your trading partner can create a Commerce Server site or a non-Commerce Server site to receive the submitted orders.

If you choose to have your trading partner set up a Commerce Server site to receive orders, you can set up the site by using the _recvpo.asp page that receives XML documents from BizTalk Server. When an XML document is received by _recvpo.asp, the XMLTransforms process is started and converts the XML document back to an order form. Commerce Server then runs a pipeline on the order form. After the pipeline processes the order form, the order is saved to the Commerce Server database. By using _recvpo.asp, you can use Commerce Server objects to redirect the XML to your order management system.

The following figure shows how an XML document is sent from your BizTalk Server installation and processed by the Commerce Server site of the vendor.

You can also set up Commerce Server to process and send order forms to a queue, and then set up either your BizTalk Server (or the BizTalk Server at the vendor installation) to poll the queue. If you use this configuration, you can install BizTalk Server and Commerce Server on separate servers. The following figure shows this configuration.

See Also

Integrating with BizTalk Server

Programmer's Reference

Splitter

Copyright © 2005 Microsoft Corporation.
All rights reserved.