Brian Loesgen's Blog

BizTalk Server, Enterprise Service Bus (ESB), SOA, Oslo, Dublin, WCF/WF... and related stuff!

  Home  |   Contact  |   Syndication    |   Login
  142 Posts | 0 Stories | 152 Comments | 81 Trackbacks

News

Tag Cloud


Archives

Post Categories

Image Galleries

My Blog Friends

I'm a bit late because of my extended bout of 100% travel, much of it disconnected, but I thought I'd do a post about this anyhow because it is a very significant piece of news.

Microsoft has announced that what was previously being called BizTalk Server 2006R3 has been renamed to BizTalk Server 2009.

Why is this announcement important? Because, if you've been following my blog and others, you know that Oslo and a wave of other technologies is heading towards us, and that there will be a first-release of some of this at the PDC in October. Many people are probably wondering: what does this mean to existing BizTalk customers? Are their investments protected? Is there a migration path? Is migration something that needs to be done? The BizTalk Server 2009 announcement should go a long way to reassuring people that their investments are protected, and that there is a BizTalk future in Oslo-land.

In the announcement, Microsoft also reaffirmed their commitment to continuing to release new versions of BizTalk Server at 2 year intervals.

Key highlights of what will be in BizTalk Server 2009 are:

  • Support for Windows Server 2008, Visual Studio .NET 2008 and SQL Server 2008
  • Support for Hyper-V virtualization
  • A new version of Microsoft's ESB Guidance (more on this later, it's an impressive release)
  • UDDI 3.0
  • Team Foundation Services integration (MSBuild)
  • EDI Enhancements
  • RFID support for LLRP protocol, TDT standard, and Mobility stack
  • New SQL and Oracle Apps adapters
  • Upgrades for .NET 3.5 compatibility
  • SWIFT enhancements

 

For more info:

 

Technorati Tags: ,,
posted on Thursday, September 25, 2008 3:33 PM

Feedback

# re: BizTalk Server 2009 announcement 9/28/2008 3:33 PM kumar
i wanted to suggest some more features in BizTalk, then BizTalk product development team can notice these problems in current version of BizTalk server 2006 r2-
1. In BizTalk rule engine, there must be fecility of nested if statement rules or else condition.
2. Mulitple version rules calling in call rule shape, automated priority setting for rules policies(based on condition like season shopping rates...etc). More ease/simple way to Calling BizTalk rules with .net coding(GUI). More GUI based features in BRE like other third patry Business rules engine/composers.
3. Giving less burden on middileware BizTalk developer ratherthan TFS/ Coding stuff. If this seperation is there then there will be seperate work area for BizTalk developer and .Net developer/TFS developer/all. This is the major drawback for BizTalk middileware development or code dependency over other Microsoft sub technologies. This is taking more time consuming ratherthan other middileware technologies in middileware market. Then development time is also take less time ratherthan other middileware technolgies.
4. There must be standard BizTalk Pattren wizard (which support failed messsage/pipeline/error handling, correlation, compensation, bam, Bas, convoy, direct binding, intterput, fault tolerance/handling in orchestrations services, ESB....real pattrens etc). This will reduce devlopment for projects timeline.
5.Automated testing tools for BizTalk orchestration/pipelines/adapters/schema level unit testing with out third party unit testing tools within Visual studio IDE.
6. Integrated Load/performance tools for load/stress testing BizTalk applicatons within Visual studio IDE with interuption support of suspened messages or zombies.

hope & See u later in BizTalk server 2009....

# re: BizTalk Server 2009 announcement 10/26/2008 12:18 PM Xin zhang
The first thing we need is to fix the the orchestration design window. Like WF, we surely need to be able to zoom in-out and drag-drop capability. In WF design, there is the toolbar in the bottom right to achieve it.

WE NEED TO HAVE IT IN BIZTALK AS WELL!!!

Post Feedback

Title:
Name:
Email: (never displayed)
Url:
Comments: