| Author |
BTS.CorrelationToken
|
|
| Samuel L 2005-10-28, 5:03 pm |
| Hi!
I want to be able to use a correlation set for untyped messages (messages of
types like XmlDocument). Since the messages are untyped I cannot promote any
properties, so I will have to correlate on some other properties.
In the Correlation properties list I found the BTS.CorrelationToken, which
sounds quite relevant to me! =)
Well is BTS.CorrelationToken used by BizTalk for some internal correlation,
or is it free for me to use? Does anyone know this?
Thanks for your help!
| |
| Danny Buysse 2005-10-28, 5:03 pm |
| This property is implicit used by the Messagebox engine to be able to
correlate messages in a request/response scenario.
Although you could use it, it is probably not supported.
Don't know about your exact situation but you could use one of the system
properties to correlate on e.g. BTS.ReceivedFileName
Danny.
"Samuel L" wrote:
> Hi!
>
> I want to be able to use a correlation set for untyped messages (messages of
> types like XmlDocument). Since the messages are untyped I cannot promote any
> properties, so I will have to correlate on some other properties.
>
> In the Correlation properties list I found the BTS.CorrelationToken, which
> sounds quite relevant to me! =)
>
> Well is BTS.CorrelationToken used by BizTalk for some internal correlation,
> or is it free for me to use? Does anyone know this?
>
> Thanks for your help!
>
| |
| Samuel L 2005-10-28, 5:03 pm |
| Thanks for your reply Danny!
The thing is that I want to perform my correlation independent of the port's
transport type. So properties like BTS.REceivedFileName would probably not be
such a good solution.
Are there any other strategies for this kind of correlations?
I have thought of using some kind of envelope which holds the correlation
properties, but I don't know if that's such a good idea?
What do you think?
Thanks!
| |
| Danny Buysse 2005-10-28, 5:03 pm |
| If you've got control over the party that is sending you the data this looks
a good solution. In fact this should be the solution you need to follow where
you've got a Header part containing your correlation key and a Body of type
<Any>, as such you can recieve anything but you've got always properties you
can use for correlation or tracking
"Samuel L" wrote:
> Thanks for your reply Danny!
>
> The thing is that I want to perform my correlation independent of the port's
> transport type. So properties like BTS.REceivedFileName would probably not be
> such a good solution.
>
> Are there any other strategies for this kind of correlations?
> I have thought of using some kind of envelope which holds the correlation
> properties, but I don't know if that's such a good idea?
>
> What do you think?
> Thanks!
>
| |
| Samuel L 2005-10-28, 5:03 pm |
| Thanks Danny!
But could you please explain a bit more?
Or maybe give an example structure of the message schema?
Thanks!
"Danny Buysse" wrote:
[vbcol=seagreen]
> If you've got control over the party that is sending you the data this looks
> a good solution. In fact this should be the solution you need to follow where
> you've got a Header part containing your correlation key and a Body of type
> <Any>, as such you can recieve anything but you've got always properties you
> can use for correlation or tracking
>
> "Samuel L" wrote:
>
|
|
|
|