BizTalk Server 2006 R3 Announced

23 באפריל 2008

BizTalk Server 2006 R3 Announced

Today, Steve Martin announced in his post BizTalk Server Platform Updates a few details about the next version of BizTalk2006 (that will be available in early 2009) Called BizTalk Server 2006 R3.
It seems that once SQL Server 2008 becomes generally available, an updated version of BizTalk Server 2006 is expected to be released.  BizTalk Server 2006 R3 is designed for Windows Server 2008, the .NET Framework 3.5, Visual Studio 2008, and SQL Server 2008.

new investments in the release include:

  • New web service registry capabilities with support for UDDI (Universal Description Discovery and Integration) version 3.0
  • Enhanced service enablement of applications (through new and enhanced adapters for LOB applications, databases, and legacy/host systems)
  • Enhanced service enablement of "edge" devices through BizTalk RFID Mobile
  • Enhanced interoperability and connectivity support for B2B protocols (like SWIFT, EDI, etc)
  • SOA patterns and best practices guidance to assist our customer’s implementations

To ensure existing BizTalk Server 2006 applications continue to run without changes,  an incremental approach by limiting the changes to the items listed above was taken.
Because this release is built on existing bits, the name of this release will be BizTalk Server 2006 R3.

הוסף תגובה
facebook linkedin twitter email

להגיב על Eric Stott לבטל

האימייל לא יוצג באתר. שדות החובה מסומנים *

3 תגובות

  1. Eric Stott24 באפריל 2008 ב 7:49

    I am excited to learn about the new features…

  2. Israel Master3 במאי 2008 ב 1:54

    We are developing mobile RFID solutions and we would like to learn the BizTalk RFID Mobile features.

  3. Muhammad21 ביוני 2012 ב 21:55

    This type of data is a little more calihenglng to store in the catalog as it is always changing with customers. You don't want to be creating one-off products every time you get a new customer. There are probably a few ways you could do this, but one way would be to create some additional fields at the order level (form and line item) and persist the customer specific data when the item gets added to the basket. This data will then get persisted to your completed Purchase Order. Another way might be, if the customer data you're capturing is similar enough you could create a profile for the customer and store the data in some custom profile attributes. As for calculating the premiums, this will involve some custom logic regardless of how you do it.Another way might be to create custom properties on your insurance products in the catalog. These custom properties would only serve as a sort of list of the type of details you need to capture. Each new property could also have an associated cost as well that could be used to calc the total premium.Hope this helps a little!