by community-syndication | Apr 28, 2009 | BizTalk Community Blogs via Syndication
My colleague, the ’Arch Hacker’, forwarded an email to me this evening from Kenton Price. Kenton had noticed some peculiar behaviour using the Microsoft Business Rules Engine. Here are the pertinent extracts from Kenton’s report:
“It appears that if you assert a fact in a rule, it hangs around for subsequent instantiations of the rule engine, behaving like a long-term fact…. I solved it by retracting each asserted fact on every exit path (I had a jump-out-early that halts and stops all other rules, so I had to retract the asserted facts here too)….Facts provided in the object[] passed to the BRE call are all retracted automatically. It appears that any others you assert within the rules must be manually retracted.”
Kenton is quite correct.The issue is actually to do with the Policy class, and there are good reasons why the engine behaves this way. Read more at http://geekswithblogs.net/cyoung/archive/2009/04/28/131548.aspx.
by community-syndication | Apr 28, 2009 | BizTalk Community Blogs via Syndication
Recently I got the following error while trying to write out a flat file. The way I resolved it was to remove the .dll from the GAC and resinstall the .msi.
Event Type: Error
Event Source: XLANG/s
Event Category: None
Event ID: 10025
Date: 4/28/2009
Time: 12:01:17 PM
User: N/A
Computer: YOURCOMPUTER
Description:
Uncaught exception (see the ‘inner exception’ below) has suspended an instance of service YOURPROCESSNAME’.
The service instance will remain suspended until administratively resumed or terminated.
If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
InstanceId: 3f85458e-35c0-4f56-bce9-c4dc7a054f5f
Shape name: Send msg_FlatFile
ShapeId: 65a1739e-9b12-41c2-abb1-1aa2776d2657
Exception thrown from: segment 1, progress 22
Inner exception: Failed while attempting to send message ‘msg_FlatFile’.
Exception type: SendFailedException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void WriteMessageState(Microsoft.BizTalk.Interop.IBTPEPInfoLookup, System.Guid, Microsoft.XLANGs.BaseTypes.XLANGMessage, Microsoft.XLANGs.Core.Segment, System.String, System.String, System.Collections.IList, Boolean, System.Collections.IList)
The following is a stack trace that identifies the location where the exception occured
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.WriteMessageState(IBTPEPInfoLookup pepLookup, Guid portId, XLANGMessage msg, Segment seg, String opname, String url, IList promoteProps, Boolean track, IList toPromote)
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXLogicalPortBinding.SendMessage(XLANGMessage msg, XlangStore store, Segment seg, OperationInfo op, IList additionalProps, IList toPromote, Boolean ignoreRoutingFailure)
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.SendMessage(Int32 iOperation, XLANGMessage msg, Correlation[] initCorrelations, Correlation[] followCorrelations, Context cxt, Segment seg, ActivityFlags flags)
at YOURORCH.segment1(StopConditions stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)
Additional error information:
Exception from HRESULT: 0xC0C01672
Exception type: COMException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void PostToSendPort(System.Guid ByRef, Microsoft.BizTalk.Agent.Interop.IBTMessageBatch, Microsoft.BizTalk.Agent.Interop.IBTMessage, System.String, System.String, Microsoft.BizTalk.Interop.IBTMMessageList ByRef)
The following is a stack trace that identifies the location where the exception occured
at Microsoft.BizTalk.Interop.IBTPEPInfoLookup.PostToSendPort(Guid& sendPortID, IBTMessageBatch batch, IBTMessage msg, String operationName, String url, IBTMMessageList& dlMsgList)
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.WriteMessageState(IBTPEPInfoLookup pepLookup, Guid portId, XLANGMessage msg, Segment seg, String opname, String url, IList promoteProps, Boolean track, IList toPromote)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
by community-syndication | Apr 28, 2009 | BizTalk Community Blogs via Syndication
Last month I blogged about a free end-to-end ASP.NET MVC tutorial called “NerdDinner” that I wrote for the Professional ASP.NET MVC 1.0 book from Wrox Press. The book is now released and shipping on Amazon.
The NerdDinner tutorial walks through how to build a small, but complete, application using ASP.NET MVC, and introduces some of the core concepts behind it. You can download a PDF version of the tutorial here.
NerdDinner Tutorial Now Also Available in HTML
A few minutes ago I finished publishing an HTML version of the NerdDinner tutorial as well. You can read it online for free here.
I split the tutorial up across 12 segments to make it more manageable to read. I also increased the sizes of the screenshots, and used a really nifty syntax highlighter that Scott Hanselman helped set me up with. I actually find the end result a lot easier to read than the PDF version.
Below are links to the different NerdDinner tutorial segments:
Hope this helps,
Scott
by community-syndication | Apr 27, 2009 | BizTalk Community Blogs via Syndication
Microsoft today announced the general availability of BizTalk Server 2009, which is available to Microsoft Developer Network (MSDN) customers and will be made available broadly in nine languages – Chinese simplified, Chinese traditional, English, French, German, Italian, Japanese, Korean and Spanish – on May 1. BizTalk Server 2009 delivers new capabilities to help customers more effectively integrate disparate systems, enhance end-to-end enterprise connectivity and more quickly exchange data across multiple platforms resulting in increased efficiency and lower costs. Key improvements in the BizTalk Server 2009 release include:
- New Application Lifecycle Management (ALM) experience to make development teams more productive
- New adapters and numerous enhancements that provide increased enterprise connectivity.
- New RFID mobile capabilities that will enable innovative solutions to drive business value.
As the sixth release for this mature server product, BizTalk Server 2009 provides a solution that allows organizations to more easily connect disparate systems. Check out the the following customer case studies to find out what early adaptors are already doing with BizTalk Server 2009:
Energy Firm Integrates Processes, Speeds Business Rules Development by 87 Percent
Software Company Speeds Bank Validation Process, Expects 20 Percent Productivity Gain
Microsoft Division Connects Systems and Virtualizes Servers to Improve Productivity
Microsoft’s BizTalk Server 2009 release offers a range of new capabilities and advancements, including:
- Simple, Cost Effective SOA Connectivity: With new and updated adapters, BizTalk Server 2009 advances interoperability by providing more than 25 industry adapters that make it easier for customers to connect critical business applications such as SAP, PeopleSoft, JD Edwards, Siebel and Oracle E-Business Suite.
- Increased Developer Productivity: BizTalk Server enhances the first-class developer experience provided within Visual Studio 2008 by offering new integrated capabilities including visual debugging, unit testing, and access to code artifacts.
- Better Visibility into Data and Activities: BizTalk Server 2009 enhances its Business Activity Monitoring (BAM) capabilities by reducing the complexity associated with trusted data collection and simplifying access to data.
- Leverage the Benefits of Virtualization: With BizTalk Server 2009 running on Windows Server 2008 with Hyper-V, businesses can take advantage of the benefits that virtualization provide including cost savings, production server consolidation and business continuity management.
- Simple RFID Solutions: BizTalk Server 2009 RFID capabilities reduce the need for complicated custom coding for disparate device types. Businesses can now easily extend RFID capabilities to mobile environments and experience the benefits from updated standards such as TDT, EPC EPCIS and LLRP.
- Application Lifecycle Management (ALM) Made Easier: BizTalk Server is now a first class citizen within the application development lifecycle by including new project management, testing and deployment capabilities.
BizTalk Server 2009 is again offered in four editions: Enterprise, Standard, Branch, and Developer. There will be no price increase over previous versions, and customers interested in upgrading to BizTalk Server 2009 can access complete pricing and licensing information on May 1 for all versions of BizTalk Server 2009.
by community-syndication | Apr 27, 2009 | BizTalk Community Blogs via Syndication
Microsoft have now officially released BizTalk Server 2009 for general availability – the April 27, 2009 press release is available here.
To match the release there have been a few updates on the product page as mentioned by Richard Seroter. A couple of other important changes I’ve noticed are:
BizTalk Server 2009 RTM Installation and Upgrade Guides […]
by community-syndication | Apr 27, 2009 | BizTalk Community Blogs via Syndication
Microsoft officially released BizTalk Server 2009 today. Press release is here, and you can see a complete list of new features here.
I was wondering what to write, and a retrospective seemed appropriate.
But first, where are we today? I hear lots of questions out in the field: where will BizTalk fit in a Dublin world?, what about WF?, how does BizTalk mesh with the future technologies? One of the talks I just submitted for the San Diego CodeCamp I think sums up where we are now pretty nicely:
BizTalk Server 2009: Integration Server, SOA Foundation, Gateway to Azure
Microsoft recently released BizTalk Server 2009. In this session we will look at the power that BizTalk provides to connect applications, services and partners. Now in its 6th release, BizTalk has evolved to play a vital role as the foundational messaging bus in a services-oriented architecture. We will look at the value BizTalk Server 2009 adds in bridging between on-premises and cloud-based application, as well as how it enables SharePoint to provide human interaction in workflows, processes and service orchestrations.
BizTalkers, we have a VERY interesting story to tell. We are the glue that holds things together. BizTalk Server 2009, plus all the adapters, WCF capabilities, ESB capabilities in the ESB Guidance, BAM, the rules engine, SharePoint adapter. the list of value-adds and the power BizTalk provides goes on and on. BizTalk has evolved with the times, and the industry, adopted standards as they emerged, and added capabilities as they were needed. We started out by being (as Don Box said circa 2002-ish) “ahead of our time”, and, we still are. We were doing loosely-coupled async services long before anyone said that’s what we should be doing. We were contract-first message-oriented – about a decade ago!
Now for the retrospective part:
- Here’s my post about the BizTalk 2004 launch: http://blog.brianloesgen.com/archive/2004/03/08/2671.aspx
- Here’s a retrospective I did about 4 years ago: http://blog.brianloesgen.com/archive/2005/11/30/61669.aspx (I figure I can quote my own retrospective in my retrospective once it’s over 3 years old :))
And, my favorite, is the CD I have:
Yes, it says “1999”, and no, as it turns out there never was a “BizTalk Server 1.0”, that would be BizTalk Server 2000. I actually remember seeing the first press announcement about this new thing called BizTalk, and telling a co-worker “I’m going to keep an eye on this, it sounds cool”. I started working with bits and interacting with the product team back in the BizTalk Jumpstart Kit days, which pre-dated even this Alpha. I think I’ll wait a few more years, then take that CD and try installing it on Windows 12 or whatever we are running then (assuming whatever I have can still read CDs!).
We’ve come a very long way since then, and the future continues to be bright for BizTalkers.
Note, if you’re in the US Southwest, watch this space for details of a “first look” tour we’re putting together.
Technorati Tags: BizTalk,SOA,ESB Guidance,ESB
by community-syndication | Apr 27, 2009 | BizTalk Community Blogs via Syndication
Earlier today, the DMTF announced the creation of the “Open Standards Cloud Incubator” group which will specifically focus on developing a set of informational specifications for cloud resource management. This is one of what will probably be a number of important efforts to drive additional value and choice for customers. This particular effort may catch the eye of folks on the enterprise side, as managing applications and infrastructure that spans premises and cloud is a very real topic of conversation. In the end, success in the cloud for most enterprises will include the ability to utilize a broad and diverse set of computational resources, some of which may be implemented very differently from others. A sensible goal of the DMTF is to reduce the friction across different vendor offerings in these datacenter scenarios.
As we have said previously, Microsoft will approach cloud standardization from multiple angles:
%u00b7 Practical interoperability – Microsoft-based services should be easily interoperable in practice with a diverse set of applications, platforms, and other clouds. We envision that our customers will integrate applications across multiple data centers, for example, having some of the component services running on Microsoft technology while other components run on Amazon, Google, Salesforce, or other data centers. Microsoft will work with other cloud vendors to produce guidance on building applications, to define the interoperability protocols, and to test real-world interoperability.
%u00b7 Standards–Microsoft will continue to invest in organizations, like DMTF, that help push the interoperability state of the art forward. Management is a great example of this, as there will likely need to be further evolution of the management protocols, such as WS-Management, to add cloud-specific extensions.
%u00b7 Data portability — Microsoft believes that our customers own the data that they have entrusted to our applications and platforms, and the applications they build on our platforms. Microsoft will work with other datacenter and cloud vendors to make this bi-directional, customer-centric approach a more common industry practice.
While it’s still very early to talk about elaborate technical standards for cloud computing, establishing the conduits for the conversations and outlining a collaborative approach is critical. Projects like the DMTF incubator will develop requirements and use case scenarios to allow all the participants to better understand where standards for communication with cloud services can create the most value.
As always, we pledge to be open, collaborative and transparent about our efforts in the cloud standards space. If you have thoughts on where we should focus additional attention, please let us know!
by community-syndication | Apr 27, 2009 | BizTalk Community Blogs via Syndication
A while back Matt Milner and I coauthored a whitepaper on the new WCF LOB Adapter SDK and the BizTalk Adapter Pack. It was published on microsoft.com a few weeks ago but I guess I missed it. You can download the paper from here. Here’s a brief overview:
When building applications today, it’s hard to consider building something that doesn’t involve connectivity of some sort. Applications require business data and logic that is distributed across several applications or servers. Unfortunately, not all systems provide the same interface to their data and business logic which ultimately forces developers to figure out how to talk to each of those systems. Connecting to a system doesn’t just involve opening up a port on a network address either; we have to work with different message formats, varying security mechanisms, and in many cases custom libraries that rely on proprietary mechanisms. In the end, it’s common for developers to struggle with learning a variety of different programming interfaces, communication protocols, and messaging semantics.
Windows Communication Foundation (WCF) promises to change all of that. WCF provides a unified programming model for building distributed applications using the .NET Framework. WCF was designed to provide a single unified programming model for writing either clients or services while also providing a flexible framework for different styles of communication on the wire. This approach allows developers to focus on writing code in their business domain rather than on learning new networking interfaces or object models. The code you write with WCF always looks the same but you can configure your apps to use different transport protocols like TCP, HTTP, and MSMQ; different message encodings like XML, MTOM, and binary; and varied security options including certificates, passwords, and security tokens.
The goals addressed by WCF are also very similar to the integration goals of Microsoft%u00ae BizTalk%u00ae Server. Ultimately BizTalk Server is primarily focused on providing an easy-to-manage model for connecting disparate, heterogeneous systems using a variety of different protocols, message formats and security mechanisms without requiring much, if any, code. This whitepaper discusses how the worlds of WCF and BizTalk Server 2006 are fully converging through the WCF LOB Adapter SDK and the BizTalk Adapter Pack.
I hope those of you working with WCF, BizTalk, and BizTalk adapters find this paper helpful.
by community-syndication | Apr 27, 2009 | BizTalk Community Blogs via Syndication
I will be speaking at Microsoft DevDays 09 in Hague on May 27-29. You can read more about the show here.
I will be delivering a pre-conference workshop on the Azure Services Platform, and I’ll be presenting several individual sessions on WCF/WF 4.0, .NET Services, “Dublin”, and the WCF REST Starter Kit. Hope to see you there!
If you find me at the conference, I’ll give you a substantial discount card for a Pluralsight On-Demand! subscription.
by community-syndication | Apr 27, 2009 | BizTalk Community Blogs via Syndication
A friend of mine, Jon Helmberger, posted on this Facebook status the other day a great quote which really pointed out how some people use technology that is trendy, and not necessarily the most appropriate technology. “If RSS had a cooler name we wouldn't have shenanigans like this…” with the following link: http://tiny.cc/kxALC. In a nutshell, local Minnesota municipalities are posting information, of varying usefulness, on Twitter and Facebook.
I realize it must be hard for organizations that are not on the cutting edge of technology to make decisions about what to pick. For that matter, I have been talking to a lot of developers lately who have trouble keeping up with all the technologies, even from a single vendor like Microsoft. But it is frustrating to see people gravitate to the hot item and try to use it without really figuring out if it is the right technology for the job. I can’t imagine that with the 140 character limit in Twitter, an organization can convey much useful information. If the posts always end up linking to something else, how useful is that? It seems to me that having an RSS feed would be the more appropriate mechanism for conveying this type of information. There are so many tools for reading RSS / ATOM feeds and including them in a page, etc. Sure, a Twitter feed can be read as an RSS feed, but again, the micro format seems like an inappropriate means conveying anything other than the simplest bit of information.
We at Pluralsight have started using these technologies (Facebook and Twitter) to convey information about what is happening with classes, content, etc. Of course we are mostly on the cutting edge of technology and hopefully have some idea of the best way to use these technologies. However, even we are still learning how best to use these technologies and which information is best suited for each format.
What do you think, is Twitter an appropriate tool for this sort of thing? Do enough, or the right, people use it to make it worthwhile? Or are too many people caught up in the hype? What tools do you find work best for you to get information?
