BTDF Deployment - Custom Pipeline Component

If I am deploying manually, I am able to deploy, GAC and get output accordingly.
1) But when using BTDF, its not getting deployed properly and not receiving any output. What am I doing wrong ?
2) Before deploying 'RemoveFooter' assembly and adding to PipelineBizTalk Project, how can I add that in tools of Pipeline components to add this 'RemoveFooter' component in Decode stage ?
In BTDF mentioned this :
<PropertyGroup>
<IncludePipelineComponents>true</IncludePipelineComponents>
</PropertyGroup>
<ItemGroup>
<PipelineComponents Include="$(ProjectName).PipelineComponents.dll">
<LocationPath>..\PipelineComponents\bin\$(Configuration)</LocationPath>
</PipelineComponents>
</ItemGroup>
MBH

Hi
MBH,
The configuration that you mentioned above is totally correct. When you add the custom pipeline component in BTDF it deploys
to “Pipeline Components” folder and at run time BTS refers the dll from this place.
Its working for me with the same configuration and I believe it might be other problem related to the actual project.
JB

Similar Messages

Custom Pipeline Component in BTDF

I have created a separate c# based custom pipeline component, how should I embed this in BTDF ?
Want to make sure this is Gac'd and available when I deploy to all other environments ?
MBH

I created a c# code Custom Pipeline component for parsing against my flat file schema.
<PropertyGroup>
<IncludePipelineComponents>true</IncludePipelineComponents>
</PropertyGroup>
<ItemGroup>
<PipelineComponents Include="$(ProjectName).PipelineComponents.dll">
<LocationPath>..\PipelineComponents\bin\$(Configuration)</LocationPath>
</PipelineComponents>
</ItemGroup>
But it doesn't appear when I deploy into other environments ? what am I missing ?
MBH

Deploying the custom Pipeline component in Production

I would like to know how to deploy the Pipeline component in to production. I created an an application in dev with the custom receive pipeline component in it. Thought importing the application's msi and binding file in production will automatically deploy
the pipeline component in to Pipeline component's folder. Bad thing is I didnt check if .dll was in Pipeline component's folder and ran the application. Now the messages got suspended with error
There was a failure executing the receive pipeline:Source: "Unknown " Receive Port: "" URI: "" Reason: Could not load file or assembly 'file:///E:\Program Files (x86)\Microsoft BizTalk Server 2013\Pipeline Components\.dll' or
one of its dependencies. The system cannot find the file specified.
Help me out with this. Thanks

You do not need to copy the DLL in C:\Program Files (x86)\Microsoft BizTalk Server 2013\Pipeline Components.
You have to just GAC the dll on all the BizTalk servers and restart the host instance.
Please see
BizTalk: Deploying Custom Pipeline Components in BizTalk Server 2006 and Higher wiki article
I hope this solves all your queries.
Greetings,HTH
Naushad Alam
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or
Mark As Answer
alamnaushad.wordpress.com

Custom Pipeline Component - Deployment Issue

We have created a custom pipeline component that logs information via ETW. The component was added to a suite of common pipelines that our applications share, as well as to a handful of application specific pipelines that require other custom components
used only by those applications. I made a change to the component and deployed the DLL to our test environment, added it to the GAC and restarted all of the host instances. The common pipelines all seem to work fine with the new DLL, but for some reason those
pipelines that are application specific (which use the same version of the DLL) all started generating the "Object reference not set to an instance of the object" error. So I replaced the new DLL with the original version and all of the pipelines
(common and otherwise) worked okay again. Can anyone tell me what I need to do to get the application specific pipelines to work with the modified DLL?
Thank you.
Thanks, Bruce

