Pipeline Testing Library Updated

Pipeline Testing Library Updated

I’ve just now updated my Pipeline
Testing Library
. In this version, I’ve created my own mock IPipelineContext[Ex]
implementation, to support configuring some functionality not previously available:

  1. You can now configure at the pipeline level the thumbprint for the Group Signing Certificate
    so that it is returned from IPipelineContext.GroupSigningCertificate to pipeline components.
    Here’s how you’d configure it:

    SendPipelineWrapper pipeline = PipelineFactory.CreateEmptySendPipeline();

    pipeline.GroupSigningCertificate = “….”;

  2. Now transactional support is available for pipeline components if you enable it (it’s
    disabled by default). If you do enable it, then components will get a valid DTC transaction
    returned from IPipelineContextEx.GetTransaction(). I’m not 100% comfortable with this,
    but it can be useful in a few scenarios (see below for one such one). To enable it,
    call the EnableTransactions() method on the pipeline wrapper object just before calling
    Execute().

The reason why I implemented the transactional support in the pipeline context mock
object is that some components require it. In particular, it turns out that the BizTalk
Framework Disassembler Component (BtfDasmComp) will not work unless the pipeline context
returns a valid transaction from IPipelineContextEx.GetTransaction().  With this
update, you can now test pipelines that use the BtfDasmComp component, though be aware
that the transaction object is then used to access some of the biztalk databases (I’m
not exactly sure yet what for, though). Here’s an example piece of code with such
a trick:

ReceivePipelineWrapper pipeline = PipelineFactory.CreateEmptyReceivePipeline();

pipeline.AddComponent(new BtfDasmComp(), PipelineStage.Disassemble);

FixEncodingComponent fix = new FixEncodingComponent();

fix.Encoding = Encoding.Unicode;

pipeline.AddComponent(fix, PipelineStage.Decode);

 

pipeline.EnableTransactions();

 

Stream input = new FileStream(@”e:\temp\BtfDasmTest\BOBUILDING_SITE2.xml”, FileMode.Open);

IBaseMessage inputMsg = MessageHelper.CreateFromStream(input);

 

MessageCollection outputMsgs = pipeline.Execute(inputMsg);

 

Download Page Issues — FIXED!!

I just checked and the corrected page is now live.


There seems to be some issues with the official download page for the BizTalk Server 2006 Tutorials. I am investigating and we will have it fixed shortly. In the meanwhile, the files are available in the posts below — some are on page 2 (link at the bottom).


Thanks,


Liza


This posting is provided “AS IS” with no warranties, and confers no rights.

CodePlex is online now.

We all know the problems we had with gotdotnet and people tend to move their open source projects to SourceForge. Here is the reply from Microsoft towards open source community CodePlex.

As I mentioned in my previous post Microsoft launched a new portal to know about the people, insights, and analysis from the Microsoft Open Source Software Lab.

It clearly shows Microsoft positive approach towards open source community, big applause for the guys over there who made it happen.

I already contacted James Newkirk to bring my SQL Service Broker Management studio 2005 project into open source community, since CodePlex is in BETA now, you cannot add projects directly.

WSE Adapters for BizTalk Server 2006

The service pack for the WSE 2.0 adapter is now available and now works with 2006 or 2004.Grab it today to start adding WSE enabled web services to your integration options.
Also, the fine folks at TwoConnect have created a WSE 3 adapter for BizTalk Server 2006. Given that Microsoft will not be creating an adapter for WSE 3, this is a great option if you need to support WSE 3.0 in your BizTalk solution today.

Tutorial 2 issue

Tutorial 2: Purchase Order Process > Lesson 1: Set Up the Supplier Side > Step 2: Enable Web Service Publishing >


In this step I create a new Application Pool named TutorialAppPool, but I’ll never use this App Pool to associate with one Virtual Directory in the tutorial.  I assume that this App Pool will be use in B2BOrchestrations_webservice but the tutorial doesn’t have this information.


This posting is provided “AS IS” with no warranties, and confers no rights.