Oracle® Application Server Forms Services Deployment Guide
10g Release 2 (10.1.2)
This section introduces the basic files you need to configure Forms applications. For more advanced configuration topics, see Chapter 4, "Configuring Forms Services".
This section contains the following:
Note:Location of files are given relative to the
Note:If you manually edit any of the configuration or environment files, you'll need to restart Enterprise Manager so that Enterprise Manager can read all changes. If you do not restart Enterprise Manager, any changes that you make through Enterprise Manager will overwrite any manual changes you've made to these files.
This file contains environment settings for Forms runtime and can be found in the
ORACLE_HOME/forms/server directory. On Solaris, default.env should include the
This is the Forms Servlet configuration file that contains the following:
Values for Forms runtime command line parameters, as well as the name of the environment file to use (
Most of the servlet configuration parameter settings that you set during installation. You can modify these parameters, if needed.
%variablename%) in the baseHTML file are replaced with the appropriate parameter values specified in the formsweb.cfg file and from query parameters in the URL request (if any).
You manage the formsweb.cfg file through Enterprise Manager Application Server Control Console.
For more information about formsweb.cfg, see, Chapter 4, "Configuring Parameters with Application Server Control Console".
Oracle recommends that you make configuration changes in the formsweb.cfg file and avoid editing the baseHTML files. If you need to change the baseHTML files, create your own versions and reference them from the formsweb.cfg file by changing the appropriate settings.
For a look at a sample baseHTML files, see Appendix C, "base.htm, basejini.htm, and basejpi.htm Files".
This file allows you to configure Forms Trace. Forms Trace allows you to replace the functionality that was provided with Forms Runtime Diagnostics (FRD) and Performance Event Collection Services (PECS), which were available in earlier releases of Oracle Forms. Forms Trace allows you to trace the execution path through a form (for example, steps the user took while using the form).
You manage Forms Trace through Enterprise Manager Application Server Control Console.
For more information about ftrace.cfg, see Chapter 8, "Tracing and Diagnostics".
By default Forms Services is configured for OC4J by deploying it as a J2EE compliant application packaged in an EAR (Enterprise Archive) file called formsapp.ear. This EAR file is deployed during the Oracle Application Server installation process (if you choose to configure Oracle Forms). During deployment, the EAR file is unpacked into the applications directory of the OC4J instance.
This section describes:
Once Forms Services has been installed and configured, the web.xml file is located in the directory
ORACLE_HOME. It defines the aliases
lservlet for the Forms Servlet and the Forms Listener Servlet.
For more information about web.xml, see Appendix C, "web.xml".
During Oracle Application Server installation and configuration, the Forms EAR file (formsapp.ear) is deployed to the
"OC4J_BI_FORMS" OC4J instance. This results in the following directory structure.
Names with a + sign are directories:
-application.xml (defines the structure of the ear file)
-web.xml (forms & listener servlet definitions, including servlet parameters) -orion-web.xml (virtual directory mappings and context parameter, only used in iDS) +lib -frmsrv.jar (contains the Forms Servlet and Listener Servlet code)
This section describes the file used to configure Oracle HTTP Listener for Oracle Application Server Forms Services.
This is the Oracle HTTP listener configuration file for Oracle Application Server Forms Services. It is included into oracle_apache.conf, which in turn is included into httpd.conf (the master HTTP listener configuration file). forms.conf defines virtual directories (aliases) and servlet mount points to map URL requests to the Forms Servlets running in the OC4J servlet engine.
For more information about forms.conf, see Appendix C, "forms.conf".
This section describes the file used to configure font and icon settings for Oracle Application Server Forms Services.
This file allows you to change the default font, font mappings, and icons that Forms Services uses.
For more information about Registry.dat, see Appendix C, "Registry.dat".
This section describes the files used to configure WebUtil at runtime. For information about using WebUtil at design time, see the Oracle Forms Online Help.
These files are only available in Oracle Developer Suite under
Oracle_Home/forms/server directory. These files are not available with Oracle Application Server or with Oracle Application Server Forms and Reports Services.
This file provides all of the configuration settings for webutil, including:
File Upload and Download Options
Server Side Logging Options for logging errors and log messages
For more information, see Appendix C, "Default webutil.cfg".
This is the default base HTML file for running a form on the Web using a generic APPLET tag to include a Forms applet with a certificate registration for WebUtil.
For more information, see Appendix C, "Default webutilbase.htm".
This is the HTML template file for running a form on the Web using JInitiator-style tags to include the Forms applet with a certificate registration for WebUtil.
For more information, see Appendix C, "Default webutiljini.htm".
This is the default base HTML file for running a form on the Web using the JDK Java Plugin. This is used for example when running a form on the Web with Netscape on Solaris and a certificate registration for WebUtil.
For more information, see Appendix C, "Default webutiljpi.htm".