Quite certain. The application specific pipelines call public methods that write string data to a log file - they don't pass any parameters - all of that is contained within the component itself. We only changed the content of the data for the internal parameters,
not the data type, so the signature of the procedures remain the same.
The original author of the code had the component logging every attribute of the pipeline and received message to the log file which was creating very large and non-useful logs. We only replaced the call to the pc.GetProperties() and inmsg.GetProperties()
methods (both return string values) with concise strings containing the data we need logged.
The first version of the pipeline did not contain the GetProperties methods, those were added later and the pipeline was deployed for testing. At that time, all of the application specific pipelines began generating errors that the GetProperties() method
was not recognized, so we ended up having to go back and rebuild and re-deploy all of the application specific pipelines to use the newer version in order to get them to work. We should not have to go through this much effort to replace a shared
library, and am hoping we can find a way to deploy it without having to redeploy all of the other pipelines as well.
We deployed the new pipeline according to Microsoft's recommendations in
BizTalk: Deploying Custom Pipeline Components in BizTalk Server 2006 and Higher so we are left scratching our heads at this point.
Thanks, Bruce

Unable to add the Custom Pipeline component in to the Visual Studio Tool Box

I have tried to create the custom Pipeline component to transfer the large message in Receive side,
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Xml;
using System.IO;
using Microsoft.BizTalk.Message.Interop;
using Microsoft.BizTalk.Component.Interop;
namespace Sample.LargeFilesDecoder
[ComponentCategory(CategoryTypes.CATID_PipelineComponent)]
[ComponentCategory(CategoryTypes.CATID_Encoder)]
[System.Runtime.InteropServices.Guid("25984614-BCFD-4c47-82FC-4A2300B76411")]
public class LargeFilesDecoder : IBaseComponent,
IComponentUI,
IComponent,
IPersistPropertyBag
#region IBaseComponent Members
public string Description
get
return "Pipeline component used to receive Larger Files through SFTP Ports";
public string Name
get
return "LargeFilesDecoder";
public string Version
get
return "1.0.0.0";
#endregion
#region IComponentUI Members
public IntPtr Icon
get
return new System.IntPtr();
public System.Collections.IEnumerator Validate(object projectSystem)
return null;
#endregion
#region IPersistPropertyBag Members
private string _largeFileLocation;
private int _thresholdSize;
public string LargeFileLocation
get { return _largeFileLocation; }
set { _largeFileLocation = value; }
public int ThresholdSize
get { return _thresholdSize; }
set { _thresholdSize = value; }
public void GetClassID(out Guid classID)
classID = new Guid("DBA77DFA-5D3E-4B85-8F78-1D6330B6BCA0");
public void InitNew()
public void Load(IPropertyBag propertyBag, int errorLog)
object val1 = null;
object val2 = null;
try
propertyBag.Read("LargeFileLocation", out val1, 0);
propertyBag.Read("ThresholdSize", out val2, 0);
catch (ArgumentException)
catch (Exception ex)
throw new ApplicationException("Error reading PropertyBag: " + ex.Message);
if (val1 != null)
_largeFileLocation = (string)val1;
if (val2 != null)
_thresholdSize = (int)val2;
public void Save(IPropertyBag propertyBag, bool clearDirty, bool saveAllProperties)
object val1 = (object)_largeFileLocation;
propertyBag.Write("LargeFileLocation", ref val1);
object val2 = (object)_thresholdSize;
propertyBag.Write("ThresholdSize", ref val2);
#endregion
#region IComponent Member
public IBaseMessage Execute(IPipelineContext pContext, IBaseMessage pInMsg)
if (_largeFileLocation == null || _largeFileLocation.Length == 0)
_largeFileLocation = Path.GetTempPath();
if (_thresholdSize == null || _thresholdSize == 0)
_thresholdSize = 4096;
if (pInMsg.BodyPart.GetOriginalDataStream().Length > _thresholdSize)
Stream originalStream = pInMsg.BodyPart.GetOriginalDataStream();
string largeFilePath = _largeFileLocation + pInMsg.MessageID.ToString() + ".msg";
FileStream fs = new FileStream(largeFilePath, FileMode.Create);
// Write message to disk
byte[] buffer = new byte[1];
int bytesRead = originalStream.Read(buffer, 0, buffer.Length);
while (bytesRead != 0)
fs.Flush();
fs.Write(buffer, 0, buffer.Length);
bytesRead = originalStream.Read(buffer, 0, buffer.Length);
fs.Flush();
fs.Close();
// Create a small xml file
string xmlInfo = "<MsgInfo xmlns='http://Sample.LargeFilesDecoder'><LargeFilePath>" + largeFilePath + "</LargeFilePath></MsgInfo>";
byte[] byteArray = System.Text.Encoding.UTF8.GetBytes(xmlInfo);
MemoryStream ms = new MemoryStream(byteArray);
pInMsg.BodyPart.Data = ms;
return pInMsg;
#endregion
I have
Added .dll file in to the Global Assembly Cache (use gacutil)
Copied it the Pipeline Components folder (E:\Program Files (x86)\Microsoft BizTalk Server 2013\Pipeline Components)
Everything was successful, when I try to add the component to the Toolbox I get the message like below and cannot find the component in Toolbox.
Tried several times but still getting stuck in the same place. I am using Visual Studio 2013. Any help is greatly appreciated.

