submissionGUID equivalent in 06

Hi,

I'm trying to figureout if there is something equivalent to the submissionGUID and some of the other transport dictionary values that were available in in 02 in custom components. These values equate to keys in the DTA tables when a message moves through the work queue. The submissionGUID was particularly handy when doing a submit synch call as the guid was retrurned to the caller application effectively giving the calling application a pointer to the record in BT 02 tables

In 02, custom COM+ components that implemented the IPipelineComponent interface would get a transport object which was just a dictionary object of these key values regarding the incoming message. We used those quite heavily to extend the BT02 DTA interchange tables for our own tracking and processing purposes. I see some parallels between this and the context properties that we get in 06 but am curious if anyone knows of the equivalents in 06 context properties for these 02 transport keys and the associated database tables

submission_id

in_interchange_key -

in_doc_key

tracking_id

Thanks

[1139 byte] By [mitre] at [2008-2-23]
# 1

Here is the list of system context properties that comes as part of each message

http://msdn2.microsoft.com/en-us/library/ms966048.aspx

I guess for "submissionGUID" equivalent in 2004 and above will be "BTS.MessageID" context property. (OR)

"LEGACY.SubmissionHandle" context property.

There is BTS.InterchangeID, its mainly used in an interchange scenario, where one message splits into "n" number of messages, to associate them together you can use InterchangeID.

There are some context properties associated with message tracking example MessageTracking.MessageIdentity

You need to play with it, and see which properties suits your requirement.

Regards,
Saravana Kumar
http://www.biztalk247.com/v1/
http://www.digitaldeposit.net/blog
[Please mark the response as "Answer" if it solves your problem.]

Saravana_Kumar at 2007-9-26 > top of Msdn Tech,BizTalk Server,BizTalk R2 General...
# 2
Mitre,

Chase up promoted properties - these solve alot of those challenges we had in '02.

As far as which Id's to use - check out the link that Savandara posted.

Due to promoted properties and the flexible nature of them, we're now not limited to ID's for our correlation.

MickBadran-MVP at 2007-9-26 > top of Msdn Tech,BizTalk Server,BizTalk R2 General...