BizTalk

BizTalk and RabbitMQ

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:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk and 0MQ (ZeroMQ)

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:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk: Ordered Delivery

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:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk: Advanced Questions

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 It is time for fun! These questions are for an Advanced level of the BizTalk Developers. I hope you don’t have a single...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk: Samples: Error Handling, Email Notification

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:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk: Sample: Error Handling

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:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk Orchestration Naming Conventions

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:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk: Sample: PGP Encryption/Decryption Pipeline Components

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:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk and WCF adapters: Operation and SOAP Action

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:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

Microsoft 2011 MVP Global Summit: Pictures

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:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk: Using context for routing

[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:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk: Sample: Context routing and Throttling with orchestration

[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:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk: Suspend shape and Convoy

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:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk: Instance Subscription and Convoys: Details

This is Part 1. Part 2. BizTalk: Suspend shape and Convoy Convoys are frequently used in the in the orchestrations in BizTalk Server. Sometimes we have got contra intuitive behavior in the convoys, when messages and orchestrations get suspended in unpredictable manner. This issue is well-known, the suspended messages get name the "zombie". The name is unofficial, but issue is still there. Here I would describe in details, what, when and why this zombie situations are happen. An orchestration can...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk and SQL: Alternatives to the SQL receive adapter. Using Msmq to receive SQL data

If we have to get data from the SQL database, the standard way is to use a receive port with SQL adapter. SQL receive adapter is a solicit-response adapter. It periodically polls the SQL database with queries. That’s only way it can work. Sometimes it is undesirable. With new WCF-SQL adapter we can use the lightweight approach but still with the same principle, the WCF-SQL adapter periodically solicits the database with queries to check for the new records. Imagine the situation when the new records...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk: History of one integration project

[Russian version of the article] "In the beginning God made heaven and earth. Then he started to integrate." At the very start was the requirement: integrate two working systems. [fairy tale of the system integrators] Small digging up: It was one system. It was good but IT guys want to change it to the new one, much better, chipper, more flexible, and more progressive in technologies, more suitable for the future, for the faster world and hungry competitors. One thing. One small, little thing. We...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk: Timeline: Platform Support

This is the second part. Part 1: BizTalk: Timeline: Development Tools. As you can see, the last version of the BizTalk 2010 shifts the platform support to new versions of the .NET, SQL Server, and Visual Studio, and finish support for the previous platform versions. High-quality picture in PDF format...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk: Timeline: Development Tools

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:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

MVP Global Summit 2010. Pictures

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:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

UDDI standard is a niche technology. Why?

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:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

Full BizTalk Archive