Do not put the Assembly in the %\Pipeline Components folder. Pipeline Component Assemblies should be in the GAC only.
To correctly deploy a custom Pipeline Component, you can follow the steps in this Wiki Article:
http://social.technet.microsoft.com/wiki/contents/articles/26404.biztalk-deploying-custom-pipeline-components-in-biztalk-server-2006-and-higher.aspx
I have never seen that specific error before. Are you sure you're browsing from the Pipeline Components tab?

Custom Pipeline Component stopped changing input filename

Hi
In my project, I have a custom pipeline component to change the input file name. I use it in the receive pipeline decode stage. It was working initially when I had only a receive pipeline and custom pipeline component in my solution. later I introduced
two schemas, an orchestration, map and a send pipeline. The rename is not working anymore. Please help.
receive adapter: FILE
send adapter: FTP
Custom pipeline component: (File Name Setter)
Receive pipeline:
decode: custom pipeline component to rename the filename
disassemble: flatfile disassembler conecting to a document schema
Map:
Schema 1 to Schema 2 (transforms from Windows to Unix format)
Orchestration:
receive message
transform using map above
send message
Exception Handler
Send pipeline:
FlatFile assembler
manibest

May be its not working now, because in the orchestration which you have added,
you’re constructing a new message from the received message and the context properties from the Received message is not copied across to the newly constructed message. So when you use “%SourceFileName%” macro in the send port,
the ReceivedFileName context property is missing in the newly constructed message which is sent out.
So in your Orchestration, while constructing (in MessageAssignment shape) the outbound message from the Received message, copy the context property of the Received message to the newly constructed message. Something like this
//This line copies all the context properties from received message to the outputted message
msgOutputted (*)= msgReceived(*)
//or
//This line just copies the receive file name context property from received message to the outputted message
msgOutputted (FILE.ReceivedFileName)= msgReceived (FILE.ReceivedFileName).
If you’re not using the Orchestration or constructing the new message (even in map), then just add the schemas/orchestration or any pipeline would not affect the ReceiveFileName code. May be in this case, debug the pipeline and also check whether the outputted
message has ReceivedFileName in its context property.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Custom pipeline component creates the folder name to archive messages

Hi
I have an requirement that a BizTalk application is receiving untyped messages and at the receive location the pipeline have to archive the incoming message with the specifications:
suppose I have an xml like
<PurchaseOrder>
<OrderId>1001</OrderId>
<OrderSource>XYZ</OrderSource>
<Code>O01</Code>
</PartyType>
In the pipeline component it has to read this xml and have to use OrderSource value 'XYZ' to create a archival folder and the message have to archive with file name '%MessageId%'
It has to be done by writing custom pipeline component where I am not familiar with c# coding, Can anyone please how to implement mechanism.
Thanks In Advance
Regards
Arun
ArunReddy

