The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.
All information submitted is secure.
The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.
Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.
Because of its flexibility and its presence in many application
environments, XML is becoming the preferred log format. In this article,
you'll learn how to easily set up an application logging environment by
bringing the XML features of WebSphere and DB2 together. We first introduce a
simple application logging scenario, then show how to use solidDB for caching
and decoupling the application from the logging infrastructure. WebSphere
Message Queue and WebSphere Message Broker will be used 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,
WebSphere Message Broker will also be used to transform log files to other XML
formats prior to storing them into DB2.
In Part 2 of this two-part series, set up IBM solidDB Universal Cache
with DB2 for Linux, Unix and Windows to accelerate access to data. Learn about
system and environment requirements, as well as the ways to acquire IBM
solidDB Universal Cache code. Learn also how to install, configure, and use
the IBM solidDB Universal Cache solution.