Web-enabling legacy systems for Net access allows data to remain where it has always resided while making it available over the Web.
Few organizations Web-enable corporate databases simply because they can. A company must have compelling business and technological motivations for undertaking the project. Otherwise, it’s not worth the effort. On the technology side, the primary reasons for Web-enabling legacy database systems are to manage inevitable migrations from old to new technology before the former runs out and leverage existing Web knowledge within the corporation for the benefit of both programmers and employees.
Chances are that your organization can save time and money by enabling your mainframe databases for Web browsers instead of replacing them wholesale. But let’s be honest. Not all companies have saved time or money. The practice of Web-enabling legacy systems is so new that not much hard data is available yet. The success stories are impressive, though. Here’s how to avoid hidden costs and unnecessary tasks:
Don’t enable your Web database at the wrong end. The difference between connecting your mainframe directly to the Internet and building a gateway between the legacy system and your corporate intranet is the difference between $9,000 and $90,000.
Don’t assume that off-the-shelf software packages will solve all your problems. Web application development environments are young. Expect to budget for the construction of macros or extensions to address your specific needs.
Don’t expect to get away with a modest pilot program that gradually revs up to full use by a department. Those stuck with dumb terminals will be jealous if their machines aren’t updated within a short period.
Don’t expect existing desktop hardware to handle a Web-enabled database. Giving your employees access to mainframe data via a Web browser often means you’ll have to upgrade their systems to allow them to make use of it.
How do you use the Web to access legacy data? We want to know.
