Web Builder uses model information to generate Web applications. You determine the look and feel of the Web application by the model and Web Builder settings you choose. You can use the same model to generate Web applications for either a Java or .NET environment.
The complexity and functionality of the Web application depends on the host application model that you create with the Design Tool. Using a model that contains only connection information, has no defined entities, and uses the default settings, Web Builder generates a Web application matching the terminal screen layout. However, if you use a model with defined entities, attributes, operations, recordsets, and procedures, you have more control over the Web application that is generated.
How does it work?
A Web page is generated for each included entity and procedure in the model. The pages are named entity_<ENTITYNAME> and procedure_<PROCEDURENAME>. Each procedure is exposed through a link in the generated Web application. When you click the link the application either displays a form to input the procedure parameters and an Execute button, or if there are no more parameters, a link that automatically executes the procedure.
When you include procedures in a model, Web Builder can generate a Web application that exposes the host application functionality, rather than just the host screens. Procedures encapsulate host data and logic so that it can be accessed as database tables. A set of files is generated that provides a Web-based front-end to the procedures in the table of your host application model. Programmers can then retrieve information from the host application using a familiar database interface.
Types of Web Applications
You can create Web applications for the following platforms:
To run a selected Web application: