IProbeMessage interface in BizTalk.

If the pipeline component's execution mode is set as "First recognized" or "All recognized", Pipeline Manager iterate through all the components in the stage to find a component which has implemented IProbeMessage interface; then it executes that component leaving others in First recognized mode and executes all the components that recognise the format of the data in the All recognized mode. i.e. IProbeMessage interface enables the pipeline component to decide do they want to process the message or not.

In BizTalk pipeline, there is concept called Message Probing. This means pipeline component intercepts (probes) the message and determine the format of the message. Disassemble stage's message probing capability enables it receive different format of the message to be received from same endpoint, enables it to identify the format of the message that is being processed dynamically.

IProbeMessage interface contains a method Probe which returns true if the disassembler decides to process the message. Probe method read firs few bytes of the message data stream in order to decide whether it is capable of processing the message or not.

public interface IProbeMessage
{
bool Probe(IPipelineContext pContext, IBaseMessage pInMsg);
}

BizTalk in .NET 3.5 Framework

To find out, What's in .NET 3.5 framework for BizTalk.

http://blogs.breezetraining.com.au/mickb/2008/02/08/Feb27thSydneyBizTalkUserGroupALookAtTheNET35Framework.aspx

Adapter version details under host process domain.

Our production support guys came up with an interesting requirement, How to find the version of the custom BizTalk adapter assembly being executed under particular host. This has to be achieved without disturbing the production servers.

The answer is pretty simple, use the Process Explore (procexp.exe). One of the gems from SysInternal (Acquired by Microsoft). Process Explore doesn’t require installation, just works with the XCOPY of the procexp.exe as many of the SysInternals tools (satisfied our ChangeManagement since this doesn’t require any installation in the production server :) )

• Start it up…
• In the View menu, ensure that Show Lower Pane option is checked
• In the View\Lower Pane View submenu choose DLLs
• Highlight the relevant BTSNTSvc.exe process in the upper pane
• Locate your adapter’s runtime assembly and you can get the version details

Process Explore: http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

PS: Assemble name has been hidden for companies privacy. And Thanks for Chris Dickson in helping us.

Technorati Tags: BizTalk

Oslo, BizTalk Mapper & Surface – Fjord

I came across a very interesting initiative from Microsoft and thought of blog it. It is about Microsoft's Fjord.

Fjord is the code name for the Microsoft Surface integration pieces to the Modeling commitments of Oslo. BizTalk Mapper, a BizTalk component is the first piece of Oslo to be integrated with Surface.

As Oslo’s one of the key focus is going to be on Modeling, I am expecting the orchestration designer can also be integrated with the Microsoft’s surface(lets see). For expression or for the editor requirement, they may come up with Tablet-PC kind of the keyboard in Surface for Orchestration. More surprises and wonders can be expected as part of Oslo.

Fjord – The code name for BizTalk mapper’s integration with Surface. As fjord means a long, narrow bay with steep sides from the top region of the mountains to the sea, the source schema and destination schema on the two sides on the functoids in the BizTalk Map could have resembled as mountains in the two side of the sea. Aptly named.

And another interesting fact about the Microsoft’s Fjord and Mother Nature’s fjord is Norway has got many deep fjords. Again I donn know why Microsoft’s Oslo is more linked with Norway (Norway’s capital is Oslo).

Reference:

http://www.biztalkgurus.com/blogs/biztalksyn/archive/2007/11/29/project-fjord-biztalk-mapper-to-require-surface-in-oslo.aspx

Microsoft OSLO.

OSLO is a codename for the Microsoft’s technical strategy which would provide the platform and tools to make and manage the cross boundaries integrated enterprise applications easily. When they mean easier, they mean by

• Reducing the development code be 10xth portion and hence 10X increase in productivity.
• And by hosting the services online, integration and the maintenance of these applications could be made simpler.

(I donn why Microsoft code-named their technical strategy for their next version of SOA after Norway’s capital)

Oslo is a initiative from Microsoft’s CSD – Connected Systems Division., CSD is where service-oriented application platform components of Microsoft like BizTalk Server, WCF, WF, messaging and queuing products, and much of the identity and authorization services, such as Windows CardSpace are created.

Microsoft has targeted to print its footprint on SOA by heavily investing in the five primary areas like Framework, Server, Services, Tools and Repository. And in these areas the strategy would be focused mainly on two key elements: Model driven and Service Based.

Model-Driven:

Microsoft is building a general-purpose modelling language, tools and repository to bridge all the models within an application, moving models to the centre of application development. So they have planned to create a modelling tool which bring the gap existing between the various modelling methodologies used by business analyst, architects, developers and non-it professionals who provide requirements to IT. We would be the more mature universal modelling editor.

Service-Based:

Continue to build on our service-oriented architecture (SOA) platform spanning client, server and cloud. BizTalk Services "1", which will feature messaging, identity and workflow for hosting composite applications

The first version of “Oslo” will be delivered through the next versions of our application platform products such as those code-named Microsoft Visual Studio “10,” Microsoft System Center “5,” BizTalk Server “6,” BizTalk Services “1” and Microsoft .NET Framework “4.”

In short Oslo would enable us to simplify modelling, developing, maintenance of enterprises integrated applications.

References:

Microsoft Oslo: http://www.microsoft.com/soa/products/oslo.aspx

Whats Oslo: http://blogs.msdn.com/asmitaw/archive/2007/12/27/whats-oslo.aspx

INDWAY-Integration Services