Oracle Forms Developer and OracleAS Forms Services Migrating Forms Applications from Forms 6 10g (9.0.4) Part Number B10469-01 |
|
If you are currently using the client-server version of Forms Server, migrating applications to Forms Services for the Web is straightforward. This chapter briefly describes the differences between client-server and Web implementations, and then gives guidelines to migrate your current applications from client-server-based to Web-based Forms Services. In addition, you will find white papers and other resources at http://otn.oracle.com.
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.
Text description of the illustration csimp.gif
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.
Text description of the illustration formserv.gif
This chapter will be useful to you if the following statements apply to your deployment environment:
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.
|
Copyright © 2003, 2003 Oracle Corporation. All Rights Reserved. |
|