Category Archives: Azure

Azure, BizTalk, Blog , , , Leave a comment

BizTalk Integration Summit 2013 Recap

By Nick Hauenstein

The week before this last holiday week was quite a time to be in the BizTalk world. The BizTalk Integration Summit 2013 kicked off at the swanky Fairmont Olympic Hotel in Seattle, Washington bringing with it a defined release cadence and roadmap, new cloud-based product announcements, and even a peek into the plans for the upcoming on-premise version of BizTalk Server.

The First Peek

The first peek into what the Thursday-Friday event would hold is captured in this agenda from the first day. The first day contained a single track of content, where all attendees would be able to experience the same messaging and presentations. The second day provided two tracks for those who wanted to chose their own adventure.

agenda

Familiar Faces & New Faces

The man in the Red Polo himself – Scott Guthrie kicked off the event – and also took the opportunity to announce the general availability of Windows Azure BizTalk Services. To clarify, it’s real and released – no longer in preview – but also not a static unchanging thing (as we will see later).

scottgu

We also had a new face bringing the initial welcome – Mark Moritmore. He’s the man behind the event, having received the torch passed by Kent Brown (who is now working with NY-based integration powerhouse Nimbo). This guy is passionate about the product, and is a long-term thinker. He’s exactly what BizTalk needs as organizations continue to choose BizTalk Server and Windows Azure BizTalk Services for mission critical integration applications that are expected to have long lifespans.

mark

Updated WABS SDK

The announcement of the general availability of Windows Azure BizTalk Services left me itching to get the bits, and “play” with them for lack of a better term. However, all the turkey from Thanksgiving put me a week behind the times and I just had a chance to download/install the freshly released SDK last night. One of the changes I noticed right away (from the last time I had installed one of the preview SDKs), is that I wasn’t having to hunt for miscellaneous MSIs to install the pre-requisite components. The new streamlined setup just makes it happen (though you’d better have a SQL Server or SQL Server Express instance handy if you’re planning on using the BizTalk Adapter Service – it’s not going to do that for you).

auto_install_dependencies

One of the other things demoed at the summit was the BizTalk Service Explorer Visual Studio Extension. This is a nice little plug-in for the Server Explorer window that allows you to interact with BizTalk Services artifacts in really cool ways (e.g., submitting a test message without leaving Visual Studio). While the UI looks/feels clunky at times, it definitely gets the job done. After seeing it, this will be on my list of extensions to install by default.

biztalkservice_explorer

Misc Thoughts About WABS GA

Looking at WABS from the perspective of migrating existing on-premise solutions to the cloud, I’m not sure the story is really complete there (and that’s not some huge secret – WABS is still in active development, and upcoming changes will erase most of the concerns I’m about to mention).

First, as noted in an earlier post, I did have some expectations around the map upgrade tool that still weren’t really met with this release. I had at least hoped the limitations in the preview would not be seen in the final release, or that I would get happier results than I was seeing before out of the tool at the very least.

