Most companies have a large investment in legacy systems for ERP, transaction
processing, and database applications. Everyone's talking about how they can
leverage these systems and integrate them into their modern, multitier,
e-business application architectures.
There's an old saying about the weather - everyone talks about it but no one
ever does anything about it. Fortunately, this is not true for Enterprise
Information Systems (EISs). In fact, IBM, Sun, and a number of other
companies are doing something about it in the Java 2 Platform, Enterprise
Edition (J2EE) with something called the J2EE Connector Architecture (JCA).
VisualAge for Java contains the tooling that was, in large part, the
inspiration for JCA. J2EE and JCA are not, as of this writing, finalized and
thus no application server or development tool can claim support for either.
We'll see, however,... (more)
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.
As we saw in the last issue, integrating these systems into a modern
e-business architecture is complicated, to say the least. The APIs that these
systems pro... (more)
Every company that'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'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.
Of course, the developers who did the customization are long gone.
At some time between then and now new features were needed by ... (more)
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'll discuss using the MQSeries Integrator and some of the steps for
creating data translations and data flows.
MQSeries Integrator extends MQSeries by adding message brokering that's
driven by business rules. MQSI lets us add the intelligence to route and
transform messages or filter messages (content-based or topic-based). It also
lets us perform direct database access so we can augment or warehouse
messages. We'll look ... (more)
Every company that'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'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.
Of course, the developers who did the customization are long gone.
At some time between then and now new features were needed by ... (more)
Brady Flowers is a software IT architect with IBM’s WebSpeed team specializing in WebSphere, Java, and the rest of IBM’s suite of e-business applications.
Scott Sellers
Anthony Franco
Daniel Morris
Wayne Walls
Niki Acosta
Jereme Hancock
Oren Michels
Marvin Wheeler
Douglas Kim
