IS Survival Guide

SAN MATEO (03/13/2000) - MANAGEMENT SPEAK: That's a very interesting concept.

Let me think about it, and I'll get back to you on it.

TRANSLATION: I'll get back to you on this via the company newsletter, which will give me the credit.

-- But I'm still giving IS Survivalist Scott McIntyre credit for this interesting concept.

A legacy system is like any other corporate asset. You invest in it, maintain it, and maximize returns from it. With the money you spent remediating legacy systems, you'd better get extra leverage from them.

One way to do this is with Web-to-host integration -- making functionality from legacy systems available via a browser. Like so many subjects in IT, however, the obvious solutions are often shortsighted.

Go back to the basics: the need for IS to manage technical architecture.

Technical architecture management is a core discipline for IS these days, as described in this space over a year ago (Aug. 17, 1998, through Oct. 5, 1998).

Architecture consists of three layers: Application, Information, and Platform.

Business value comes from the Application layer. Applications use Information (including databases and unstructured data), and run on the Platform layer (including hardware, networks, software, and database management systems).

Web-to-host integration from an architectural perspective begins by describing the application-layer functionality needed and then traces a path for its implementation maintaining as much simplicity and design elegance as possible in lower layers of the architecture. What functionality are you looking for?

You may be looking for a less costly way to deliver 3270 screens to end-users by simplifying the Platform layer and leveraging an intranet. If so, congratulations; you're taking an architectural view.

On the other hand, you may be trying to export legacy functionality to the company's Web site to encourage customer self-service or supply-chain optimization.

If so, you're about to make a big mess. You want to export mainframe functionality via the Web. However, you'll need to export that functionality via other channels too -- through the Web, IVR (interactive voice response), a call center, and possibly through tools customized for your direct sales force.

Once you start thinking you need Web-to-host integration, you'll start thinking you need separate host integration for every category of application. That's bad enough. What happens next is worse. Because your Web site, call center, and IVR system will have separate host connections, they will need separate, possibly inconsistent host integration logic.

Host integration logic belongs in the middle tier, where all applications can use it. That's what EAI (enterprise application integration) systems are for.

The case for EAI is compelling: The alternative is to create a spiderweb of separate interfaces between each legacy system and every front-end application.

Do this, and managing the impact of legacy system maintenance is a polynomial nightmare. EAI is difficult to implement well. First-class EAI implementations know how to use host wrappers and integration tools to map legacy systems into well-designed object class hierarchy -- to present them and to "persist" any updates.

A good EAI implementation is very hard. The alternative, however, is completely unworkable.

E-mail your questions to Bob Lewis is a Minneapolis-based consultant at Perot Systems Corp.

Join the newsletter!

Error: Please check your email address.

More about CompuservePerot Systems

Show Comments