C.4 web.xml

For a description and the location of web.xml, see Chapter 2, web.xml.

Advanced users might want to edit the web.xml file to:

• Enable extra testing options.

  If you are having difficulty running Oracle Forms in your Oracle Developer Suite or OracleAS installation, it can be useful to enable certain test options which are not usually enabled for security reasons. To use these options, edit the web.xml file to set the testMode frmservlet parameter to true. Then restart the Web server (or OC4J). The additional options are then visible on the Forms Servlet administration page (which can be accessed at a URL like http://<your_web_server_hostname>:<port>/forms/frmservlet/admin).

• Use a Forms Servlet configuration file other than the standard one (which is ORACLE_HOME/forms/server/formsweb.cfg).

  This can be done by uncommenting and changing the frmservlet's "configFileName" servlet parameter.

• Run Oracle Forms using static HTML pages (rather than the Forms Servlet).

  When Oracle Forms applications are run using a method other than the Forms Servlet (for example, static HTML pages, or JSPs), parameter settings in the formsweb.cfg file are not used. You may therefore need to define servlet parameters for the Listener Servlet, such as workingDirectory and envFile (specifying the current working directory for the Forms runtime processes, and the file containing environment settings to be used).

C.4.1 Default web.xml File

<?xml version="1.0"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
 "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
<!-- $Id: web.xml 29-apr-2004.13:43:19 ahousing Exp $
 Name
   web.xml
 Purpose
   Forms web application (WAR) configuration file
-->
<web-app>
   <display-name>Forms Services</display-name>
   <description>Oracle AS: Forms Services</description>
   <welcome-file-list>
      <welcome-file>lservlet</welcome-file>
   </welcome-file-list>
   <!-- Forms page generator servlet -->
   <servlet>
      <servlet-name>frmservlet</servlet-name>
      <servlet-class>oracle.forms.servlet.FormsServlet</servlet-class>
      <load-on-startup>1</load-on-startup>
      <!-- During product installation the configFileName parameter is
           specified in the orion-web.xml file as a context parameter
           override (in iDS), or as a Java system property (in iAS).  
           It is set to <oracle_home>/forms/server/formsweb.cfg.
           You can override that value here by editing and uncommenting the
           following servlet parameter setting: -->
      <!--
        <init-param>
           <param-name>configFileName</param-name>
           <param-value><your configuration file name goes here></param-value>
        </init-param> 
      --> 
      <init-param>
         <!-- Turn on or off sensitive options on the frmservlet/admin page. 
              For security reasons this should be set to false for 
              production sites.
         -->
         <param-name>testMode</param-name>
         <param-value>false</param-value>
      </init-param>
   </servlet>  
   <!-- Forms listener servlet -->
   <servlet>
      <servlet-name>lservlet</servlet-name>
      <servlet-class>oracle.forms.servlet.ListenerServlet</servlet-class>
   </servlet>  
   <!-- Forms servlet mappings. Allow these paths to the servlets:
           /forms/frmservlet or /forms/frmservlet/*: FormsServlet
           /forms/lservlet or /forms/lservlet/*: ListenerServlet 
   -->
   <servlet-mapping>
      <servlet-name>frmservlet</servlet-name>
      <url-pattern>/frmservlet*</url-pattern>
   </servlet-mapping>
   <servlet-mapping>
      <servlet-name>lservlet</servlet-name>
      <url-pattern>/lservlet*</url-pattern>
   </servlet-mapping>
   <!-- The following context parameter is only defined here so it can be 
        overriden by the (site-specific) value in the orion-web.xml file.  
    -->
    <context-param>
       <param-name>configFileName</param-name>
       <param-value></param-value>
    </context-param>
</web-app>