Just tried to install Orcas Beta 2 with BizTalk RFID to no avail...http://support.microsoft.com/kb/942521.
"Microsoft BizTalk RFID is not supported when it is installed on the same computer as the .NET Framework 3.5 Beta 2. However, Microsoft BizTalk RFID will be supported when it is installed on the same computer as the release version of the .NET Framework 3.5."
So I guess we wait
ESB Guidance V1 on MSDN go check it out. I'd used the CTP's but the new release looks all shiny and new. Marty and the guys did a great job. More on this soon.....
Well if you hadn't heard the news, M$ is now all about the model which is great. However it's horses for courses one persons model isn't necessarily another's e.g. business analysts versus tekkie models have different goals. Translating from higher level to lower (closer to the metal) models is complex.
There were a couple of demos that showed the generation of BizTalk orchestrations from a business process model designed by an business analyst (the companies behind the tools shall remain nameless). For the uninitiated the demos look great; anyone who has been baptized in the fires of BizTalk can immediately see the danger.
A business guy describes his process but doesn't realize the operational implications of his description or decisions e.g. 'I have a business process that receives a PO and sends a request to an ERP system, then in 90 days if we don't get paid we chase the money'. Picture the model he/she could draw; you got it delay for 90 days. Do we really want an orchestration that hangs around for 90 days?
What happens if we want to upgrade this orchestration?
What happens if 90 days becomes 110 days?
What happens if someone unenlists the orchestration?
We would want to break the process into smaller shorter-running manageable steps not just one big orchestration. IMHO these tools are dangerous in the wrong hands, they should come with a 'use with care' sticker on the front.
On the flip side Jon Flanders just released a workflow to BizTalk xlang wizard. Now this is different; typically a WF workflow has been designed with a lot of the same considerations in mind that one would have when designing a BizTalk orchestration. Therefore you are converting like with like.
The dissonance between the models that business analysts and tekkies produce is difficult to reconcile. Role on Oslo ;0)
Jon Flanders did a session (sold out) last night on building a Service Monitoring Infrastructure with BAM. Great talk! He highlighted one thing that has been drifting on the edge of my consciousness over the past year; that is where is the sweet spot for BAM and where does the BizTalk tracking database play well.
After BAM was released in BizTalk 2004 it became obvious to M$ that the BAM product had as much traction with the operational people as it did as it did on the business side. The first signs of this were the embedding of BAM functionality with the M$ Operations Manager (MOM 2005 Resource Kit). The most recent evidence is that the new EDI functionality is supported from a tracking perspective by BAM. I felt compelled to ask the question then as to what to choose
or
The answer yesterday was BAM only. I'm still weighing the implications of this. Ponder for a second what happens when you turn off all tracking in BizTalk. BizTalk would scream along enabling support for lower (not low-low) latency solutions, the downside seem all related to compliance and auditing. Now the questions is how to address these gaps with BAM.
My gut feel is that Jon is onto something here. Because BAM extends the reach of how we implement tracking in a really flexible way the power to track what's interesting to your business moves back into your control. BAM really provides a more holistic approach that reflects the reality of tracking.
Oslo really is a grand vision but what about Software Factories, DSLs, GAT, GAX etc. I've been asking that question of as many people as I could and I'm not sure what the answer is.
Last year was all about Software Factories as the future for all of us. I heard and saw lots of sessions and debates about SF versus MDA. There seems to have been a rethink on this, it's now all about executable models. Models will represent the 'actual' and 'current' state of things as opposed to a models now that show a design time state that is pretty stale and old nearly immediately. So what happens people who have invested in GAT, GAX, DSLs my gut feel is that you (we) may have been sold a pup. See the correction below...
The focus on GAT packages that was around last year seems to have blurred a bit. My sense of it is, that GAT in it's current form doesn't really align well with the Oslo vision. In terms of what is on the agenda in this at the conference; Don Smith is releasing a new version of Web Service Software Factory this week but the word on the street is that the pre-release version contained tools (really useful tools) that won't appear in the release because it confused the Oslo message. There's also a session on the Smart Client SF later in the week but very little hype.
Watch this space I will try and ferret out what the truth/future is.
CORRECTION>>> I talked to Don Smith on Thursday after his Service Factory demo. DSLs, GAT and GAX are still around Service Factory V3 looks super we'll see some really cool stuff in Rosario. I think the reason that stuff has not been talked about at this conference is to try and not confuse the Oslo message with other noise.
Once more Service Factory V3 is really really cool and looks really extensible.
I arrived late last night into 'sunny' (I'm serious) Seattle - everyone told me it would be raining. So what's new. Well the big news is Project Oslo which has been under NDA until this morning. Oslo is the vision of the future and it's all about models and services.
Oslo is where workflow, Internet Service Bus (BizTalk Labs), WCF, BizTalk Server '6', hosted services all coalesce. All this along with general purpose modeling language(s), tool(s) Universal Model Editor (CTP's next year watch this space) and a model repository.
It's a really ambitious vision and one that M$ admit might never be fully realized. I guess we'll wait and see.
I've got just over an hour so it's going to be interesting fitting all that in. I decided not to do the usual order processing demo in an effort to try and get people a bit more engaged (I hope ;0). You can read the synopsis here.
Basically I'm fascinated by the potential that RFID has as a ubiquitous technology. Every other dmeo I've seen in this area is always in the context of inventory management, tracking and stock control. In a way my demo is much the same apart from the setting. I've moved off the shop floor and into Law Enforcement.
The various CSI shows on the idiot box inspired me with their use of technology (I hate the show especially CSI Miami, Horatio Kane in particular). Having said all that I love the technology (real or not).
To cut a long story short the demo will show a CSI Evidence Monitoring system with real live RFID devices as opposed to the AcmeProvider in the RFID SDK. When I'm done I'll post the code and a step by step of how to recreate the whole solution.
I finally sat and passed the Biztalk 2004 74-135 exam. I'm now BizTalk certified (or certifiable depending on who you taIk to). I've seen lots of requests for tips on this exam. I'll do what I can within the rules of the certification program.
This checklist is targeted mainly at developers who develop but don't manage or administer BizTalk 2004.
I think that the exam is a pretty fair guide of someone's overall knowledge of the BizTalk platform. As described it covers everything the platform has to offer. Therefore if you answer 'NO' to any of the following then I suggest you look to the help and/or the BizTalk Unleashed book.
You know BTS but-
If the answer is no to more than 2 of these questions then aren't ready.
Personally I've never used HWS and I'd be lying if I said I had more than a passing aquaintance with BAS. So I basically took a chance that I would do well on the bits I did know, as it turns out I was must have.My very first blog entry! I’ve been putting this off for so long; it’s gotten to be a habit (a bad one). To start I suppose I need to position this blog and set some expectations.
Me:
I’m a solutions architect
This blog:
Every so often I’ve got something useful to give back to the community (or at least I hope I have). I’ve benefited a lot from other peoples blogging endeavours. Now it’s time to give a little back. Along the way I’ve disovered some stuff and I’ve had one or two interesting thoughts that I wanted to share, now I have a home for them.
Right now I’m interested in a couple of things BizTalk and Software Architecture to name but a few. Along the way other technologies might rear their ugly (or not) heads so don’t be surprised.
Me and BizTalk (BizTalk and I)
I’ve been working with BizTalk 2004 for what seems like an age now. I’ve been experimenting with BizTalk 2006 since Beta 1; I even demo’ed BizTalk 2006 at the November launch. I promised at that demo that I would put up a blog and post material from that presentation (expect to see it shortly).
So what should you expect?
I think my friend Daragh nailed it on the head when he set the goals for his blog
‘Learning, helping and making a little money’
If I can do that with this blog I’ll be happy.
