07-15-04 10:50 PM
Correlation functionality does not have to dependent on the transport, and
in fact it almost never is. All the correlation will be done in the
orchestration, you don't have to program (write code) but you do have to
edit XSD schemas and the orchestration. Also you should install the latest
documentation and SDK from
<http://www.microsoft.com/biztalk/do...efault_2004.asp> and
search for correlation.
See below some information on correlation that I sent previously to
somebody else on the newsgroup.
Correlation sets are used to match incoming messages with already existing
orchestration instances. First, let me explain the problem that the
correlation sets are resolving.
You have an orchestration that interacts with your partner. The flow of
data is like this:
- partner sends purchase order
- you send confirmation
- partner sends invoice
Let's assume that all this processing is done in one orchestration. Your
partner sends you 2 purchase orders, PO1 and PO2. These 2 purchase orders
will activate 2 orchestration instances that will send 2 confirmations back
to your partner, Conf1 and Conf2. Your partner replies back to you with one
invoice, let's say Invoice2. This invoice has to be received by one of the
orchestration instances already running, but the question is which of the 2
orchestration instances should receive this invoice? A human would know
that each of the messages contains information that allows him to group
these messages toghether. For instance, the purchase order has an
identification number and this identification number is also included in
the confirmation and in the invoice as well. So all you need is a mechanism
to tell BizTalk which document elements in the three messages are in fact
refering to the same data. You will use correlation sets to do that.
This is one of the ways you could do it. You would open the purchase order
and you would promote the PurchaseOrderID (right click and chose Quick
Promotion). This has defined a promoted property for this element and this
property has been mapped to the correct element in the document. Now you
open Confirmation, right click the element that contains the purchase order
id and you will select Show Promotions. In the dialog that shows up you
will map the, purchase order Id to the already existing promoted property
that you have defined at the first step. Repeat this second step for
invoice document as well.
Now, the purchase order id information is promoted (from all messages) into
a property callled PurchaseOrderID. You can create a correlation set and
include this promoted property into the correlation set.
--------------------[vbcol=seagreen]
< df0a8d5120ebaf87976f5ab052e67687@localho
st.talkaboutsoftware.com>[vbcol=seagreen]
cpmsftngxa06.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08
.phx.gbl!newsfeed00.sul.t-online.de!t-online.de!news-spur1.maxwell.syr.edu!n
ews.maxwell.syr.edu!sn-xit-03!sn-xit-06!sn-post-02!sn-post-01!supernews.com!
corp.supernews.com!not-for-mail[vbcol=seagreen]
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
[ Post a follow-up to this message ]
| 
