- Architecture

Domain Standards and Integration Architecture

The domain standard schemas are the repositories of domain knowledge. The message schemas are schemas for the real data transferring between real systems. Use the domain standard schemas as a reference model for your schemas. Do not use the domain standard schemas as your message schemas.

BizTalk: Deployment Hell & BizTalk Deployment Framework

Is there something special in the BizTalk Server application deployment? Why is it so special? BizTalk Deployment Hell For the .NET applications the live is simple. There is an exe file and maybe several additional dll-s. Copy them and this is pretty much all deployment we need. The BizTalk Server requires the dll-s placed in GAC and registered in the special Management database. Why this is required? Mostly because the BizTalk automatically hosts applications in the cluster and because of the reliability. ......

Complex XML schemas. How to simplify?

[Sample code is here: HIPAA Schema Simplification for the BizTalk Server application]The XML Schemas are used for two main tasks: for processing XML documents (for the XML document validation and for the XML document transformation); for defining the domain specific standards. XML Schemas and Domain StandardsLet's talk about the domain standards. EDI, RosettaNet, NIEM, ebXML, Global Justice XML Data Model, SWIFT, OpenTrave, Maritime Data Standards, HIPAA, HL7, etc. If we look at those standards, ......

BizTalk Server: to be successful

What should be presented in the successful software? [By Raymond Hettinger from EuroPython 2011] It was told about Python and I will try to use the same criteria for the BizTalk Server. So, how it plays for the BizTalk Server? My score is (from * to *****): License – ** Commercial Distributions – *** Zen – ** Community – **** Third party software – **** Killer Apps and Success Stories – ** Platforms – Books – *** Now in more details: License BizTalk license is a typical server license from Microsoft. ......

BizTalk Integration Development Architecture

You can find some architecture information into the BizTalk documentation. You find out several tutorials and good amount of samples. Almost all of them related to the infrastructure architecture, i.e. how to create high available systems with clusters, how to scale out the BizTalk systems, etc. I covered several development aspects of architecture in series of articles:BizTalk Integration Development ArchitectureNaming ConventionsArtifact Composition ......

The Best Application Server from Microsoft

-Are you stupid? The BizTalk Server is an Integration Server. It is nothing to do with Application servers. That’s what you are probably thinking now… Application Types Let’s discuss different application types. Sequential Processing Application These applications work as single-threaded processes. An application gets the data potions and processes them one after another. . One exemplar of such kind is a file processing application. An application reads a file and processes it, then it reads another ......

BizTalk: Internals: Schema Uniqueness Rule

A source code could be downloaded from here.Sometimes in BizTalk the artifact visibility can be global. We place the artifacts in different assemblies and it doesn't change visibility. We place the artifacts in different BizTalk applications and it doesn't change visibility. Let’s talk about the schemas. In my previous post BizTalk: Internals: namespaces I've shown that schemas have additional parameter, the Xml [target] namespace. Why it is so important? The BizTalk receives messages on the Receive ......

BizTalk: Internals: the Partner Direct Ports and the Orchestration Chains

Partner Direct Port is one of the BizTalk hidden gems. It opens simple ways to the several messaging patterns. This article based on the Kevin Lam’s blog article. The article is pretty detailed but it still leaves several unclear pieces. So I have created a sample and will show how it works from different perspectives. Requirements We should create an orchestration chain where the messages should be routed from the first stage to the second stage. The messages should not be modified. All messages ......

BizTalk: Internals: Namespaces

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 ......

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, ......

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 Note: There is BizTalk Administrator interview questions by Tord Glad Nordahl. It is time for fun! These questions are for ......

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 ......

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 ......

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 ......

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 ......

Full - Architecture Archive