<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title>Articles by Brady Flowers</title>
<link>http://websphere.sys-con.com/</link>
<description>Latest articles from Brady Flowers</description>
<copyright>Copyright 2008 WEBSPHERE JOURNAL</copyright>
<lastBuildDate>Sun, 20 Jul 2008 13:58:00 GMT</lastBuildDate>
<generator>WEBSPHERE JOURNAL</generator>
<ttl>10</ttl>
<docs>http://backend.userland.com/rss</docs>

<item>
<title>Consolidating Legacy Data</title>
<guid isPermaLink="true">http://websphere.sys-con.com/read/43059.htm</guid><link>http://websphere.sys-con.com/read/43059.htm</link>
<pubDate>Fri, 30 Jan 2004 07:52:00 GMT</pubDate>
<description>Every company that&apos;s been around longer than a few months has probably created or purchased many different systems dedicated to specific areas of the business. For example, let&apos;s say customer files were set up years ago using off-the-shelf software. The software had hooks for customization, and some features were added. Over the years the customer list has grown very large, and the company has become dependent on this system. You know the word: legacy.</description>

</item><item>
<title>Using The VisualAge For Java Enterprise</title>
<guid isPermaLink="true">http://websphere.sys-con.com/read/36288.htm</guid><link>http://websphere.sys-con.com/read/36288.htm</link>
<pubDate>Fri, 01 Jun 2001 00:00:00 GMT</pubDate>
<description>Last month in JDJ (Vol. 6, issue 5) we looked at the Java 2 Platform, Enterprise Edition (J2EE) connector architecture (JCA) and its common client interface (CCI). To recap, JCA is the part of the J2EE 1.3 specification that facilitates the integration of Java applications with Enterprise Information Systems (EISs). The term EIS refers to a number of systems such as ERP, legacy databases, or transaction processing systems.</description>

</item><item>
<title>The J2EE Connector Architecture</title>
<guid isPermaLink="true">http://websphere.sys-con.com/read/36268.htm</guid><link>http://websphere.sys-con.com/read/36268.htm</link>
<pubDate>Tue, 01 May 2001 00:00:00 GMT</pubDate>
<description>Most companies have a large investment in legacy systems for ERP, transaction processing, and database applications. Everyone&apos;s talking about how they can leverage these systems and integrate them into their modern, multitier, e-business application architectures.</description>

</item><item>
<title>Consolidating Legacy Data Part 2 of 2</title>
<guid isPermaLink="true">http://websphere.sys-con.com/read/36213.htm</guid><link>http://websphere.sys-con.com/read/36213.htm</link>
<pubDate>Thu, 01 Feb 2001 00:00:00 GMT</pubDate>
<description>In Part I of this article (JDJ, Vol.6, issue I) we discussed solving legacy data integration problems with VisualAge for Java and WebSphere Studio.  In Part 2 we&apos;ll discuss using the MQSeries Integrator and some of the steps for creating data translations and data flows.</description>

</item><item>
<title>Consolidating Legacy Data</title>
<guid isPermaLink="true">http://websphere.sys-con.com/read/36189.htm</guid><link>http://websphere.sys-con.com/read/36189.htm</link>
<pubDate>Mon, 01 Jan 2001 00:00:00 GMT</pubDate>
<description>Every company that&apos;s been around longer than a few months has probably created or purchased many different systems dedicated to specific areas of the business. For example, let&apos;s say customer files were set up years ago using off-the-shelf software. The software had hooks for customization, and some features were added. Over the years the customer list has grown very large, and the company has become dependent on this system. You know the word: legacy.</description>

</item></channel></rss>