Newletter Sign Up
Posts on the
Design Decomposition Blog
Iridium Satellite Collision in Space
You might have seen the recent news reports about the collision between U.S. and Russian communication satellites. The U.S. satellite was one of the Iridium satellites. What wasn’t reported and you probably don’t know is that an object database management system (ODBMS) is an important part of the Iridium system. Even though ODBMSs are a [...]
February 13, 2009
(The Acronym) SOA is (Perhaps) Dead (at Some Companies); Long Live Services
I am now also posting on the Cutter Blog. My initial posting is (The Acronym) SOA is (Perhaps) Dead (at Some Companies); Long Live Services. It is a response to Anne Thomas Manes’ SOA is Dead; Long Live Services on her blog at the Burton Group.
January 9, 2009
Atomicity
The typical definition of an atomic task or process is one that cannot be decomposed further. This is vague and subject to interpretation. The Decomposition Matrix on this site uses a specific definition: A task (for business process diagrams) or a process (for data flow diagrams) is atomic if every input relates to every output [...]
December 3, 2008
Well-Formed Business Process Diagrams
My last posting referenced the criteria for a well-formed business process diagram mentioned in Business Process Driven SOA using BPMN and BPEL by Matjaz B. Juric and Kapil Pant. I am going to expand on their criteria to create a more comprehensive definition of a well-formed business process diagram. To start, here are three criteria from [...]
November 18, 2008
Recent Business Process Modeling Books
I recently received two new books on business process modeling. Both books looked interesting because they had great titles. As it turns out, one book is great and the other not so good. The not so good book is Business Process Driven SOA using BPMN and BPEL by Matjaz B. Juric and Kapil Pant. There are [...]
October 9, 2008
The Design Decomposition Blog
is written by Doug Barry.

Message routers direct data from a requesting resource to a responding resource and back. These are also known as application brokers, message brokers, or XML data routers. A router "knows" which of the other internal systems needs to receive a certain types of updates. The individual internal systems can pass updates to a router and would not need to know who receives such updates.

A message router usually needs to transform the data in some way in order to match the format of the data expected by the receiving system. The following shows examples of such transformations. Internal system A at the left is sending data in tagged XML format. Internal system B at the right expects a tagged XML format, but expects the tags to be different. For example, instead of the tag <name> in system A, system B expects the data to be tagged with <customer>. The tags for phone and postal code data also are different. The message tag itself varies as well. At the left, the tag is <GetCustomerInfoResponse> and at the right, the tag is <GetCustomerAccount>

Example message router

Existing internal systems will most likely also need an adapter. See Web Services adapters for how a message router is shown with adapters.

More information on Web Services message routers can be found in Web Services and Service-Oriented Architectures: The Savvy Manager's Guide.

If you are interested in a listing of message router products, click here.

Related content for: Web Services message routers

More on the general topic: Messaging components

Read more free articles on this site

There are nearly 400 pages of articles on this site with over 130 pages on Web services and service-oriented architecture.

Search this site for more articles

Custom Search

Browse this site for more articles

Click on the topics below to browse the articles on this site. You can see more detail by clicking on the arrows. This highlights the location of the current article: Web Services message routers.

Related recent articles from Google News

Spring.NET 1.3: VS.NET Solution Templates, MSTest Support and Spring ...
InfoQ.com
NET and Spring Java applications, across a range of distributed technologies such as messaging, web services and REST. Milestones and release candidates are ...

11 Feb 2010 at 8:08pm
More related news on: "Web services" message router

Related books at Amazon.com

NT Network Plumbing: Routers, Proxies, and Web Services
NT Network Plumbing: Routers, Proxies, and Web Services
Publisher: Hungry Minds
Publication Date: January 1998
More related books: Search Amazon.com for router Web services