Skip Headers
Oracle® Forms Migrating Forms Applications From Forms 6i
10g (10.1.2.0.2) for Windows and UNIX
B15572-01
  Go To Documentation Library
Library
Go To Product List
Product
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

15 Migrating Client-Server Applications to the Web

If you are currently using the client-server version of Forms Server, migrating applications to Forms Services for the Web is straightforward.

This chapter contains:

In addition, you will find white papers and other resources at http://www.oracle.com/technology/products/forms/.

Guidelines for Migration

When migrating 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 JavaBeans as a replacement or WebUtil.

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

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' machines.

Figure 15-2 Oracle Forms Web Architecture

Web-based architecture overview