With BizTalk 2006 R2 rounding the corner into the home leg, the folks in the CSD (Connected Systems Division - Biztalk, .NET, WCF, WF) have been very busy!! :)

We're looking down the telescope at BizTalk 'vNext'.

It's current name is 'BizTalk Internet Services' which offers a bunch of services for the 'cloud' (aka internet based wcf services). My personal favourite is the relay service.

Alot of functionality that previously existed in BizTalk has been pushed down into the .NET framework 3.x/4.x (WCF Services etc.)....allowing the BizTalk team to focus on some really cool new BizTalk features.

Here's an email I got earlier from Marjan from MS.

----------------------------------------------

As you may have heard, for the past year the Connected Systems Division has been incubating a set of building-block services that will shape the next generation of application development.  On Tuesday the 24^th, we will open the incubation of BizTalk Services to the public by inviting developers from all over the world to use the services and provide feedback. 

BizTalk Services will be available via labs.biztalk.net.  (UPDATE: OPENS 24th Tues - US TIME)

What are BizTalk Services?

These services, which have been in internal incubation for the past year, represent hosted versions of some technologies developed in the Connected Systems Division.  Included in this set of services are:

o Message routing – think of this as firewall friendly B2B messaging (Available now)

o Simple publish/subscribe event brokering – Pub/Sub at Internet scale (Coming soon)

o Simple federated identity and access control  (Available now)

o Workflow processes – Simple templates for cross-organization integration and the orchestration of business processes interacting with multiple services (Coming soon)

(Just had to stick 'The cloud' image in :)

Through the MOSS/WSS v3.0 TAP program and the early betas, there was a whole bunch of 'debug' type messages being logged.

I've always loved the MOSS/WSS V3.0 log files - under ...\12\Logs\.... as there's some very funny error messages. Here's such one

04/23/2007 04:50:51.09 w3wp.exe (0x152C) 0x1650 Windows SharePoint Services General 8l1n High An SPRequest object was not disposed before the end of this thread. To avoid wasting system resources, dispose of this object or its parent (such as an SPSite or SPWeb) as soon as you are done using it. This object will now be disposed. Allocation Id: {65D8E0A2-C330-418A-8871-C597A7C612C9} To determine where this object was allocated, create a registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\HeapSettings. Then create a new DWORD named SPRequestStackTrace with the value 1 under this key.

I recently got an email to inform me I was able to participate in the CSD Technology Advisors program.........

Basically I can sit down and give MS feedback on what works, what doesnt - "the button should be moved over 2cms".....
Specifically about BizTalk, WCF, WF, .NET 3.x, 4.x oh and did I mention BizTalk??

I've had an interesting discussion this week with some of my fellow BizTalk MVPs and also a few MS folks.

Here's the crux of my beef.
1. Stop a Send Port or Orchestration - it is still Enlisted but in the Admin Console it's stopped. (at this stage - you're stopped and my 'stopped' are the same)
2. Shoot a message into BizTalk destined for the stopped Send Port or grab one of the queued up Suspended-Resumable messages and say "Resume" (mind you, you do have other options here of Resume in Debug Mode etc)
3. Guess what happens?? BizTalk Queues the message up as it knows the corresponding Send Port is stopped???? NO!!!!! BizTalk will send the message through the STOPPED send port - (bang head against wall)
4. This 'feature' IS useful for when BizTalk receives a flood of msgs and an issue arises downstream (backend system or so) and you can 'trickle feed' A msg to the back end system.
5. I think this functionality should be tied into some sort of 'Resume for Debug' type wording. Something to indicate that it's an 'unusual' circumstance.
6. The terminology within the Admin Console is what I have an issue with. The port is Stopped, an NT Service is STOPPED, an application is 'stopped' - so these terms of stopped differ in the biztalk world.
7. Outcome of the week's discussion: MS are looking into changing the terminology within the Admin console.

Examining and Building an R2 Adapter using the New R2 Adapter Framework 

