Bridge your legacy systems to the Web

This business of linking the Web to the rest of the enterprise has become central to the jobs of IS staff. The demand for access has sent them scurrying for middleware solutions to connect Web technology to relational databases, legacy systems, and the rest of the IT infrastructure.
(Page 1 of 2)

There's something comforting about neighborhood hardware stores--something evocative of father-son projects on Sunday afternoons in autumn. Technically speaking, the thousands of Ace Hardware stores that dot the country are anything but refugees from Mayberry RFD. They're actually sophisticated end users of local computing power, and they want to be able to use the Web to place orders with their supplier, Ace Hardware of Oakbrook, Ill.

This business of linking the Web to the rest of the enterprise has become central to the jobs of IS staff. The demand for access has sent them scurrying for middleware solutions to connect Web technology to relational databases, legacy systems, and the rest of the IT infrastructure.

Middleware by any other name

Middleware definitions get sticky when products that, at first glance, aren't middleware provide middleware functions. Ostensibly, Amazon from Intelligent Environments in Burlington, Mass., is not middleware at all. Rather, it's a "development environment for Web-based applications."

But, if you're going to develop for the Web, you're going to have to link through something. Amazon has lots of links to databases, making it look a lot like middleware--and that's how some users treat it.

Lereta Corp., a Covina, Calif., company that provides tax servicing for mortgage banks, used Amazon as a Web link. In many states, mortgage companies must keep track of the tax records of the properties they finance. In a fluid real estate market, where properties change in value at high speed, that can get "kind of complex," says data communications analyst/Web master William Burnette. So the banks turn to companies like Lereta to do the job. The firm also provides flood zone determination. "We have what may be the nation's largest database on flood zones," says Burnette.

In the past, Lereta's subscribers dialed into its mainframe system and extracted property and tax information via standard terminal emulation. Now they want to do so via their browsers--a delight to Lereta, since that removes the process from its mainframe and 800 phone line. "It's going to take our maintenance cost down a bunch," Burnette reports. "And we're not going to be spending $50,000 a month on phone bills."

Burnette set up an NT-based Web server, which links to the company's mainframe via SNA. The rub was in connecting the Web to the database. The company's ES 9000 mainframe runs VSE. "That's important because MVS is relatively easy to link, but VSE is hard," he says.

Lereta uses Software AG's Adabas and intended to use that vendor's middleware to link to the Web, but Burnette was concerned that it would tie Lereta to a product that was too proprietary. He therefore turned to Amazon, which provided the company with both a development environment and a way to link its application to the Web. "Basically, what we're doing is using it as middleware to integrate all our existing databases on the mainframe with our other systems," he says. "Amazon integrates everything in just one shot. It can talk to OLE, CICS, and the Web."

Amazon isn't the only product that's kinda, sorta middleware. InterWorld Technology Ventures of New York City makes its money in the Web-based electronic commerce business. "We're definitely at the high end of the market," says president and chief technology officer Michael Donahue. "Our customers tend to be building major businesses around the Web." InterWorld's Oasis product suite includes electronic catalog, order entry, and back-end transaction processing technology.

"Oasis can also be used as a middleware application," Donahue says. The suite includes an assortment of high-speed proprietary gateways to such RDBMSs as Sybase and Microsoft's SQL server. It also has generic ODBC connectivity and, says Donahue, "as a last resort, it can use EDI" to get at legacy applications.

The bad news is that there are dozens, perhaps even hundreds, of middleware vendors vying for the role of universal Web-to-enterprise link provider. It's a product and technology explosion on the scale of a minor Big Bang, and it's every bit as chaotic and confusing as its cosmological cousin.

Middle of the road

Defining the technology is harder than you'd think. In general, middleware can be said to be the glue (or logic) that lies between the client and the server. Invisibly to the user, it deals with all the grim stuff of incompatible operating systems and file structures.

Middleware comes in five different types: database middleware, message-oriented middleware (MOM), object request brokers (ORBs), remote procedure calls (RPCs), and transaction-processing (TP) monitors. (For definitions of all of these, see the sidebar below, "Middleware methods.")

However you classify it, middleware is important, says Chris Stevens, electronic commerce analyst at the Boston-based market research firm the Aberdeen Group. "The Web servers themselves--from Microsoft or Netscape or whoever--aren't all that striking anymore. The key issue is providing the middleware necessary to bring corporate systems onto the Web."

"Absolutely," agrees Erica Rugullies, research analyst at the Hurwitz Group in Newton, Mass. "The companies, the users, are looking for integration with their back-end systems. And that's not easy."

The result has been a boom in the middleware market. Dozens of companies, ranging from start-ups to giants, have developed products that they hope will be to the Web market what Phoenix Technologies' BIOS was to the PC market--that is, the invisible but universal common denominator that makes computing possible.

All five of the major middleware types are represented among current offerings. Particularly active are the database companies; all of the major RDBMS vendors, from Informix to Unify, are offering software to link their databases to the Web. Some are actually developing entire Web-based computing architectures for a computing model in which the de facto user interface is the browser; Oracle's Network Computing Architecture and Informix's Universal Web Architecture are examples.

However, many of the larger architectures are still under construction, and the pure database-to-Web middleware solutions don't necessarily link Web sites to other legacy systems. So, at least for the moment, the focus of the Web-middleware market tends to be on the third parties that are following either a MOM or a combined ORB-TP monitor strategy.

Why these two? Chiefly, "because message-oriented middleware and ORBs came out of LAN and WAN markets," says Tom Laffey, cofounder and vice president of engineering at Talarian. The other middlewares tended to come out of pure client/server applications, where one large system is connected to one smaller system. On the Internet, by contrast, a great many systems of any number of sizes are talking all the time. "And message-oriented middleware had already worked out the sorts of issues involved [in that kind of communication] long before the Internet came along," he says.

Page 1 of 2

1 2
Next Page

0 Comments (click to add your comment)
Comment and Contribute


(Maximum characters: 1200). You have characters left.