Hi Arun,
Use
BizTalk Server Pipeline Component Wizard to create a decode pipeline component for receive. Install this wizard. This shall help you to create the template project for your pipeline component stage.
Use the following code in the Execute method of the pipeline component code. This code archives the file based with name of the file name received.
public Microsoft.BizTalk.Message.Interop.IBaseMessage Execute(Microsoft.BizTalk.Component.Interop.IPipelineContext pc, Microsoft.BizTalk.Message.Interop.IBaseMessage inmsg)
MemoryStream tmpStream = new MemoryStream();
try
string strReceivedFilename = null;
DateTime d = DateTime.Now;
try
//Get the file name
strReceivedFilename = inmsg.Context.Read("ReceivedFileName", "http://schemas.microsoft.com/BizTalk/2003/file-properties").ToString();
if (strReceivedFilename.Contains("\\"))
strReceivedFilename = strReceivedFilename.Substring(strReceivedFilename.LastIndexOf("\\") + 1, strReceivedFilename.Length - strReceivedFilename.LastIndexOf("\\") - 1);
catch
strReceivedFilename = System.Guid.NewGuid().ToString();
originalStream = inmsg.BodyPart.GetOriginalDataStream();
int readCount;
byte[] buffer = new byte[1024];
// Copy the entire stream into a tmpStream, so that it can be seakable.
while ((readCount = originalStream.Read(buffer, 0, 1024)) > 0)
tmpStream.Write(buffer, 0, readCount);
tmpStream.Seek(0, SeekOrigin.Begin);
//ToDo for you..
//Access the receive message content using standard XPathReader to access values of OrderSource and construct file pathAccess the receive message content using standard XPathReader to acceess values of OrderSource and contruct the file path
string strFilePath = //Hold the value of the file path with the value of OrderSource
string strCurrentTime = d.ToString("HH_mm_ss.ffffff");
strFilePath += "\\" + strReceivedFilename + "_";
FileStream fileStream = null;
try
System.Threading.Thread.Sleep(1);
fileStream = new FileStream(strFilePath + strCurrentTime + ".dat", FileMode.CreateNew);
catch (System.IO.IOException e)
// Handle the exception, it must be 'File already exists error'
// Wait for 10ms, change the file name and try creating the file again
// If the second 'file create' also fails, it must be a genuine error, it'll be thrown to BTS engine
System.Threading.Thread.Sleep(10);
strCurrentTime = d.ToString("HH_mm_ss.ffffff"); // get current time again
string dtcurrentTime = DateTime.Now.ToString("yyyy-MM-ddHH_mm_ss.ffffff");
fileStream = new FileStream(strFilePath + strCurrentTime + ".dat", FileMode.CreateNew);
while ((readCount = tmpStream.Read(buffer, 0, 1024)) > 0)
fileStream.Write(buffer, 0, readCount);
if (fileStream != null)
fileStream.Close();
fileStream.Dispose();
if (originalStream.CanSeek)
originalStream.Seek(0, SeekOrigin.Begin);
else
ReadOnlySeekableStream seekableStream = new ReadOnlySeekableStream(originalStream);
seekableStream.Position = 0;
inmsg.BodyPart.Data = seekableStream;
tmpStream.Dispose();
catch (Exception ex)
System.Diagnostics.EventLog.WriteEntry("Archive Pipeline Error", string.Format("MessageArchiver failed: {0}", ex.Message));
finally
if (tmpStream != null)
tmpStream.Flush();
tmpStream.Close();
if (originalStream.CanSeek)
originalStream.Seek(0, SeekOrigin.Begin);
return inmsg;
In the above code, you have do a section of code which will access the receive message content using standard XPathReader to access values of OrderSource and construct the file path. I have
commented the place where you have to do the same. You can read the XPathReader about here..http://blogs.msdn.com/b/momalek/archive/2011/12/21/streamed-xpath-extraction-using-hidden-biztalk-class-xpathreader.aspx
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Custom Pipeline Component error

I have created a custom pipeline component which references a template file on the local drive e.g. c:\test\template.xlsx. however when I run the application the Send pipeline fails Reason: 'c:\test\template.xlsx' could not be found.
It does exist, everything is spelt correctly and the host account has access to the folder. Why can't the component see it?
----------------<0>----------------
http://redeyedmonster.co.uk
----------------<0>----------------

