Develop browser applications

Develop browser applications

If an RPG/COBOL programmer wants to develop browser applications on the iSeries, which of the two is best for speed and long-term usage, WebFacing the old application or rewriting it in VisualAge for Java?

    Requires Free Membership to View

    Register today to access targeted resources from our editorial writers and independent industry experts including news, tips, and advice to help you do your job more efficiently and effectively. Stay informed on the hottest topics and biggest challenges faced by IT professionals working with iSeries products and services.

    By submitting your registration information to Search400.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of Search400.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Converting existing applications

If you are creating a browser interface for an existing application, then the fastest most productive way to create the Web interface is with the WebFacing Tool. A normal business application with under 200 screens can be converted and published to WebSphere Application Server for test in under 2 hours. One company converted a major ERP application with over 18,000 screens in under 3 months. With the latest version of the WebFacing Tool, they were able to convert all but five screens without changing any display file DDS. The five remaining screens required some minor changes.

Creating new Web applications

If you are creating brand new "browser-based" applications, then you have several choices. If you are going to run the applications on the iSeries server, then you should write the modular business logic as batch applications in ILE RPG or ILE COBOL. ILE RPG and ILE COBOL are the most efficient languages for writing business logic for OS/400. If you are writing applications to execute on multiple servers, then you should write your business logic in Java. The performance of the applications will be dependent on your programming skills in the language chosen but RPG and COBOL applications will probably execute slightly faster than Java because Java is an OO language and will have more instructions for the same application. The differences should only be marginal.

Since you have created a callable batch application (one without a user interface)in either RPG, COBOL or Java, you can now choose the application interface. You would typically develop a browser interface with the Web development tools included in WebSphere Development Studio for iSeries. The Web development tools come with wizards to generate a Web interface to iSeries programs and data. You now have a browser based application that runs in batch mode and doesn't require any interactive cycles to execute. With a batch application, you have the freedom to modify your application interface. You can access your logic from a Java application, a Web/browser interface, or a Web services application. Your application just became a lot more flexible.

==================================
MORE INFORMATION ON THIS TOPIC
==================================

Ask your Web development questions--or help out your peers by answering them--in our live discussion forums.

The Best Web Links: tips, tutorials and more.

Check out this live Q&A with Dave Slater and Jim Mason, How to best get started with WebSphere Development Tools.

Search400's targeted search engine: Get relevant information on machine interface (MI).


This was first published in August 2002