Interesting BizTalk Error – When’s a receive location not a receive location?

Interesting BizTalk Error – When’s a receive location not a receive location?

Today in class (in the beautiful city of Perth 🙂 I was busily going through a class
demo in BTS06 R2(Feb CTP) and I created a Project having:

  1. BizTalk project
  2. Test App
  3. BizTalk Wizard Published WCF Service hosted in IIS.

I then needed to give this out to the 12 students in class, so I (some something quick):

  • zipped up the project + Test App
  • exported the Bindings info (via a MSI)
  • Seeing I had made a few changes in IIS to the virtual directory/web app created I
    decided to use IIS Mgr, select the Virtual Directory, then under ‘Tasks….’ select
    ‘Export to Config file xml’ option

    This essentially saves the metadata (that’s normally placed in the IIS metabase) into
    the file – I envisaged the students would be able to ‘Import XML IIS Config file’
    and be done with it……….

    nice thoughts……

After all was said and done, the error we got was something like “Receive
location /SERVICES/WCFSERVICE/page.svc” could not be found.

All was inplace and worked on my machine…..we did discover what the problem was
and moral to this story…..

“/SERVICES/WCFSERVICE/page.svc” is treated differently to

“/Services/wcfService/page.svc”    (this was the actual BTS receive
location path settings for the ‘basicHttpBinding’.

Solution:

– either change the BTS receive location to capitals….or….recreate the Virtual
directory under IIS…..or……modify the virtual directory config.xml file.

Now we know……fingerscrossed

WCF Performance Comparisons

One of the most common questions I get while teaching WCF is “how does WCF stack-up against the existing distributed technology stacks (ASMX, WSE, COM+, .NET Remoting) in terms of performance and throughput?” This whitepaper, written by Saurabh Gupta, offers some answers. [Via Paul Andrew]
I love the comparison between message-based security and the mixed mode where you secure the transport and use message credentials for authorization. According to this study, mixed offers 2.5x more throughput than message security (using WCF for both), and about 10x more than using WSE 2.0. I think mixed mode will end up becoming the sweet spot for many scenarios.

Welcome Fran!

I haven’t blogged a lot since two weeks, but this time there’s a reason: last week I became the very proud father (1st time!) of our beautiful daughter Fran. Last week was very hectic but now everything is stabilizing (at least that’s what I hope); she is getting to know us and we are getting to know her habits. Everything they say about having children is true: it changes your life … instantaneously and dramatically. But she is so beautiful, for more pictures check her “blog” (created in WSS v3 of course), it’s in Dutch only.

BizTalk 2006 R2 Beta 2 is Out

BizTalk 2006 R2 Beta 2 is Out

News is already out: Beta 2 of BizTalk 2006 R2, the first public release, is available for download. Just go to Connect and sign in to BizTalk Server 2006 R2’s program.

If you want to know what’s new in this release, I direct you to my presentation at TechDays 2007, a few days ago, available here.

This beta includes the BizTalk 2006 R2 package itself, comprising:

  • BizTalk EDI
  • BizTalk RFID
  • BizTalk WCF Adapter
  • WCF and WF Interceptors
  • BTS 2006 Accelerators
  • BTS 2006 V1 LOB Adapters
  • Product Documentation and Tutorials

As well as the .Net Line-Of-Business Adapters:

  • .NET LOB Adapters
  • Siebel Adapter
  • SAP Adapter
  • Oracle DB Adapter

And the WCF Line-Of-Business Adapter SDK.

Important to notice is that these 3 will have different release dates for the RTM versions, and that this beta 2 is an unsupported beta release. You can head for the forums for community support.

BizTalk 2006 R2 Public Beta released

So now everyone gets to play…!
Announcement is here.
Download it from here (you’ll
need to register for Microsoft Connect and/or sign in – but it’s free to register).
If you download everything, it’s a 558MB download.

This the Beta2 version.

So download it, and go play with all the WCF goodness…

What’s new in R2?

I’ll have a play with this new Beta and blog about my findings soon.

Public Beta for BizTalk 2006 R2 has released!


 


We are pleased to announce the public Beta 2 release of BizTalk 2006 R2.  The beta 2 files are available from the Microsoft Connect site.   While there are numerous improvements to BizTalk, this release has three major themes:


 



  • EDI: The native support for comprehensive EDI and AS2 protocols in BizTalk Server 2006 R2 will provide much richer data integration and management capabilities for our customers. The Base EDI adapter that comes with BizTalk Server 2006 enables the sending and receiving of messages using X12 and EDIFACT. Customers can leverage this base functionality in order to build custom EDI solutions.

 



  • RFID: BizTalk RFID provides rich data, device and event management, as well as open APIs and tools.  The capabilities allow customers to cost effectively build vertical solutions and configure intelligent RFID-driven processes. 

 



  • Platform Alignment: BizTalk Server 2006 R2 features improved alignment with 2007 Microsoft Office system and Windows Vista, including key .NET Framework 3.0 technologies such as WF and WCF.  This alignment will help customers access LOB data, as well as system-to-system or supply-chain processes from within their Office System applications (like SharePoint Server, InfoPath and Dynamics). 

BizTalk Server 2006 R2 Beta 2 is an unsupported beta, however there are community-based support forums available for the release.


Regards,


Marjan Kalantar

Testing Multi-part Map

Recently I was debugging an orchestration and found unexpected output from the map. The obvious decision was to use Visual Studio’s “Test Map” option. I opened the Map and realized that “Input” schema is multi- part schema.
 
Combining two xml messages into one file will produce the multiple roots exception. So, I looked at the […]