Application logging using solidDB, WebSphere Message Broker, and DB2 pureXML

How to set up an infrastructure for application logging

From the developerWorks archives

Daniel Schall and Dr. Henrik Loeser

Date archived: January 12, 2017 | First published: May 07, 2009

Because of its flexibility and its presence in many application environments, XML is becoming the preferred log format. This tutorial shows how to easily set up an application logging environment by bringing the XML features of IBM® WebSphere® and IBM DB2® together. This tutorial first introduces a simple application logging scenario, then shows how to use IBM solidDB® to cache and decouple the application from the logging infrastructure. Use WebSphere Message Queue and WebSphere Message Broker to reliably move the log messages from the application to DB2, where they can be stored and queried using the pureXML® functionality. To normalize different message formats, use WebSphere Message Broker to transform log files to other XML formats prior to storing them in DB2.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.

Zone=Information Management, WebSphere, XML
ArticleTitle=Application logging using solidDB, WebSphere Message Broker, and DB2 pureXML