Oracle Forms Configuration Files Oracle Forms External Dependencies Oracle Forms Log Files

14-18 Oracle Fusion Middleware High Availability Guide

14.4.1.5 Oracle Forms Runtime Considerations

The Oracle Fusion Middleware Forms Services is made up of three components: a Forms Client that is downloaded automatically to the end users client machine and cached, the Forms Listener Servlet, and the Forms Runtime, on the middle tier. Oracle Forms Client Java Applet When a user runs a Forms session, the Forms Client, a thin 100 percent Java Applet, dynamically downloads from the Oracle Fusion Middleware Application Server. This generic Java Applet provides the classes for rendering the user interface for the associated Forms Runtime process on the middle tier, and handles user interaction and visual feedback, such as that generated by navigating between items or checking a checkbox. The same Java applet is used for all Forms application, therefore it is downloaded only once and cached on the client and so is available for subsequent Forms applications. In order to run a Java applet in a browser, it is necessary to have a Java Runtime Engine JRE installed. The JRE is installed on the client and is platform dependent. Oracle Forms Runtime Process The Forms Runtime process is the process that maintains a connection to the database on behalf of the Forms Client. The process is created when a user accesses a page containing a Forms application. The process is automatically stopped when the user closes the Forms application or terminates the browser window. Oracle Forms Listener Servlet The Forms Listener Servlet manages: ■ The creation of a Forms runtime process for each client when a user requests to run a Forms application. ■ The Forms Listener Servlet is also in charge of stopping the runtime process as the user closes the Forms application or terminates the browser window. ■ Network communications between the client and its associated Forms runtime process

14.4.1.6 Oracle Forms Process Flow

The various components of Oracle Forms Services contribute to the process of running and Oracle Form as follows: 1. Client requests a form by contacting a server through a URL. 2. Oracle HTTP Server routes the request to Oracle WebLogic Server 3. Oracle WebLogic Server creates a forms Runtime process to run the form. If a middle tier server crashes or a servlet session is interrupted, recover from either failure by restarting the application. A new Forms Runtime is created by doing so and any unsaved data can be reentered. The unsaved data does not cause database corruption since Forms uses atomic transactions which guarantees that database saves happen in an orderly and defined manner.

14.4.1.7 Oracle Forms Configuration Files

The following table shows configuration files used by Oracle Forms: Configuring High Availability for Oracle Portal, Forms, Reports, and Discoverer 14-19

14.4.1.8 Oracle Forms External Dependencies

Oracle Forms requires an Oracle HTTP Server to service requests. Optionally these requests may be cached by Oracle Web Cache, in which case it also acts as a load balancer. Oracle Forms uses Suns Java plug-in JRE on the client to run the Forms Java Client.

14.4.1.9 Oracle Forms Log Files

The following table shows log files used by Oracle Forms: File APPHOST1 Location APPHOST2 Location formsweb.cfg DOMAIN_ HOMEconfigfmwconfigserve rsWLS_ FORMSapplicationsformsapp_ 11.1.1config DOMAIN_ HOMEconfigfmwconfigserve rsWLS_ FORMS1applicationsformsapp _11.1.1config default.env DOMAIN_ HOMEconfigfmwconfigserve rsWLS_ FORMSapplicationsformsapp_ 11.1.1config DOMAIN_ HOMEconfigfmwconfigserve rsWLS_ FORMS1applicationsformsapp _11.1.1config basejpi.htm DOMAIN_ HOMEconfigfmwconfigserve rsWLS_ FORMSapplicationsformsapp_ 11.1.1config DOMAIN_ HOMEconfigfmwconfigserve rsWLS_ FORMS1applicationsformsapp _11.1.1config Registry.dat DOMAIN_ HOMEconfigfmwconfigserve rsWLS_ FORMSapplicationsformsapp_ 11.1.1configformsregistryor acleformsregistry DOMAIN_ HOMEconfigfmwconfigserve rsWLS_ FORMS1applicationsformsapp _ 11.1.1configformsregistryor acleformsregistry frmweb.res UNIX: ORACLE_ INSTANCEconfigFormsCompo nentformsadminresourcela nguage Windows: ORACLE_ INSTANCEconfigFormsCompo nentforms UNIX: ORACLE_ INSTANCEconfigFormsCompo nentformsadminresourcela nguage Windows: ORACLE_ INSTANCEconfigFormsCompo nentforms jvmcontroller.cfg ORACLE_ INSTANCEconfigFRCompone ntfrcommontoolsjvm ORACLE_ INSTANCEconfigFRCompone ntfrcommontoolsjvm forms.conf ORACLE_ INSTANCEconfigOHSohs1 moduleconf ORACLE_ INSTANCEconfigOHSohs1 moduleconf File Location Description WLS_FORMS.log DOMAIN_HOMEserversWLS_ FORMSlogs Log file for the WebLogic Managed Server 14-20 Oracle Fusion Middleware High Availability Guide

14.4.2 Oracle Forms Protection from Failover and Expected Behavior

Oracle Forms has no serializable state, which means that transparent failover is not possible. If a runtime process fails, the client process served by that server process also fails. Oracle Forms employs atomic database transactions. With atomic transactions, a set of data, a record, or set of records, is either fully saved or not saved at all. As a result, the failure causes data not yet saved to be lost in a defined and precise manner. The data must be re-entered by the user when the application is restarted. If the process failed as a result of the machine it ran on failing, a substantial part, or all of the existing capacity to service the user base may be unavailable. In this scenario the application as a whole may be unavailable. To ensure continuity one option is to have redundant capacity either in an active-active or active-passive configuration. WLS_FORMS.out DOMAIN_HOMEserversWLS_ FORMSlogs Supplemental log file for the WebLogic Managed Server. This is generally the first place to look for WebLogic issues. Various ORACLE_ INSTANCEFormsComponentf ormstrace Forms trace files, generated if a Forms runtime process fails. The filename has the format: forms_runtime_process_ dump_process_id Forms runtime process does not write to a log file under normal operation Various DOMAIN_HOMEserversWLS_ FORMSlogs Listener Servlet logs File Location Description