SOA & WOA Magazine on Ulitzer
Although XML has been around for quite some time many developers still don't
know too much about it. Not needing to know too much about it is one of XML's
strengths, but cursory knowledge is rapidly becoming mandatory for all
developers. This post will discuss some of the details of namespaces in XML.
In XML a namespace is just that, a space (or area) identified by a name. When
we look at a namespace such as
http://novaenterprisesystems.com/schemas/purchaseorder we are not actually
identifying a location on the web. Granted it does look like a URL and your
browser will probably make you want to click it (don't bother, at least for
now it doesn't actually go anywhere). In an XML document this simply means in
a namespace that certain nodes of the document exist in this namespace. That
is they are identified by their Element / Attribute na... (more)
I am writing for cio.com again and thought I'd go back down the SOA track.
This will be in parallel to my BizTalk specific posts here, but there will be
a lot of overlap. The UDDI series I am just starting will mostly be based on
the UDDI v3 that is part of BizTalk Server 2009. The first of the cio.com
articles can be found here:
http://advice.cio.com/dan_rosanova/why_uddi_is_important
Future articles will elaborate on the points presented in the article above.
... (more)
I'm a really big fan of BAM and I use it in basically every solution I
create. Even if it is just for support use the ability to see into running
business processes is vital. As much as I love BAM I would say that there is
still a lack of good information out there about it. Here is one of my
favorite details. Which schema you tie your BAM to depends on if you're
binding to a Send or Receive port.
I always build my solutions with a consistent Visual Studio Solution
Structure that has always worked well for me. Binding BAM to my internal (or
canonical) schemas always made sense a... (more)
I've been on a pretty serious WCF kick for the past few months and more and
more I love it. I like even more how well BizTalk works with WCF. BizTalk is
the application server you normally need to provide yourself to make WCF very
useful. In Handling Binary Messages in Orchestrations I had mentioned that I
used SQL Reporting Services via Web Services to run reports and do something
with the output. As I had been experimenting with the solution I tried using
both the SOAP Adapter and the WCF Adapter and found the WCF Adapter to be
much more to my liking.
Using the WCF Http Basic ... (more)
I've spent a lot of time lately designing stateless services and the schemas
to enable them to be both stateless and extensible (which will be another
post), but in doing so I began to realize that very often people embrace
BizTalk Orchestration as the closest analogy to Business Process and tend to
over leverage it in an attempt to unify and track their business processes.
There certainly are times when an Orchestration is a business process, but
often business processes will span multiple Orchestrations. Fortunately BAM
and the TPE allow for this.
So what's wrong with just mak... (more)