Concurrency and Commerce Server 2006 Catalog/Inventory Biztalk Adapters
When using send ports with BizTalk 2006, every message that is sent from BizTalk to the send port will, by default, invoke a new instance of the send port’s adapter to handle an incoming message. For example, if three files are sent to the Commerce Server catalog adapter, three instances of the send adapter will be invoked to process all incoming files...each instantiated object will process one file. This means that all three files will be processed starting at the time they arrive, which could be at the same time or merely seconds apart. So what does this mean to the Commerce Server Biztalk Developer and why do I need to know this?
Well, for Commerce Server 2006, we do not support concurrent imports on the same system. Meaning, we do not support more than one catalog import at a time or more than one inventory import at a time. Although, we do support a concurrent catalog and inventory import (e.g. one catalog import can occur while an inventory import is in progress). So if you have a catalog or inventory adapter send port configured, you will need to prevent concurrent imports. As explained earlier, if two catalog import files are sent to the catalog/inventory send port, both files will be imported at the time they arrived at the send port. Thus, the catalog or inventory import will fail.
This is easy configuration setting to disable this behavior and thus insure that your inventory/catalog system will not encounter any concurrency failures. On the send port Advanced Transport Options, there is a checkbox labeled: "Ordered Delivery". Check this box. This will force the incoming files to be handled by the send port in the order that they arrived; thus, preventing concurrent imports.
I hope this helps and let me know if any of you have any questions about this!
-Alan
