BizTalk team did a good job hiding the .NET guts from developers. Developers are working with editors and hardly with .NET code. The Orchestration editor, the Mapper, the Schema editor, the Pipeline editor, all these editors hide what is going on with artifacts created and deployed. Working with the BizTalk artifacts year after year brings us some knowledge which could help to understand more about the .NET guts. I would like to highlight the .NET namespaces. What they are, how they influence our ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/dMo

BizTalk Map Editor (Mapper) is a good editor, especially in the last 2010 version of the BizTalk. But sometimes it still cannot do the tasks easily. It is time for the Xslt code, it is time to remember that the maps are executed by the Xslt engine. Right-click the Mapper Grid (a field between the source and target schemas) and choose Properties /Custom XSLT Path. Input here a file name for the file with Xslt code. Only this code will be executed now, forget the picture in the Mapper, all those links ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/d0Z

The same article in the TechNet. If you are working with queues in BizTalk Server, the most possible it is the MSMQ (in my experience). MSMQ is an old man of the Microsoft technology stack. It was created when there were no good standards for messaging. Now MSMQ is wrapped partly in the .NET System.Messaging namespace. It is just a small facelift. MSMQ is still a proprietary technology without well-defined messaging protocol. It means, you cannot use the MSMQ messaging protocol without MSMQ itself. ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/cfa

It is stupid to compare those two beasts. BizTalk Server is a pricey, huge development and run-time system, it includes tons of the tools, supports tons of protocols and systems. It works for very specialized middle ware integration stack. It integrates big and complex systems as SAP, CRM, Oracle and intermediates many protocols and standards as SOAP, EDI, SWIFT, FTP, tons of them. It is a messaging system. ZeroMQ is a low-level, wire-level protocol, the same level as TCP. It has ultra-simple API. ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/cby

It is one more description of the Ordered Delivery (OD) in BizTalk. The main article about it is in MSDN. Here I am discussing the BizTalk Ordered Delivery “implementation details”. OD Considerations Ordered Delivery (sequential) mode is opposite of the “Parallel Delivery” mode. Parallel Delivery is the most productive mode; the Ordered Delivery is less productive mode. Transports such MSMQ and protocols, supporting the WS-ReliableMessaging, are the protocols supporting OD. Other protocols as FTP, ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/caB

This article is a Part 6 of the Interview Questions series. Part 1: BizTalk: Questions for interview without answers Part 2: BizTalk: Interview questions and principles Part 3: WCF: Questions for studying and interviewPart 4: WCF: Questions for studying and interview: DiscoveryPart 5: WCF: Questions for studying and interview: Routing Service Part 6: BizTalk: Advanced Questions Note: There is BizTalk Administrator interview questions by Tord Glad Nordahl. It is time for fun! These questions are for ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/cZz

One problem with email notifications is it usually sends too many emails. Errors frequently happen in series. For example, a temporarily issue with network can result in hundreds repetitive emails. In result an email notification designed as a “VIP” notification is downgraded to the “annoying” status. This email flooding could be mitigated with this solution. A Sample demonstrates using the emails for sending notification in case of failed messages. It compounds several similar errors in one email ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/cZJ

Recently I uploaded a "BizTalk: Sample: Error Handling" in MSDN Gallery This sample shows the BizTalk features: Routing Failed Messages in ports Catching Failed Messages with Send Port Catching Failed Messages with Orchestration Handling Exceptions inside Orchestration Handling SOAP Fault messages inside Orchestration ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/cYR

This is a second part of the BizTalk Naming Convention. Part 1: biztalk: BizTalk solution naming convention Special Orchestration Objects <Message> =: msg_ + <ShortMessageType> <Variable> =: var_ + <Name> <CorrelationSet> =: cor_ + <Name> <OrchestrationParameter> =: par_ + < Name> <RoleLink> =: roleLink_ + <Name> Note: These objects are special BizTalk objects. They are used in different language context and sometime they use different language ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/cXk

A sample demonstrates the PGP Encryption/Decryption in pipelines. You can download code here. A sample is based on a sample by Brian Jones See original code here The main additions to original code: · Single pipeline component was separated to two Encrypt and Decrypt pipeline components. It simplifies the pipeline configurations. · Configuration parameters are stored in SSO, which, I hope, improves security. · File names for temporary files are regenerated randomly each time. That eliminates errors ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/cXM