I tried a code as highlighted by Rachit, but I don’t see issue as the referred blog suggest.
Coming to questioners code, I created a quick pipeline component which uses a dll for
Microsoft.Office.Interop.Excel
accessing the excel files and does something with Excel file.
Few things I want to highlight here.
If the questioner (RedEyeMonster) is using the same dll (Microsoft.Office.Interop.Excel)
in the pipeline component as I used, then I am afraid Workbooks.Open’s component doesn’t just take one parameter as shown.
Open method doesn’t have any overloaded methods. It takes few parameter and its worth checking each one on them.Some of the parameter are very important and could cause issues (like
ReadOnly , IgnoreReadOnlyRecommended, Editable etc). As said, the
Workbooks .Open method doesn’t just have template file location parameter. It’s worth reviewing the code again.
Microsoft.Office.Interop.Excel.Application excelApplication = new Microsoft.Office.Interop.Excel.Application();
//When I tried without the following couple of lines, my program waited for long time and crashed
excelApplication.DisplayAlerts = false;
excelApplication.Visible = true;
Microsoft.Office.Interop.Excel.Workbook excelWorkboook = excelApplication.Workbooks.Open(@"C:\MRAshwinPrabhu\TestExcel.xsl", 2, false,
5, "", "", true, Microsoft.Office.Interop.Excel.XlPlatform.xlWindows, "",
false, false, 0, false, true, 0);
While trying the code, I create a excel file as extension *.xls (older version of Excel 97-2003 workbook) and in the code I tried to open the file as “C:\foldername\FileName.xlsx”.
*.xls and *.xlsx are different, though in the folder the excel icon may look similar they are different file extensions. I for the same error as the questioner.
Also issue I faced while trying this is “DisplayAlerts”
property. When I tried without setting this property to false, my program just waited for long time and crached evently. So when you use in a program like pipeline where you don’t have UI, ensure this property is set to false.
Hope the above suggest would help the questioner.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Is it possible to process a 0kb file within a custom pipeline component?

Hi There,
You probably wondering.. what the hell do you need this for?
Well.. we have a third party application that process a file as following
1) Import the original file
2) Export the original file
3) Append the original file (with the data I need)
4) Create a 0 kb file with the original exported filename but added .sem to show me that the export is done.
So my guessing was to with a custom pipeline component (receive) to pickup the .sem file, and use the original exported file to process the data from within the custom pipeline component.
Well, this works perfectly.
But... this only works if I add any data to the .sem file.
Otherwise BizTalk picks up the .sem file, but does not process it, it actually does not enter the pipeline at all, and it also does not appear in the tracking.
Is there a possiblity to accept 0kb files within a custom pipeline component?
Please help, Thanks
DP

Hi,
Here is an excellent article explaining the behavior of BizTalk for zero Byte files. It can help you achieve your mentioned goal.
If this answers your question please mark as answer. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Custom Pipeline component for Removing Trailer record from .txt file

public Microsoft.BizTalk.Message.Interop.IBaseMessage
Execute(Microsoft.BizTalk.Component.Interop.IPipelineContext pc,
Microsoft.BizTalk.Message.Interop.IBaseMessage inmsg)
    IBaseMessagePart bodyPart = inmsg.BodyPart;
    Stream originalStrm = bodyPart.GetOriginalDataStream();
    StreamReader sReader =
new StreamReader(originalStrm,
System.Text.Encoding.UTF8);
    string sRecord = sReader.ReadToEnd();
    MemoryStream memStream =
new MemoryStream();
    StreamWriter sw =
new StreamWriter(memStream);
    inmsg.BodyPart.Data
= memStream;
    inmsg.BodyPart.Data.Position
= 0;
    //"\r\n" is the delimeter for the the record
    string[] separator
= new string[]
{ "\r\n" };
    string[] strArray
