Posts

Creating Custom Pipeline Component and Pipeline for Reading Excel File in BizTalk

Image
In this blog I will explain how can we read an Excel file using pipeline in BizTalk . A custom pipeline components need to be develop to parse the excel file  to generate an xml file matching an existing defined schema .   A custom pipeline component is just simple .NET DLL that implements a class with some predefined interfaces. This interface represents the layer between a .NET program and the BizTalk Server. When we create custom pipeline class we need to Implement   IBaseMessage ,  IComponent ,  IComponentUI , and  IPersistPropBag   interfaces.You can use the below code as is.  The logic for reading an Excel file will be implemented inside the  Execute  method under  IComponent I nterface . ExcelDecoder.cs (Custom Component File) using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.ComponentModel; using Microsoft.BizTalk.Component.Interop; using Mic...
Post a Comment
Read more

Issues After upgrading BizTalk 2013 to BizTalk 2013 R2 - Could not load file or assembly 'Microsoft.BizTalk.Interop.SSOClient

I just upgraded 2013 to 2013 R2. These are the steps. I installed VS 2013 first which is required. Backup All the DB's ·          BizTalkDTADb ·          BizTalkMgmtDb ·          BizTalkMsgBoxDb ·          BizTalkRuleEngineDb This is the issues that I found. After Smooth Installation of Biztalk 2013 R2.I tested the already deployed orchestration which was up and running before R2 installation to check the impact of upgrade on the code. After restarting the Host Instances when I trigger the orchestration by placing the message at receive location,message got suspended and following Exception was logged in Event Viewer. Exception : Inner exception: Could not load file or assembly 'Microsoft.BizTalk.Interop.SSOClient, Version=7.0.2300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' o...
Post a Comment
Read more

Dynamically Selecting an Itinerary Using Business Rule Policy in BizTalk 2013

Image
Currently, In BizTalk 2013 when we call a Business Rule Policy   Via the default pipeline  ItinerarySelectReceiveXml using following ResolveConnectionString BRI:\\policy=Mypolicy;version=1.0;   will not work. The following exception is thrown with ESB 2.2 on Microsoft BizTalk Server 2013 in event log when the ItinerarySelectReceiveXML receive pipeline is used to call the Business Rules Engine to dynamically select an itinerary (using the ESB BRI Resolver). Exception has been thrown by the target of an invocation.  Source: Microsoft.Practices.ESB.Resolver.ResolverMgr  Method: System.Collections.Generic.Dictionary`2[System.String,System.String] Resolve(Microsoft.Practices.ESB.Resolver.ResolverInfo, Microsoft.BizTalk.Message.Interop.IBaseMessage, Microsoft.BizTalk.Component.Interop.IPipelineContext)  Error Source: mscorlib  Error TargetSite: System.Object InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)...
1 comment
Read more