This article is an expanded version of the May 2004 print-magazine article. See 15 Webfacing Programming Tips at the bottom of article ID 18303! See Webfacing Tables

It's interesting to many and perhaps confusing to some. WebFacing is an IBM product, but it's also become a term that generically describes the process of Web-enabling or rejuvenating legacy applications. So, can one Webface an app? Yes. Does one necessarily have to use IBM's WebFacing product to do so? No, not really.

Although the IBM offering provides a wealth of functions for accomplishing the task of putting an Internet interface on an existing application, it's not the only way to get the job done. In fact, there are at least two dozen third-party software tools that can also help you Web-enable an iSeries application. iSeries NEWS queried vendors of interface generation products and presents a summary of the responding companies' solutions in online tables.

To qualify to participate in this roundup, interface generator products had to meet several criteria. First, they had to be capable of generating a front-end, Web-accessible GUI that left the base application's back end intact. The front end may need additional modification before deployment, and Code Designer or some equivalent is needed to keep the Web and back-end versions of application code synchronized with each other. Second, the tools' functions must facilitate Web-enablement of existing applications rather than helping programmers develop new Web-based applications. And finally, the tools must support leveraging of existing RPG and Cobol programmer skill sets.

The qualifying products fall into two general categories: tools that don't use emulation as a basis for generating elements of the interface, and those that do. We've separated these into two product tables — the first table being those products that don't use emulation. We've made this distinction because, strictly speaking, only those tools that don't use emulation are true competitors to IBM's WebFacing, which also doesn't use emulation. But those products in the second table also fit all the requirements we set out for products that generate a Web interface and so are included for completeness. Some of the products either use 5250 emulation as an option or don't require emulation use if a DDS is available. If you consider purchasing a product, you'll need to check up on this point with the vendor. Because the online tables are dynamic, we plan to update those tables over time as additional vendors profile their products or as new products come on the market.

We asked each provider a set of questions regarding its Webfacing product. The providers' responses are compared in the online tables, but a few of the questions themselves require some words of explanation:

• Is the application's source code necessary for your product to work? If source code is necessary, then the Webfacing product is intrusive, meaning it requires modifications to your existing code. This isn't necessarily bad. In most cases, you'll find the product modifies the code for you, although you have to be careful with future changes to the source code. And, if presence of source code is necessary to accomplish the Webfacing, that means a particular tool may prohibit you from Web-enabling third-party applications because source code isn't available.



• What editing/design tools can be used with the product? Typically, because you're creating a GUI with the product, you'll have to tweak the product's generated interface or build your own from scratch. Therefore, it's important to know whether the product comes with a tool for building the interface or whether you'll need to use another tool (e.g., FrontPage, DreamWeaver).



• Is another server required? Some products run on a different platform and interface with your iSeries on the back end. End users access the other platform where the product is running, and the product handles the communications with your original application running on the iSeries. This is another important feature because if the product runs on another platform, you need to consider the total cost of purchasing and maintaining another server in addition to buying the product itself and other costs.



• Does the result still use the expensive iSeries Interactive CPW? Near and dear to all of us is concern about the cost of running our applications. Under IBM's pricing model, a product that lets you run your legacy applications in batch CPW can save your company thousands. On the other hand, if your new Webfaced application increases the exposure (usage) of your application, and it uses Interactive CPW, the result may cost more than you expected!

As you'll see, there are dozens of alternatives to IBM's WebFacing product. I think you'll be impressed with many of these solutions and how they can give new life to your applications and programs. However, the few questions we asked the vendors just scratch the surface of the unique set of features and functions each product provides. A vendor contact list included with the online tables provides URLs at which you can get more details about the listed solutions and, in some cases, give the product a test run. I urge you to do this if you're considering using any of the alternatives to IBM's WebFacing product.

Jef Sutherland is an iSeries NEWS technical editor and vice president of information services for KOA Kampgrounds of America, Inc., in Billings, Montana. You can e-mail Jef at dqtech1@bresnan.net.