= sRecord.Split(separator,
StringSplitOptions.None);
    //Loop untill the last line (i.e ignore the trailer)
    for (int n
= 1; n < strArray.Length; n++)
        sw.Write((strArray[n
- 1] +
"\r\n"));
    sw.Flush();
    memStream.Flush();
    memStream.Position
= 0;
    inmsg.BodyPart.Data
= memStream;
    inmsg.BodyPart.Data.Position
= 0;
    return inmsg;
after Deploying and in Gac, when configuring Receive Pipeline, it shows no properties in Decode stage ?
MBH

There is nothing wrong with your code it removes the lastline, if there is no carriage return on it.
If your input file is like:
line1 <cr><lf>
line2 <cr><lf>
line3
The result is:
line1 <cr><lf>
line2 <cr><lf>
But if your input file is like:
line1 <cr><lf>
  line2 <cr><lf>
line3 <cr><if>
The result is:
line1<cr><lf>
line2<cr><lf>
<empty line>
So when you have a carriage return on the last line, it results in an empty line, can this be the cause of your problem?

BizTalk BTDF Custom Pipeline deployment

I have Schemas, Maps, Pipelines, Orchestration all under 1 BizTalk project A.
I have created another project B and have written custom c# Custom Pipeline component.
A and B are both under 1 solution.
I am using BTDF for deployment. Only for project 'A' I created the .btdf proj and mentioned :
<Itemgroup>
<schemas Include= "Corp.Integrations.ProjName.dll">
<LocationPath>..\$(ProjectName)\bin\$(Configuration)</LocationPath)
</schemas>
</ItemGroup>
Do I need to do add anything here ?
<IncludePipelines>False</IncludePipelines> ----> do I need to make it true ?
<ItemGroup>
<AppsToReferenceInclude="Corp.Integration.Proj"/>
<ItemGroup>
Please help, my Proj B is not deploying or inserting into GAC or under Custom Pipeline components.
MBH

Hello,
First, you need to GAC the Custom pipeline component dll.
And from Property Group you need to Include
<IncludePipelineComponents>true</IncludePipelineComponents>
From Item Group
<PipelineComponents Include="yourPipelineComponent.dll">
<LocationPath>..\$(ProjectName)\bin\</LocationPath>
</PipelineComponents>
Praj Dixit

Biztalk Custom Pipeline Error

i have deployed my Custom pipeline and when i tried to use it it gives me the below error
There was a failure executing the receive pipeline: "BizTalk_Server_Project22.ReceivePipeline123, BizTalk Server Project22, Version=1.0.0.0, Culture=neutral, PublicKeyToken=2f421c0b0e473f3a" Source: "Unknown " Receive Port: "ReceivePort8"
URI: "E:\rcv\gvgvg\*.xml" Reason: The pipeline component ClassLibrary123.filename,ClassLibrary123, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7cd997faca10c5d6 can not be found. If the component name is fully qualified, this error may occur
because the pipeline component can not be found in the assembly.
I have build the custom pipeline project placed the dll in the pipleine components and gac the same dll but i still get the below error
can you help me with this?

Do not put the Assembly in the %\Pipeline Components folder. Pipeline Components should be in the GAC only.
See here:
BizTalk: Deploying Custom Pipeline Components in BizTalk Server 2006 and Higher
Make sure you're trying to put it in the correct GAC location. You cannot drop CLR 4.0 Assemblies in the Assemblies folder.
You muse use gacutil.exe to properly GAC any Assembly. There is an example in the above Wiki Article along with all other steps to use a custom Pipeline Component.

How to get interchange id in custom pipeline and in orchestration

My scenario is that I want to create a unique id for a message which should be remain unique throughout biztalk so that I can track it anywhere.
I got messageID context property of message in decoding pipeline component through IBaseMessage pInMsg.MessageID.ToString() and
got the same messageID in orchestration through messageName(BTS.MessageID) in expression shape.
But when I am using a custom disassembler component , I am unable to get the same messageID in orchestration because disassembler stage create a new messageID.
Can I use interchangeID of message for this scenario ?
If yes,how can I get interchangeID in custom decoding component as well as in orchestration ?
Prakash

