The correlation of a document to its running XLANG schedule instance begins when the hub receives an invoice associated with a purchase order. At this point, BizTalk Server queries the invoice for the TransactionID (PO number) and looks up the associated XLANG schedule GUID in the CustomCorrelation database. The invoice document is passed to the Hub.skx schedule instance that matches the GUID, and the schedule continues running.
Similarly, when the supplier receives a payment from the hub, BizTalk Server queries the payment for the TransactionID (invoice number) and looks up the associated XLANG schedule GUID in the SupplierCustomCorrelation database. The payment document is passed to the Supplier.skx schedule instance that matches the GUID, and the schedule continues running.
Finally, when the hub receives the payment acknowledgement, BizTalk Server queries the acknowledgement for the TransactionID (PO number) and looks up the associated XLANG schedule GUID in the CustomCorrelation database. The payment acknowledgement is passed to the Hub.skx schedule instance that matches the GUID, and the schedule continues running.
Previous Next |