Skip Headers
Oracle® Forms Upgrading Oracle Forms 6i to Oracle Forms 11g
11g Release 2 (11.1.2)

Part Number E24478-01
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

15 Upgrading Client/Server Applications to the Web

This chapter describes guidelines for upgrading client/server applications to the Web.

This chapter contains:

In addition, refer to the white papers and other resources at http://www.oracle.com/technetwork/developer-tools/forms/documentation/index.html.

15.1 Guidelines for Upgrade

When upgrading your applications from client/server deployment to the Web, note that a Web-based application:

If the functionality of these Built-in and packages is required for the client, use WebUtil.

15.2 About Client/Server-Based Architecture

In the client/server-based implementation, shown in Figure 15-1, the Forms Server Runtime Engine and all application logic are installed on the user's desktop machine. All user interface and trigger processing occurs on the client, except for database-server-side triggers and logic that may be included in some applications.

Figure 15-1 Oracle Forms Client/Server Architecture

Legacy Forms Server client-server-based architecture

15.3 About Web-Based Architecture

In a Web-based implementation, shown in Figure 15-2, the Forms Services Runtime Engine and all application logic are installed on application servers, and not on client machines. All trigger processing occurs on the database and application servers, while user interface processing occurs on the Forms client, located on users' systems.

Figure 15-2 Oracle Forms Web Architecture

Web-based architecture overview