After a very valuable and interesting TAP (Technology Adoption Program) process, a public beta of BizTalk Server 2009 is now available at https://connect.microsoft.com/site/sitehome.aspx?SiteID=218 . In unison, the CTP of the ESB Guidance Toolkit v2 is Read More……(read more)
Microsoft announced the public BizTalk 2009 beta today. You can snag it from the Microsoft Connect site. I’ve been running BizTalk 2009 on a VM since late summer, and while you don’t notice a whole lot of differences, there are some subtle things that you’ll notice. Recall that the big ticket features are platform specific […]
Do you wish you could open your presents before Christmas?
Your wish has come true! Microsoft has announced the release of BizTalk 2009 CTP, and it’s available at https://connect.microsoft.com/site/sitehome.aspx?SiteID=218. The updated Enterprise Service Bus (ESB) Guidance is available at http://codeplex.com/esb.
Details
With the public beta release of BizTalk Server 2009, Microsoft is delivering the first customer preview of the multi-release road map announced in September 2008 and is giving customers the first look of the feature-complete download. BizTalk Server 2009 supports the latest Microsoft application platform technologies, including Windows Server 2008, Microsoft Visual Studio 2008 SP1, Microsoft SQL Server 2008 and the .NET Framework 3.5 SP1. BizTalk Server 2009 also delivers expanded new connectivity options including new integration with Oracle Corp.’s E-Business Suite, as well as updated platform support for the most recent versions of IBM Corp.’s Customer Information Control System (CICS), Information Management System (IMS), DB2, DB2/400, DB2 Universal Database and WebSphere MQ.
Customers will also benefit from BizTalk Server updates in key enterprise focus areas, including connectivity, visibility and platform support, which extend their investments in existing infrastructure, people and applications. BizTalk Server 2009 also delivers improved scalability and reliability through support for SQL Server 2008, Windows Server 2008 Hyper-V virtualization and enhanced failover clustering. It provides significant new enhancements to both individual and team productivity by enabling new interoperability with Microsoft’s application life-cycle management (ALM) solution Visual Studio Team System and Team Foundation Server. This allows development teams to utilize the integrated source control, bug tracking, team development support, Project Server integration, and support for automating builds via MSBuild for a more seamless development and testing experience.
BizTalk RFID Mobile also extends the power of BizTalk Server RFID to mobile devices running Windows Mobile and Windows CE. In addition, BizTalk RFID Mobile delivers simple device management and offline processing capabilities, all of which help reduce the total cost of ownership.
In addition, customers and partners can now expedite development of RFID applications in heterogeneous environments with BizTalk Server support for RFID standards, Tag Data Translation (TDT) and Low Level Reader Protocol (LLRP). Also being released today is a community technology preview of the ESB Guidance 2.0, which delivers updated prescriptive guidance for applying ESB usage patterns with improved itinerary processing, itinerary modeling using a visual domain-specific language (DSL) tools approach, a pluggable resolver-adapter pack and an enhanced ESB management portal.
BizTalk RFID Mobile is available at no cost to all BizTalk Server customers with Microsoft Software Assurance as well as new BizTalk Server customers who purchase an edition of BizTalk with Software Assurance. When BizTalk Server 2009 becomes generally available, customers will be able to acquire BizTalk RFID Mobile as part of the software license.
From the connect.microsoft.com Site:
|
BizTalk Server BizTalk Server 2009 represents the next release in Microsoft’s long-term strategy to enable the connected enterprise. BizTalk Server 2009 enhances enterprise connectivity with broad industry support of WS* protocols, the edge via Microsoft BizTalk RFID, and business partners though EDI. What’s new in BizTalk Server 2009?
%u00d8 Simplify Interoperability %u00fc Support for .NET Framework 3.5 SP1 and Visual Studio 2008 SP1 – take advantages of the latest developer tools. %u00fc Support for Windows Server 2008 and SQL Server 2008 – full support of Hyper-V, and increased performance and scale. %u00d8 Extend To The Edge %u00fc EDI – enhanced out of the box support for the most commonly used EDI schema and trading partner management tools. %u00fc Simplify development of mobile applications that expose relevant, real-time business information (RFID Mobile). %u00d8 Enhance Productivity %u00fc ALM – new support is provided for Team Foundation Server (TFS), allowing development teams to leverage the integrated source control, bug tracking, support for team development, Project Server integration and support for automating builds via MSBuild. %u00fc Enhanced Developer Productivity – improved underlying project system enhances debugging support for artifacts, pipeline components and orchestrations, and enables support for unit testing. Support %u00fc This beta is community supported. The TechNet forums will be the primary place for support – http://forums.microsoft.com/TechNet/ShowForum.aspx?ForumID=1470&SiteID=17. %u00fc This beta is for evaluation purposes only. It is not supported in a live operating environment. |
This application has been on blog for a while, and I'm happy to have got lots of feed-back. Apparently, I'm not the only one finding uninstalling/re-installing BizTalk assemblies to be challenging. You have to know the order of references between every assembly, along with ports that might be using the assembly you want to uninstall. If you have worked with BizTalk for a while, – I'm pretty sure you have sworn over this dialog in the past:
The BizTalk Undeploy Helper is an application I built for a customer, where they often deploy and undeploy large solutions. This might not an big issue when deploying from Visual Studio to your build environment. But this is seldom (at least in my experience) the procedure when deploying to an production environment. The recommended way is to add the binding files to your BizTalk Application resources before exporting the MSI package, and then set the Target Environment. If you then undeploy using the Add/Remove Programs, the assemblies and ports should be removed in the right order. However, I haven't found this to work that well when deploying multiple solutions to the same application(s), and that's pretty much why I developed this application. This is all very well described in a post by Stephen W. Thomas
Using this tool is pretty straight forward. First, select the assemblies to undeploy. By selecting one assembly, the tool marks all assemblies referencing the one you selected. You may also use the new feature of marking all unused assemblies. This might come in handy if you are updating the assembly version each time you deploy. –Use this option with caution. It's virtually impossible to determine if an assembly is used or not, so carefully examine the result before you undeploy.
Before you choose to undeploy, you'll be given a list of all assemblies and BizTalk artifacts related to those assemblies. You have the option to leave the ports, in which case the ports will be reconfigured to use passthrough pipelines and no in- or outbound transformations.
If you are working with a big solution, with assemblies deployed to multiple applications, you can save the uninstall configuration for later use. This way you don't have to reselect the assemblies the next time you undeploy. Just click the load button, and point to the configuration file.
IMPORTANT
If you choose not to run the application on the server, make sure the assemblies you're about to uninstall are deployed to the computer from which you're running the application. This is because the application needs to access the assemblies to get its dependencies.
Find it at CodePlex
I was asked: "How can I call into a Windows Service to get it's status?" A little more background said that status was to be retrieved by clients (a website) on the same machine. My response was to use WCF with the NetNamedPipeBinding. Since…(read more)
The papers in Sweden reported last week that resources with expert level knowledge on standard platforms and systems are hard to come by. In summary it says that its an emerging trend in Sweden to use standard platforms, but the fact that resources are…(read more)
BizTalk Server 2006 R2 has brilliant support for WCF out of the box; in fact I use it’s WCF based adapters almost exclusively now, unless I have a specific line of business system, like S.A.P / Microsoft Dynamics to connect to. It is really painless to Read More……(read more)
Yesterday I was hanging out at the Microsoft office in Los Angeles for an “Architecture Council” meeting on the new Cloud Computing platform. You can find the slide materials on the Strategic Architecture Council blog.
Overall, a worthwhile session that you should attend if you get the chance in your city. My favorite local evangelists were […]
My friend Jon Flanders‘ most recent book, RESTful.NET, is now available. Jon’s a masterful instructor, always doing a great job explaining technologies to the masses. I’d highly recommend this book if you’re doing anything with REST.
Great job Jon, and you’ve now forever associated catfish with REST 🙂