Oracle Applications Forms R12

Components involved??

Oracle forms server works based on 3 Tier Architecture. A tier is a logical collection of services running on more than one machine.

Client Tier:

 The client browser connects to the form server using the forms client Applet which is running on the local machine. Forms client applet is a collection of Java Archive files (JAR).

Application Tier:

Application tier mainly has 2 components web listener and forms server.

·         Forms server :

o   Maintains all user interfaces and database connection for thin client.

o   Caches data which is needed by forms thin client.

o   Uses HTTP, HTTPS and TCP/IP protocols to communicate with the thin client.

·         Web Listener

o   Sends and receives request for the browser which is running the Jinitiator.

Database Tier:

·         Stores all the data required for the forms thin client.

How it works??

1.       Browser sends request to HTTP Listener.

2.       Web server receives the request.

o   If request is referring to a static file then the file will be retrieved from storage.

o   If request is referring to CGI Script then

§  Static CGI : Retrieve from storage and execute the file.

§  Dynamic CGI : Checks for the available server from load balancing server. Load balancing server basically monitors the current load in all forms server. Forms server runs a thin client of load balancing server to keep the load balancing server informed about the load.

3.       HTTP Listener sends a HTML page to the browser.

o   HTML file has a tag <APPLET> which contains all the information including form server name to be used.

4.       Browser requests for Java Applet to HTTP Listener.

5.       HTTP Listener sends Applet in JAR Files as they can be downloaded more quickly.

6.       Browser receives the JAR files and uses the JVM JInitiator to execute the JAR file.

7.       Browser signs off as the JVM takes care of the Java Applet.

8.       Applet connects to the forms listener which starts a Forms Runtime Engine.

9.       Forms listener passes the command line parameters and any form builder parameters to Forms Runtime Engine.

10.   Forms listener signs off as the Applet is now directly connected to Forms Runtime Engine.

11.   Java applet passes the form information with the required parameters to the Forms Runtime Engine.

12.   Forms Runtime Engine interacts with the database tier to open a database connection to get the data.

Client browser and JRE Version

Below table lists out the JRE version for the corresponding client browser and the information is available in the Oracle support “Deploying JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12 (Doc ID 393931.1)”. Also any form related issues are addressed in the same Oracle Doc ID.

64 Bit version

Browser Version	Windows 8(64 Bit)	Windows 7 (64 Bit)
IE 10	JRE 1.6.0_37 (64-bit) and higher JRE 1.7.0_10 (64-bit) and higher	JRE 1.6.0_32 (64-bit) and higher JRE 1.7.0_10 (64-bit) and higher
IE 9	Not Certified	JRE 1.6.0_32 (64-bit) and higher JRE 1.7.0_10 (64-bit) and higher
IE 8	Not Certified	JRE 1.6.0_32 (64-bit) and higher JRE 1.7.0_10 (64-bit) and higher

 32 Bit Version

Browser Version	Windows 7 (64-bit)1	Windows 7 (32-bit)	Windows Vista (32-bit)	Windows XP (32-bit)
IE 10	JRE 1.6.0_03 and higher JRE 1.7.0_10 and higher	JRE 1.6.0_03 and higher JRE 1.7.0_10 and higher	Not Certified	Not Certified
IE 9	JRE 1.6.0_03 and higher JRE 1.7.0_10 and higher	JRE 1.6.0_03 and higher JRE 1.7.0_10 and higher	JRE 1.6.0_03 and higher JRE 1.7.0_10 and higher	Not Certified
IE 8	JRE 1.6.0_03 and higher JRE 1.7.0_10 and higher	JRE 1.6.0_03 and higher JRE 1.7.0_10 and higher	JRE 1.6.0_03 and higher JRE 1.7.0_10 and higher	JRE 1.6.0_03 and higher JRE 1.7.0_10 and higher
IE 7	Not Certified	Not Certified	JRE 1.6.0_03 and higher JRE 1.7.0_10 and higher	JRE 1.6.0_03 and higher JRE 1.7.0_10 and higher
IE 6	Not Certified	Not Certified	Not Certified	JRE 1.6.0_03 and higher JRE 1.7.0_10 and higher