BizTalk Tutor

Biztalk : The system cannot find the file specified. (Exception from HRESULT: 0×80070002)

Thiru — Wed, 20 Feb 2008 13:00:34 +0000

A message received by adapter “FILE” on receive location “Client.Request_Recv.FILE” with URI

“D: \Bts\BtsFileReceiveLocs\Client\Dsn\DsnRequest_RecvPort\*.txt” is suspended.

Error details: The system cannot find the file specified. (Exception from HRESULT: 0×80070002)

MessageId: {40140550-4362-45DB-A4AA-C463D127AFA8}

InstanceID: {AC7980EC-B8C2-4DE0-ACEF-05783653716E

This issue is with the discrepancy between the dll’s that has been used in Binding and available in the GAC. Just unbind the application. Update the binding with the updated dlls. Else, Undeploy the application. Remove the dlls from GAC. Deploy the application with the updated dll bindings.

History of Biztalk Server

Thiru — Tue, 12 Feb 2008 08:27:38 +0000

BizTalk is definitely not a new product and it has gone through multiple releases, and as with all Microsoft products it has matured and stabilised over the past few years. Below is a short overview to the history of BizTalk.

2000 – BizTalk Server 2000
Microsoft released BizTalk late 2000. The BizTalk editor had a Mapper for translating data, a management desk for tracking data. Orchestrations were introduced to manage business processes. The product hade protocols for EDI, HTTP, HTTPS, MSMQ, SMTP, File transfer. An enterprise and standard version was released.

2002 – BizTalk Server 2002

Several new features were introduced such as the integration with Visual Studio .NET. SEED was introduced assist configuring with trading partners. BizTalk integration with Microsoft Operations Manager (MOM). There was a big drive was on web services. Changes were made to orchestrations with transaction support. The mappers were changed to support mixed XML. Developers could create functiods. There were also changes to many adapters with a few new adapters.

2004 – BizTalk Server 2004

Changes were made to how messaging and orchestrations integrated. The orchestration designer was significantly changed. Human Workflow Services, Business Activity Services added. A welcome content-based routing mechanism introduced. Security changed and SSO introduced. The rules engine and integration of rules into orchestrations. Pipeline designer for assembling and disassembling messages. Better support for industry standards. Used Microsoft .NET 1.0

2006 – BizTalk Server 2006

Used Microsoft .NET 2.0. The deployment model changed with a more modular approach. Easier to configure. Business Activity Monitoring was introduced. Health and Activity Tracking introduced with improvements to monitor. Development support in Visual Studio 2005 The processing of XML changed with some welcome changes should there be failures in messages. Recoverable interchange processing. Developers could create flat-file schemas with a wizard. Changes to the orchestration designer. BizTalk application introduced to allow solutions to be separated. Monitoring was radically changed. Many improvements were made to adapters with an introduction of new adapters. BAM improved and enhanced, the BAM portal, alerts, notifications, Web Portals and BAM interceptors added.

2007 – BizTalk Server 2006 R2

Runs on Microsoft .NET 2.0 with Microsoft .NET 3.0 using Windows Communication Foundation and Windows Workflow Foundation. RFID functionality added to BizTalk EDI Adapters changed. The BizTalk Adapter Pack introduced allowing adapters to be created and consumed with .NET Framework applications. BAM Interceptors for WF and WCF introduced. SSO 4.0 adopted.

Host Instances

Thiru — Wed, 06 Feb 2008 10:46:38 +0000

The Host Instances node contains all of the host instances in the current BizTalk Server group. Host instances are processes of the BizTalk Server runtime that execute your application components. Using the Host Instances node, you can create new host instances and refresh host instance information.

Hosts

Thiru — Wed, 06 Feb 2008 10:44:43 +0000

The Hosts node contains all of the in-process and isolated hosts in the BizTalk Server environment. A BizTalk Host is a logical container for items such as adapter handlers, receive locations (including pipelines), and orchestrations.

How to Call a Non-Serializable .Net class from an Expression Shape ?

Thiru — Mon, 04 Feb 2008 13:41:16 +0000

Add a reference of that dll (class). The class must be strongly signed and in the GAC.

Make sure your transaction type of Orchestration is Long Running transactional.

Add an Atomic scope.

Create an Orchestration variable of that class inside the scope.

Create an instance on that object inside the scope.

Call the method.

Persistence points in Orchestration

Thiru — Sat, 02 Feb 2008 13:16:21 +0000

End of a transactional scope (atomic or long running)
At debugging breakpoints
At the execution of other orchestrations through the Start Orchestration shape
At the Send shape (except in an atomic transaction)
When an Orchestration Instance is suspended
When the system shutdowns in a controlled manner
When the engine determines it wants to dehydrate
When an orchestration instance is finished

Property schema

Thiru — Mon, 28 Jan 2008 13:15:51 +0000

A property schema is used with one of the two mechanisms that exist within BizTalk Server for what is known as property promotion. Property promotion is the process of copying specific values from deep within an instance message to the message context. From the message context, these values are more easily accessed by various BizTalk Server components. These components use the values to perform actions such as message routing. Promoted property values can also be copied in the other direction, from the more easily accessible message context back into the depths of the instance message, just before the instance message is sent to its destination. A property schema is a simple version of a BizTalk schema that plays a role in the process of copying promoted properties back and forth between the instance message and the message context.

Envelope schema

Thiru — Mon, 28 Jan 2008 13:15:23 +0000

An envelope schema is a special type of XML schema. Envelope schemas are used to define the structure of XML envelopes, which are used to wrap one or more XML business documents into a single XML instance message. When you define an XML schema to be an envelope schema, a couple of additional property settings are required, depending on such factors as whether there are more than one root record defined in the envelope schema.

Flat file schema

Thiru — Mon, 28 Jan 2008 13:11:15 +0000

A flat file schema defines the structure of a class of instance messages that use a flat file format, either delimited or positional or some combination thereof. Because the native semantic capabilities of XSD do not accommodate all of the requirements for defining the structure of flat file instance messages—such as the various types of delimiters that might be used for different records and fields within the flat file—BizTalk Server uses the annotation capabilities of XSD to store this extra information within an XSD schema. BizTalk Server defines a rich set of specific annotation tags that can be used to store all of the required additional information.

XML schema

Thiru — Sat, 26 Jan 2008 13:08:41 +0000

An XML schema defines the structure of a class of XML instance messages. Because this type of schema uses XML Schema definition (XSD) language to define the structure of an XML instance message, and this is the intended purpose of XSD, such schemas use XSD in a straightforward way.