One area here is not so well documented. When we are filling in the Transport properties for WCF adapter, we see the SOAP Action header section. What is it? Where we could take the values for Operations and Actions? If we use the Consume WCF Service wizard, this section is filled up automatically. But sometimes we have to fill it in manually. NP Open a WSDL for the Web-service and search for a binding section. If you add the “?wsdl” to the Web-service URL, usually the Web-service WSDL is opened. ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/cWj

Photos from Summit Mighty Canada Oh, Canada! Microsoft is hearing you, guys. New Zealand is here. Portugal and Brazil are here... France is here... Netherlands is here... all BizTalkiens and the whole world is here... [See more MVP-s] Vsem privet ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/bXY

BizTalk : HAT: Select all Messages/Service Instances Sometimes I need to select all Messages/Service Instances in HAT, "Operations/Messages...(or Service Instances...)" window then terminate them. When I tried to use the mouse by "hold left button - drag over all records" I'm not in luck. As I've tried to use "click the first record (cell) - hold Shift and click the last record (cell)" I'm not in luck too. All these methods work only on the visual part of list. On the big list I have to use one of ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/M6B

This article is a Part 1 of the Interview Questions series. Part 1: BizTalk: Questions for interview without answers Part 2: BizTalk: Interview questions and principles Part 3: WCF: Questions for studying and interviewPart 4: WCF: Questions for studying and interview: DiscoveryPart 5: WCF: Questions for studying and interview: Routing Service Part 6: BizTalk: Advanced Questions Standards BPEL4WS: Comparing of BizTalk 2004 and BPEL4WS • Which points is the BTS Orchestration different from BPEL4WS ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/KcV

[See Sample: Context routing and throttling with orchestration] Imagine the project where most of the routing happens between orchestrations. I.e. routing is mostly between the MessageBox and orchestration with direct endpoints. Imagine also the most of the messages are with the same Message type. Usually in this case messages got the special node only for the routing. For example, the field can be the “Originator” or “Recipient” or “From” or “To”. What wrong is with this approach, it creates the ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/bUf

This is Part 1. Part 2: BizTalk: Timeline: Platform Support Now it is the timeline of the development tools only. It is a little bit "unofficial". For example, I included the ESB but not RFID. Versions 2000 and 2002 are not covered , there only placeholders. Mainly because since the 2004 version it is completely new product from many points of view, including the developer's point of view. It is interesting, the main tools: the Schema Editor, Mapper, Orchestration Editor, Pipeline Editor were not ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/b0l

It was a long ago. Smart guys from all across the world were in one place, at Microsoft campus. There are pictrures from the MVP (Microsoft Most Valuable Professional) Summit 2010 in Bellevue and Redmond, WA. All pictures are here: http://public.fotki.com/leo... Here are mostly BizTalk and CSD MVPs. See list of BizTalk MVP here https://mvp.support.microso... list of the Connected System Developer MVP ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/aze

New standard the UDDI was announced several years ago [see the history in Wikipedia]. The UDDI future was promising. I was sure for that. I thought, the future is for Web-services [WS], and it is. Isn’t that mean, we need services to search Web-services in internet, some Registries/Catalogs of the Web-services? How we could find the WS in internet? Google Search was not effective in this; it is still not effective now. By any means, the UDDI idea should win; all WS-s should work with UDDI Registers. ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/aqz

[See BizTalk: Using context for routing] The sample demonstrates using orchestration for throttling and using context routing. Usually throttling is implemented on the host level (in BizTalk 2010 we can also use the host instance level throttling). This sample demonstrates the throttling with orchestration convoy, that slows down a message flow from some customers. Sample implements sort of quality service agreement layer for different kind of customers. The sample demonstrates the context routing ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/bUe

Part 1: BizTalk: Instance Subscription and Convoys: Details This is a Part 2. I am discussing the Suspend shape together with Convoys and going to show that using them together is undesirable. In previous article we investigated the Instance Subscriptions and how they could create situation with dangerous zones in processing. Let' start with Suspend shape. [See the BizTalk Help] "You can use the Suspend shape to make an orchestration instance stop running until an administrator explicitly intervenes, ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/bQf