3.2 Configuration Files

3.2.1.1 default.env

Location: forms/server

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 PATH and LD_LIBRARY_PATH.

3.2.1.2 formsweb.cfg

Location: forms/server.

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 (envFile setting).

• Most of the servlet configuration parameter settings that you set during installation. You can modify these parameters, if needed.

Variables (%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".

3.2.1.3 base.htm, basejini.htm, and basejpi.htm

Location: forms/server.

The baseHTML files (base.htm, basejini.htm, and basejpi.htm) are used as templates by the Forms Servlet when generating the HTML page used to start up an Oracle Forms application.

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".

3.2.1.4 ftrace.cfg

Location: forms/server.

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".

3.2.2.1 web.xml

Location: j2ee/OC4J_BI_FORMS/applications/formsapp/formsweb/WEB-INF/web.xml.

Once Forms Services has been installed and configured, the web.xml file is located in the directory j2ee/OC4J_BI_FORMS/applications/formsapp/formsweb/WEB-INF in ORACLE_HOME. It defines the aliases frmservlet and lservlet for the Forms Servlet and the Forms Listener Servlet.

For more information about web.xml, see Appendix C, "web.xml".

3.2.2.2 Directory structure for Oracle Forms OC4J files

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:

ORACLE_HOME/j2ee/OC4J_BI_FORMS/applications/formsapp 

+META-INF 

-application.xml (defines the structure of the ear file)

+formsweb 

+WEB-INF 

-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)

3.2.3.1 forms.conf

Location: forms/server.

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".

3.2.4.1 Registry.dat

Location: forms/java/oracle/forms/registry

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".

3.2.5.1 Default webutil.cfg

Location: forms/server.

This file provides all of the configuration settings for webutil, including:

• Logging Options

• Installation Options

• File Upload and Download Options

• Server Side Logging Options for logging errors and log messages

For more information, see Appendix C, "Default webutil.cfg".

3.2.5.2 Default webutilbase.htm

Location: forms/server.

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".

3.2.5.3 Default webutiljini.htm

Location: forms/server.

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".

3.2.5.4 Default webutiljpi.htm

Location: forms/server.

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".