Aug 7

Debug maps in BizTalk 2006/2006 R2 and in BizTalk 2009

This is a great feature, that in most cases overlooked, because maps can become very large, to the point that is difficult to read, very difficult to maintain

By Sandro Pereira

Jul 24

BizTalk Orchestration – Call Orchestration from another project or from another BizTalk Application

Imagine that we have 2 Visual Studio BizTalk Projects: Project1 Orch1 Schema1 Project2 Orch2 Both are deployed to the same BizTalk

By Sandro Pereira

Jul 24

There was a failure executing the send pipeline: “Microsoft.BizTalk.DefaultPipelines.XMLTra...

When trying to receive an XML document from a Receive Port, it occurs the following error message and the message is suspense: “… Error Description:

By Sandro Pereira

Jul 24

Problem with Edifact Interchange and loopback adapter Receive Pipeline – Received unexpecte...

In a previous project, I worked with EDI message to interchange with partners, but before I send the message to the partner I have the need to pass them

By Sandro Pereira

Jul 20

BizTalk Document Mapping – Mass Copy Functoid

The Mass Copy functoid allows source records and containing elements and attributes to be copied and mapped across to the destination schema It creates a

By Sandro Pereira

Jul 20

BizTalk Document Mapping – Value Mapping Functoid and Value Mapping (Flattening) Functoid

If you want to map a specific field based on a condition, then Value Mapping functoid and Value Mapping (Flattening) Functoid are the two forms available to

By Sandro Pereira

Jul 20

BizTalk Schema validation – Default and Deep Validation

By default, BizTalk Server will examine only the namespace and the root node name of a message to identify and validate the schema, and will not detect extra

By Sandro Pereira

Jul 20

BizTalk Document Mapping – Organizing Maps

If you are dealing with large maps, they can become very complex and therefore very difficult to maintain and read To minimize this problem, BizTalk Server

By Sandro Pereira

Jul 4

Introduction BizTalk Document Schemas – Part II

Schema Namespaces Has posted before (link), BizTalk Server uses a combination of Namespace + Root Node name to identify and resolve schemas

By Sandro Pereira

Jun 19

Basics of BizTalk Runtime Architecture

BizTalk runtime architecture primarily has four major components: Receive Handler;Message Box;Orchestration;Send Handler Receive handler Receive

By Sandro Pereira
turbo360

Back to Top