As per monday October 7th Microsoft released BizTalk Server 2006 CTM. This release is only available for users with a MSDN or TechNet account. The CTM release of BizTalk Server 2006 is fully compatible with Visual Studio 2005 and SQL Server 2005. I just can smell the RTM version coming very soon.
Monthly Archives: November 2005
Access message properties inside custom pipeline component
Just recently I was looking for some default message properties and how to read and write them inside a custom pipeline component. While searching I stumbled over a great post listing all the default message properties and how to read them.
If you want to access the properties in your custom pipeline component, you have to get the IBaseMessageContext object from the IBaseContext and use the Read method to get a value or the Write method to substitute a value with your own.
For example:
public IBaseMessage Execute(IPipelineContext pContext, IBaseMessage pInMsg)
{
IBaseMessageContext context = pInMsg.Context;
string value = context.Read(property, namespace).ToString();
context.Write(property, namespace, value);
}
To make your life a little easier, here’s the full list of properties:
Receive pipeline properties:
| Property | Namespace | |
1 | ReceivedFileName | http://schemas.microsoft.com/BizTalk/2003/file-properties |
2 | InboundTransportLocation | http://schemas.microsoft.com/BizTalk/2003/system-properties |
3 | InterchangeID | http://schemas.microsoft.com/BizTalk/2003/system-properties |
4 | ReceivePortID | http://schemas.microsoft.com/BizTalk/2003/system-properties |
5 | ReceivePortName | http://schemas.microsoft.com/BizTalk/2003/system-properties |
6 | WasSolicitResponse | http://schemas.microsoft.com/BizTalk/2003/system-properties |
7 | AuthenticationRequiredOnReceivePort | http://schemas.microsoft.com/BizTalk/2003/system-properties |
8 | InboundTransportType | http://schemas.microsoft.com/BizTalk/2003/system-properties |
9 | LRPMsgBodyTracking | http://schemas.microsoft.com/BizTalk/2003/system-properties |
10 | MessageExchangePattern | http://schemas.microsoft.com/BizTalk/2003/system-properties |
11 | PortName | http://schemas.microsoft.com/BizTalk/2003/messagetracking-properties |
12 | ReceivePipelineID | http://schemas.microsoft.com/BizTalk/2003/system-properties |
13 | MessageType | http://schemas.microsoft.com/BizTalk/2003/system-properties |
14 | SchemaStrongName | http://schemas.microsoft.com/BizTalk/2003/system-properties |
Send pipeling properties:
| Property | Namespace | |
1 | CopyMode | http://schemas.microsoft.com/BizTalk/2003/file-properties |
2 | LTPMsgBodyTracking | http://schemas.microsoft.com/BizTalk/2003/system-properties |
3 | ReceivedFileName | http://schemas.microsoft.com/BizTalk/2003/file-properties |
4 | SPID | http://schemas.microsoft.com/BizTalk/2003/system-properties |
5 | ActualRetryCount | http://schemas.microsoft.com/BizTalk/2003/system-properties |
6 | FileName | http://schemas.microsoft.com/BizTalk/2003/file-properties |
7 | PartyName | http://schemas.microsoft.com/BizTalk/2003/messagetracking-properties |
8 | ReceivePortName | http://schemas.microsoft.com/BizTalk/2003/system-properties |
9 | WasSolicitResponse | http://schemas.microsoft.com/BizTalk/2003/system-properties |
10 | AllowCacheOnWrite | http://schemas.microsoft.com/BizTalk/2003/file-properties |
11 | RetryInterval | http://schemas.microsoft.com/BizTalk/2003/system-properties |
12 | OutboundTransportCLSID | http://schemas.microsoft.com/BizTalk/2003/system-properties |
13 | SPName | http://schemas.microsoft.com/BizTalk/2003/system-properties |
14 | InboundTransportLocation | http://schemas.microsoft.com/BizTalk/2003/system-properties |
15 | InterchangeID | http://schemas.microsoft.com/BizTalk/2003/system-properties |
16 | ReceivePortID | http://schemas.microsoft.com/BizTalk/2003/system-properties |
17 | SPTransportID | http://schemas.microsoft.com/BizTalk/2003/system-properties |
18 | TransmitPipelineID | http://schemas.microsoft.com/BizTalk/2003/system-properties |
19 | AuthenticationRequiredOnReceivePort | http://schemas.microsoft.com/BizTalk/2003/system-properties |
20 | InboundTransportType | http://schemas.microsoft.com/BizTalk/2003/system-properties |
21 | LRPMsgBodyTracking | http://schemas.microsoft.com/BizTalk/2003/system-properties |
22 | MessageExchangePattern | http://schemas.microsoft.com/BizTalk/2003/system-properties |
23 | OutboundTransportLocation | http://schemas.microsoft.com/BizTalk/2003/system-properties |
24 | PortName | http://schemas.microsoft.com/BizTalk/2003/messagetracking-properties |
25 | ReceivePipelineID | http://schemas.microsoft.com/BizTalk/2003/system-properties |
26 | SourcePartyID | http://schemas.microsoft.com/BizTalk/2003/system-properties |
27 | MessageType | http://schemas.microsoft.com/BizTalk/2003/system-properties |
28 | OutboundTransportType | http://schemas.microsoft.com/BizTalk/2003/system-properties |
29 | PartNames | http://schemas.microsoft.com/BizTalk/2003/messageagent-properties |
30 | RetryCount | http://schemas.microsoft.com/BizTalk/2003/system-properties |
31 | SchemaStrongName | http://schemas.microsoft.com/BizTalk/2003/system-properties |
BizTalk’s sexy new XSLT mapper
I’ve just watched a clip from Channel9 featuring Eddie Churchill. In the video he demonstrates a prototype of the future BizTalk mapper. The new mapper will contain some very impressive features as I must say. Some of them make the life of the mapper a lot easier, especially when dealing with large maps.
Some of the features which are shown in the video are:
- Different drawing densities for lines which are in view and which aren’t.
- Highlighting all lines coming from and going to a functoid when the functoid is selected.
- Automatic scrolling to elements when line or functoid is selected.
- Sibling coalesence, which folds unmapped elements so only the mapped elements are visible.
- Automapping or Intellimapping, which finds the best target or source element to map to based on a very intelligent algorithm.
- Scrollbar ticks, which identifies where in the document you can find things you’re interested in.
While watching the clip I could only thing of one thing: gimme gimme gimme!!! Unfortunately the new mapper will not be shipped with BizTalk 2006. When the mapper will be shipped is not yet known as this is just a prototype. It’s also highly possible that we see some features in other Microsoft Application before the mapper is even shipped.
I recommend that every BizTalk engineer who hasn’t seen the video yet will watch it right away. You can find the clip here: http://channel9.msdn.com/Showpost.aspx?postid=126990