Hi Prakash,
Yes, I believe InterchangeID should work for you in this case.
Refer:
http://geekswithblogs.net/chrishan/archive/2006/01/17/66161.aspx
http://felixmondelo.blogspot.in/2007/08/interchangeid-vs-messageid.html
How to access?
1) In your custom pipeline component you can access it
Guid interchangeID = Guid.Parse(pInMsg.Context.Read("InterchangeID","http://schemas.microsoft.com/BizTalk/2003/system-properties");
where pInMsg is your IBaseMessage.
2) In orchestration:
varGuid = System.Guid.Parse(Message_1(BTS.InterchangeID));
I hope his helps.
Rachit

ESB - Is there a way to set context properties when using esb custom pipeline

Hi there,
I have a situation where I am using a oneway wcf sql custom receive adapter to polling db and a two-way solicit response wcf sql send adapter to update the db and receive a result back.
Now I had got this working by setting the BTS.Operation and BTS.MessageType properties using a custom receive pipeline on the receive port. FOR SOME REASON THESE TWO WERE NOT SET BY THE RECEIVE PORT !!!
Now I have decided to wrap all that in en ESB itinerary by converting the send port into a dynamic one. I get the following error:
Exception of type 'Microsoft.BizTalk.Message.Interop.BTSException' was thrown.
Since I am using the ESB pipeleine - ItineraryReceiveXML I am not able to set the BTS.Operation and BTS.MessageType explicitly in a pipeline neither can I derive a pipeline form the ESB pipeline as it's a sealed class.
So my questions are:
1. Any idea what the above error could be ?
2. Also is there a way I get set context properties using an ESB itinerary as that is the only difference from before, can I do that in a map ?
Thanks
Phanindra

BTS.MessageType is typically set by one of the Disassemblers.
BTS.Operation has nothing to do with the Receive Port/Location and is set by the Engine only when coming from an Orchestration Port.
But, you can set any Property in any Stage with a custom Pipeline Component as you've found.
"Exception of type 'Microsoft.BizTalk.Message.Interop.BTSException' was thrown."
There's usually a lot more to the stack trace. You'll have to include the whole thing.
Finally, what benefit do you expect from adding the ESB layer? This is pretty trivial with an Orchestration.

Stopping message at Pipeline component

Hi all,
I have a message and I am checking if the file size is more than 4 MB, the files should be routed back in a email.
If it is less than 4 MB, it should be processed further with orchestration.
Now i have written the code and working fine, I am just not sure if I can return a null pINMsg incase size is more than 4 MB. As of now I thought of constructing a null data message with only namespace and reject it in the orchestration.
Is there any other way to ignore the 4 MB message in the pipeline ??
Thanks,
Varun
Thanks, Varun

Hi Varun,
If you look closer to your requirement, it’s not “stopping” the message if it’s more than 4MB. It’s actually
If the message size is greater than 4 MB,
then send email with received file as attachment
Else
send/process the message in an Orchestration.
For this requirement, you can do the following:
Create a custom pipeline component use it in Receive Location. In the component check the size of the received message as you do now. If it’s lesser than 4 MB proceed with
it by publishing the message to message Box where your Orchestration will subscribe the published message.
Again in the same custom receive pipeline component, If the message size is greater than 4 MB, then store the received message to a local drive’s (or shared drive) folder.
Don’t publish the >4MB message, but construct a trigger-like message which contains the path where the received file is saved. Publish this trigger-like message into message Box in the case of <4 MB.
Have a send port with filter for message type of the trigger-like message. In the send port, use another custom send pipeline with a pipeline component which will receive
the trigger message (which would have been published into msgbox in case of >4MB). Retrieve the URL/path for the saved <4MB file construct an email message and with the >4 MB file from local/shared drive as attachment.
With this design, your requirement is satisfied also you have not published the >4MB file into BizTalk message box.
Regards,
M.R.Ashwin Prabhu
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

BTDF Deployment - Custom Pipeline Component

Similar Messages

Maybe you are looking for