BizTalk 2009 Service Pack 1 - Wish List

Here's my BizTalk 2009 Service Pack 1 wish list:

- Modify the Mapper tool to be able to add and edit multiple source schemas (Multiple source schemas can be added when using the Transform shape in the Orchestration designer), but not in the BizTalk mapper tool; and currently when trying to edit a map with multiple inputs you have to re-create a map from the Transform shape.

-Fix the references problems in Visual Studio. VS seems to lose the references from other BizTalk projects in the same Solution after some builds. The only way to solve this problem is by either restarting Visual Studio and/or adding/removing references together with a Clean in VS.
I have seen a lot of other similar problems posted in forums/blogs (e.g http://dotnet.org.za/ryancrawcour/archive/2009/07/17/biztalk-2009-amp-visual-studio-2008-annoyance-2.aspx)

-There's also some issues around copy/paste within the solution explorer (when copying Maps and Orchestrations from one BizTalk project to another), after which copied files are not building.

-Visual Studio & ESB Toolkit 2.0 - in a BizTalk project when right clicking the project and selecting "Add New Itinerary" it opens a dialog only with options to add Maps, Orchestrations etc. It should open up a new itinerary designer. This works though in a C# Class Library project.

The software I currently use and experience these problems with is:

-Visual Studio 2008 SP1
-BizTalk Server 2009
-ESB Toolkit 2.0

I will update this post with more items to my BizTalk 2009 SP1 wish list. Feel free to add to this list!

Freddie

Cool Magazine - http://biztalkhotrod.com/

I came across this site recently- http://biztalkhotrod.com/

These guys publish a BizTalk magazine every few months about BizTalk topics of interest, how-to acticles etc, with a HotRod look and feel!

From what I have seen, very cool BizTalk articles and informative information and also a great idea for a magazine, combining BizTalk with HotRods!

Refer to the website for more information and previous publication downloads as PDF documents.

F.

BizTalk 2009 / Oracle Adapter - Authentication Issue

This is my second post about my current project experience building an integration solution using BizTalk 2009 and the ESB Toolkit 2.0.

This was one of the other issues we encountered using the Oracle Adapter for BizTalk- we were getting Oracle authentication problems/errors from the BizTalk space.

The Oracle User Names must be in upper case UPPERCASE!

We were able to use a successfuly connect using a lower case user name in the Oracle Tools (like Enterprise Manager and SQLPlus) to the Oracle database, but doing this via the Add Adapter metadata in Visual Studio for example using the same lower case user name as we did for Oracle Enterprise Manager and SQL Plus, just gave us errors, specifically this error below:

"ORA-01017: invalid username/password; logon denied."

The only way we could get a successful connection from BizTalk to Oracle using the Oracle adapter was to send through the username in UPPERCASE!

We also encountered some other roadblocks in using the Oracle adapter in BizTalk, things like Oracle driver issues and installation/configuration blues. I will give more info in a coming blog.

 Freddie.

There was a failure executing the receive pipeline: "Microsoft.Practices.ESB.Itinerary.Pipelines.ItinerarySelectReceiveXml" ... does not match any of the given schemas

This week I encountered an issue using BizTalk 2009 and the ESB Toolkit 2.0 using the standard ESB.ItineraryServices.Response.ProcessItinerary webservice as on ramp.

The problem came in when using an ESB pipeline which uses an XML Disassembler as a pipeline component, specifically in the ItinerarySelectReceiveXml pipeline.

When submitting my XML request to the ProcessItinerary web service/the standard OnRamp.Itinerary.Response.SOAP receive location configured to use the ItinerarySelectReceiveXml pipeline I received this error below:

There was a failure executing the receive pipeline: "Microsoft.Practices.ESB.Itinerary.Pipelines.ItinerarySelectReceiveXml, Microsoft.Practices.ESB.Itinerary.Pipelines, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML disassembler" Receive Port: "OnRamp.Itinerary.Response" URI: "/ESB.ItineraryServices.Response/ProcessItinerary.asmx" Reason: Document type "XXX#Root" does not match any of the given schemas.

The problem was not due to a deployment issue, my schemas were deployed and only 1 schema existed for any given schema type. I also tried to use the DocumentSpecName property on the pipeline configuration to force the pipeline to pick up my schema to validate against, to no avail.

I finally came across this blog by Richard Seroter explaining a similar problem with using a web service/receive location and a pipeline that validates XML.
http://blogs.msdn.com/richardbpi/archive/2006/09/15/Fixing-_2200_SOAP-_2F00_-Envelope-Schema_2200_-Error-In-BizTalk.aspx

So... who to fix this?

I went to the  "C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Web\ESB.ItineraryServices.Response\App_Code" folder (default ESB Toolkit install) and edited the "ProcessItinerary.asmx.cs" file, commented out the current bodyTypeAssemblyQualifiedName="XXXXX" line and gave the bodyTypeAssemblyQualifiedName a null value like this below:

I then just did an IIS restart and my problem was solved!