Another tool that ships with the SDK is a TPM migration tool (essentially to move parties/profiles/agreements to the cloud. While this is actually done pretty well, there is still some mismatch in capabilities (e.g., EDIFACT is available on-premise, but is still a future delivery for WABS) that will prevent moving all solutions.

I took a look at the X12 schemas while thinking through some integrations I’ve worked on in the past, and noticed an absence of the schemas used for HIPAA sub-document splitting. To be fair, I haven’t actually had an opportunity to test to see if that functionality is present (for the most part the schemas are 100% clones of the on-premise schemas, so maybe those extensions are implemented in the WABS version of the EDI Disassembler), but it’s not looking promising. So those integrations would potentially stay on-premise as well.

Another thing that makes me more than a little bit uncomfortable is the direct deployment from Visual Studio. I’m hoping we will see more solutions like Michael Stephenson’s AppFx.ServiceBus.Build that will make deployment a happier experience (and hopefully a fully automated one that doesn’t live in Visual Studio).

That’s not the end of the story though. I don’t intend to write this in such a way that it seems I’m saying that WABS is somehow unsuitable. Instead these are the places where there is still work to be done – and I’ll emphasize again – work is being done. EDIFACT support was confirmed as coming, along with a new rules engine (with new tooling), support for Windows Workflow Foundation workflows, AS2 support, and other fun extensibility points (e.g., BAM-like tracking, easy to build/lightweight adapters). So we’re getting a better B2B story, and also starting to see the seeds of a BPM story emerge within WABS.

Essentially WABS is doing great things already (for straight-forward X12 integrations built fresh for WABS), and will be doing even better things in the future.

BizTalk 2013 Updates Since Release

Another point of discussion was the present state of BizTalk Server 2013 on-premise, as well as a road map for the future. Since the release of BizTalk Server 2013, the BizTalk team has been hard at work, and shipping updates and new functionality (e.g., HIS 2013, which had been delayed due to close work between the product team and TAP customers to get everything happy and ready for release).

2013updates

BizTalk Futures (2013 R2 and Beyond)

Looking to the roadmap ahead, the team made a commitment to a release cadence (that in a way is a continuation of what we have already seen, but which hadn’t so much been publicly formalized). The release cadence going forward will see:

  • Major BizTalk Server release every other year
  • R2 BizTalk Server release every year there is no major release
  • Cumulative update package each quarter
  • WABS refresh each quarter

release_cadence

Looking at this slide, I feel like I’m looking at a description of the release cadence for Visual Studio. Which is nice, because in a way this provides some level of guarantee that I’m going to be able to develop BizTalk Server artifacts in vLatest of Visual Studio (give or take a few months in this case).

As part of the commitment to this release cadence, an announcement was made for BizTalk Server 2013 R2, which will bring:

  • Platform alignment
  • JSON Support (so much for all that work writing pipeline components!)
  • Proxy support for the SFTP adapter (as well as SSO support)
  • Authentication improvements for Service Bus
  • Healthcare Accelerator Improvements (slides to follow with specifics)

2013r2features2013r2features2

Exciting Road Ahead

When you get down to the bottom of it, it really is an exciting road ahead for BizTalk Server. I had a lot of fun this year at the BizTalk Integration Summit, and I’m hoping that this becomes an annual tradition and opportunity for the BizTalk community to come together in-person, and have a dialog with the team that’s building the product and service.

Before I close this post out, I want to give a shout out and thanks to everyone that stopped by our table and has found themselves sporting a new tablet cover with the QuickLearn Training logo (spread the love!), and a thanks to everyone who made it to our party at the Rock Bottom Brewery – lots of good times and good conversations were had there!

If you want to get some other perspectives on the summit, Saravana and Steef Jan (among others) beat me to the punch and have offered their thoughts here:

Well, it looks like I don’t have an excuse to sit in this restaurant any longer (one of the upper floors of a seemingly endless concourse at DEN). I’m going to go catch the rest of my flight out to Houston (completely different part of Houston than last time) to teach some TFS this week, and I’ll be back in short order. Until then, take care!

Azure, BizTalk, Blog , , , , 4 Comments

Mapping Code Pairs in the WABS Mapper

By Nick Hauenstein

This post is the twenty-third in a weekly series intended to briefly spotlight those things that you need to know about new features in BizTalk Server 2013.

Assuming that one of the major benefits of using Windows Azure BizTalk Services is being able to offload some of our EDI processing to the cloud, then a major use case for the new WABS mapper becomes EDI mapping. One of the fun tasks that comes out of that is dealing with code pairs (if you’re interested in the on-premise side of this problem, the best coverage to date is found here). In this post, I’m going to examine how one might approach this problem using the new tooling available in the WABS SDK.

Give Me an Example of Code Pairs

Maybe you’re reading this and thinking to yourself, “I don’t really care about EDI, but WABS looks interesting,” and you still want to be able to gain something from this discussion without getting buried in the esoterica that is EDI. If that’s the case for anyone out there, here’s an example of the problem I’m going to try to solve using the WABS mapper.

We have an input that is a repeating record of items where there is a qualifier that describes that type of item we’re looking at, and a value that provides the value of the item. Consider this schema:

image

Here we have (at some point in the schema) a list of phone numbers, identified by a Type field element (our qualifier) and the Number field element (our value). The Type field is defined as follows:

image

We have an output that is a flat listing of items where we have a set of fields representing a few of these different types of numbers:

image

So what we are trying to do is iterate through the list of numbers in the input, map over the value for the item with the qualifier Mobile for the CellNumber output, and grab the value of the Home qualified number and toss it into the HomeNumber output field. It’s something that looks trivial, and yet is annoying to do en masse using the BizTalk Mapper:

image

In a Land Without FLATTENING Value MAPPERS

So what does this look like when brought over to the land of WABS using .trfm style maps? Well, looking into the toolbox, we do have an item called Conditional Assignemnt, which is essentially a Value Mapper:

image

If we run with that (combined with some Logical Expression map operations, we end up with something like this:

image

Unfortunately, this isn’t a Value Mapper (Flattening) type map operation. As a result, this actually will only work if we are interested only in a single qualifier, and that qualifier happens to show up in the first code pair that appears in the document.

So what do we do now? Do we reach to XSLT and code it up by hand (after-all, it is super easy to pull off)? Let’s take a look at how the migration tool that comes with the SDK handles this scenario:

image

It adds two MapEach operations to the map, that are configured something like this:

image

As you can see, the MapEach was made to be conditional upon the Type field element being compared to a constant string input. However, this conditional check is repeated inside the MapEach operation within the chained Logical Expression and Conditional Assignment map operations. While the map technically works as generated by the tool, it looks horrible, and it really feels like there ought to be a better way.

Another Approach

If you don’t want to use the MapEach approach (which really wouldn’t be so bad if our two nodes weren’t hanging out at the root as siblings), then we can take advantage of the ability of the new mapper to generate lists of items in memory while working through the mapping (really this is kind of similar to the Table Looping and Extracting functoid).

In order to make that happen, we use the Create List map operation, and then at some point inside include the Add Item operation to add items to the list. The Create List operation is configured to include the names of the fields of each item in the list. It then includes the ForEach operation with a nested Add Items. The ForEach is pointed to by the parent repeating node of our code pairs. The Add Items operation is pointed to by each value we want to include for each source item:

image

Here’s what the configuration of the Create List map operation looks like:

image

Once we have the list created, we can select values out of the list using the Select Value operation (in fact we’ve used two of them):

image

Does it Work?

Technically, both approaches worked, and took this input, and generated the output shown below it:

image

image

I’m going to be honest here, it still feels comparatively clunky, and I’m probably going to be reaching for that XSLT override pretty frequently. That is, unless there’s yet another way that’s cleaner and more simple than those presented thus far (this is one of those posts that I hope to revisit in the future with a correction showing an even better way to approach the problem).

Next Week

Next week, I will be wrapping up this series and shifting focus back to day-to-day BizTalk Development and all the fun things that we’re actively working on there.

Until then, happy mapping with shiny new tools!