Microsoft KB Archive/294275

= Issues with Interoperability Between Commerce Server and BizTalk Server =

Article ID: 294275

Article Last Modified on 10/22/2003

-

APPLIES TO


 * Microsoft Commerce Server 2002 Standard Edition
 * Microsoft Commerce Server 2000 Standard Edition

-



This article was previously published under Q294275



SYMPTOMS
The BizTalk Interchange Manager Database property in the App Default Config resource of a Commerce Server 2000 site has a description of &quot;The connection string of the BizTalk Interchange Manager Database, which stores messages sent from Commerce Server.&quot; This connection string is not used by Commerce Server to determine the location of the messaging database.



CAUSE
The catalogtovendorassociation object is used to return a list of vendors to Commerce Server. The catalogtovendorassociation object uses an encrypted connection string that is stored in the registry. To modify the connection string successfully, you must use the BizTalk server Administrator. For this reason, you must have BizTalk Server installed locally if you use the implementation that is demonstrated in the Commerce Server Solution Sites.

The current implementation demonstrated in the Commerce Server 2000 Solution Sites uses an IInterchange.Submit call. This implementation requires a license for the BizTalk Server on every CPU on the Commerce Server computer if you require integration with the BizTalk Server.

The BizTalk Server documentation includes a section titled &quot;Submit a Document from a Remote Client.&quot; The implementation in Solution Sites does not use this method, nor does Microsoft recommend that you use this method to submit order or catalog XML documents from Commerce Server 2000.

If you still want to use remote DCOM calls from the Commerce Server 2000 computer to the BizTalk Server computer by following the instructions in the &quot;Submit a Document from a Remote Client&quot; topic, then a separate BizTalk Server license is required for every Commerce Server 2000 CPU that performs this function.

If you do not want to install Microsoft Commerce Server on the same computer as the Microsoft BizTalk Server installation, then Microsoft recommends that you use Message Queuing to send messages between the two systems rather than DCOM calls to IInterchange.Submit. By using Message Queuing you loosely couple the two systems, which leads to increased availability of the overall solution.

The Sample Solution Sites that is provided with Commerce Server 2000 are not designed to work in a two computer configuration and currently use COM Interchange.Submit calls. Microsoft is currently creating a white paper that will explain how to resolve this issue by using Message Queues to route orders from a Commerce Server 2000 computer to a BizTalk Server computer. In the case of sending catalogs, MSMQ is not recommended because the size of the catalog often exceeds the 4 MB size limit of an MSMQ message. In the event that catalogs need to be sent by using BizTalk, then send them to a shared file system rather than a message queue.



STATUS
Because this connection string was not used by Commerce Server to connect to a remote BizTalk Server, the connection string has been removed in Commerce Server 2000 Service Pack 1 (SP1).

For additional information about the Service Pack, click the article number below to view the article in the Microsoft Knowledge Base:

297216 INFO: How to Obtain the Latest Commerce Server 2000 Service Pack



MORE INFORMATION
The following information is from the Commerce Server 2002 product documentation:

For detailed BizTalk Server deployment instructions and information about integrating BizTalk Server with Commerce Server 2002 sites, 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.

Keywords: kbbug kbpending KB294275

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.