Helping ordinary people create extraordinary websites!
| |
Helping ordinary people create extraordinary websites! |
Using the JMS API and XML in Content-Based RoutingBy Todd Sundsted2003-12-20 
How to make sure information gets to the right people
All Knowledge Management solutions face the challenge of putting the right information in front of the right people. It's possible to confront this challenge with the right technology. Todd Sundsted demonstrates how to use Java technology, the Java Message Service (JMS) API, and XML to build a messaging infrastructure that routes messages based on their content Information comes in many forms. It may be physical -- paper-based forms and memoranda -- or purely electronic -- e-mail, e-fax, USENET and knowledge-base postings, and other archives. And information covers many domains, from change notifications, status reports and updates, and process changes to casual communication. Much of the electronic information is conveniently packaged, transferred, and stored in the form of a message. A key limitation of this message-based electronic information is the way it is addressed. Most of this information is either addressed to specific persons or, in the case of most general knowledge-base information, is addressed to no one in particular. What happens if the specified address is no longer valid? Perhaps the intended recipient is no longer with the company. Presumably someone still handles their function. Who should handle the message now? What if others besides the intended recipient are interested in the message's content? What if no destination is specified? One possible solution to these problems is content-based routing. Content-based routing seeks to route messages, not by a specified destination, but by the actual content of the message itself. In a typical application, a message is routed by opening it up and applying a set of rules to its content to determine the parties interested in its content. Content-based routing and filtering networks are extremely flexible and very powerful. When built upon established technologies such as MOM (Message Oriented Middleware), JMS (Java Message Services), and XML (Extensible Markup Language) they are also reasonably easy to implement. In this article I will demonstrate how to use Java technology, the JMS API, and XML to build a messaging infrastructure that routes messages based on their content. Tutorial Pages: » How to make sure information gets to the right people » Messaging and the JMS API » A simple content-based routing system with agents » XML and XPath » The code » Conclusion » Resources IBM DeveloperWorks
|
 |