Fetching messaging properties from within a pipeline component

hi community, trying implement custom pipeline component fetches several context properties, used in logging scenario logging data stored in bam observation model in corresponding activities. there several properties not found in message context.

i following referenece chapter 14 pro bam in biztalk server 2009, section pipeline component implementation. there shown how fetch regular system properties interchangeid, messageid, etc, messaging properties portstarttime , portendtime straight message context.

my implementation biztalk server 2010 , there differences in naming of properties - in book messagetype property addressed bts.messagetype when issuing call msg.context.read() method, while in case works if have name of property without bts prefix. in addition there no values present properties portstarttime , portendtime. these essential implementation since tracking processing time main kpi. 

priviously have implemented using tpe, these properties available. sake of easier management , deployment have decided adopt pipeline component implementation approach time. without these 2 properties not of use. there has been major change in way properties being written/promoted in pipeline in biztalk server 2010 compared 2009, or article in book somehow misleading.

my question if there way still extract values of these properies in way within pipeline component?

thanks in advance!

imho there no change in way property promotion or property handling done post biztalk 2004.

while in orchestration, properties addresses using <namespace>.property format namespace shortened value , not xml ns field, in pipeline components need give property name, xml schema namespace. take example bts.messagetype you'll use while in orchestration or filters in pipeline components use "pinmsg.context.read("messagetype", <xml namespace>) " xml namespace pertaining messagetype http://schemas.microsoft.com/biztalk/2003/system-properties

to adapter related data such starttime or endtime need @ "messagetracking" namespace.

if not wish use tpe might encounter issues pertaining retrieving adaptertransmittime can set on message after transmission , may not retrievable through property context @ all. tpe uses event collector model gather such things , able populate bam.

regards.

BizTalk Server  >  BizTalk Server General