Blog

In fig. 1-3 shows how a client makes HTTP requests and therefore receives HTTP responses from the Forms Server process. The HTTP listener acts as a network endpoint for the client and prevents the firewall from accessing other computers and server ports.

You do not want to configure the Forms Listener servlet if it is already configured for public access during the OracleAS installation.

Process For Launching This Oracle Form

In the article, we are definitely discussing how the Oracle form is executed on the server and how client toys access it.

Oracle ApplicationsForms are designed to implement a three-tier architecture on the Internet. The application logic and the service form runtime reside in the middle tier application server. All trigger processing is done in the databases and hands-on servers, and UI processing is done in the Forms client. End users can run Forms Developer applications in a web browser.

Before we dive into the execution process, let’s take a quick look at the Forms Services architecture. Forms Services consists of four main components: clearly the forms servlet, the Java client (form client), the form listener servlet, and the form execution engine.

A Forms Servlet is a Java Servlet (class) capable of creating a beautiful dynamic HTML file in a standalone browser.

Java client or Forms client (applet) does not work, but several Java classes are loaded onto the client computer the first time a Form application is started on the client computer. The sole purpose of this component is to render every form in the browser and send those user actions to the middle tier. You don’t need p Download a separate Java applet for each application. A generic applet is used for any Race Forms Services application, no matter how many or how complex it is.

The Forms Listener Servlet is a Java Servlet that runs on a web server with a servlet engine very similar to OC4J. The Forms Listener servlet is actually responsible for managing the assembly associated with the execution of the forms process for each member, and for handling the networking that occurs between the client and the execution of the associated forms process through the web server.

A form engine is a process on a specific application server that is started by all of the form listener’s servlets. The Forms runtime engine supports all of the functionality of the Forms application and logic, and executes code written from the application.

Users request an in-app form in their web browsers by entering any URL that points to the app. Services Forms then generates an HTML file that simply downloads a Java applet to the computer with the software. This little applet can display the user interfaceby any means, while the application logic is executed at the middle tier.

The target URL for invoking a new healthy application must be in the following format:

http: // host% 5B: port% 5D / renders servlet or html file [options] (optional parts of url in square brackets)

Where http is the method, dummysite.com is the host, 8888 is the port number, and form90 / f90servlet is the servlet alias style.

We need to have a Java Runtime Environment (JRE) on the client machine to run our own forms. Can we use JInitiator, a plug-in that provides a JRE that a Forms applet can go through?

Below is the entire process of accessing a web forms application:

1] The user accesses the main Forms application through a URL in one of their web browsers.

2] At the staging layer, the Oracle HTTP or OC4J server receives an HTTP request from the browser client and connects to the forms servlet.

3] The Forms Servlet Dynamically creates an HTML page on the visitor’s computer that contains all the information to start a Forms session.

4] Oracle HTTP Or-Server OC4J downloads a generic applet from the client computer ra when the form is probably called for the first time. The client computer caches the applet so that future Forms applications can run without repackaging it.

5] A male or female machine applet communicates with a medium listening form servlet to start a workshop. The Forms Listener servlet fires the Forms Runtime Engine event on the user’s Forms server (middle tier).

6] The listener servlet establishes a connection to the runtime engine, which connects to the database as needed and loads the application’s executable files.