Wednesday, 2nd May 2007
6:00 PM Food and Drinks, 6:30 PM Kick Off
1 Epping Road, Microsoft
North Ryde, Sydney

Hi all on our Post Anzac Day Wednesday meeting and I hope two-up was (will be) kind to you. This month we’re at Microsoft North Ryde with a presentation on Adapters, Adapters and more Adapters. The new BizTalk Adapter Framework is called The Line Of Business Adapter Framework SDK (LOB Adapter SDK between friends) and is based on Windows Communication Foundation(WCF). As you can imagine, WCF adds a ton of functionality around the way we do messaging.

With BizTalk 2006 R2 comes many new features and improvements we examine R2 .NET Adapters (WCF Based) and also look at new WCF and WF BizTalk BAM Interceptors, allowing you to post to BAM directly from WCF or WF.

I've provided a calendar appointment for your calendars so join me.

Presenter:

Mick Badran, BizTalk MVP who specialises in Microsoft Technologies as a Solutions Architect/Developer. With over 15 years consulting experience and 12 years as a Microsoft Certified Trainer provides in depth real world knowledge.

Session Details

So what is the story with Integration and Adapters in BizTalk 2006 R2? This session covers the roadmap going forward in building BizTalk .NET Adapters (those based on WCF) in the new Framework. It will discuss all the benefits of the new framework and explain options on where to host these adapters.

We will also examine the relationship between BizTalk and the WCF based adapters with respect to Message Contexts, and multipart messages.

The Session details are as follows:

1.     R2 WCF Adapters Explained – including the new BAM Interceptors for WCF and WF

2.     LOB Adapter SDK framework explained

3.     Building a new Custom Adapter using the LOB Adapter SDK

As always love to hear from you and what's been getting you excited at work.

Who Should Attend?

If you're looking to get additional business related information out of your Biztalk processes then this session is for you.
This session is technically focused for Biztalk developers and System Architects.

Please be sure that you RSVP so we know how many to expect. Reply with a yea or ney to mickb@NOSPAMbreezetraining.com.au

Looking forward to seeing you there at Microsoft Premises - North Ryde
Mick and Mark 
Ph: 0404 842 833 (Mick's mobile)
SydBiz.Org

Earlier this week I received an email from Anil Sanagavarapu who firstly is crazy about Cricket and the World Cup.

He mentioned that his company Iris Software is embarking on a cool RFID Services project.....

So we got chatting and I've just seen what they're doing around RFID using Microsoft RFID Services, was fantastic.

Specifically their solution implements:

1. Sync/Async reading of Tags
2. Enrichment of Tag data within MS RFID Services Environment, supplimenting Tag Info with data coming from external datasources in a high performance environment.
3. Optional emails of various tag events as the items go about their merry way.

The guys are looking to bring out some Video Content around their solution and project based on their experiences. They will provide a Walk through of Microsoft RFID Services, how to develop and implement solutions.

Looking fwd to that - great work guys!

Cheers,

Mick.

With over 6000+ EDI schemas and a brand new home grown EDI engine that WORKS!!!! (like BTS2000/2002 days)

Here's a great article that talks about the support for various schemas from the BizTalk Team.
http://blogs.msdn.com/biztalkb2b/archive/2006/10/14/edi-support-in-biztalk-server-2006-r2.aspx

---snip ---

EDI support in BizTalk Server (BTS) 2006 R2

Hello all:

BTS2006 R2 provides for design and run time support for six encoding standards and includes over 8000 ‘standard’ XSD schemas 'in the box' ready for implementation. Please do understand that these schemas will only operate with EDI systems in BTS 2006 R2 and are not compatible on Base EDI Adapter (BTS 2004 and 2006 versions). In forthcoming topics I will include documentation on how to modify/customize these schemas.

One of the most asked question is the on a listing of the Version/Release schemas supported in BTS2006 R2 – Microsoft EDI. So here goes: