13-8 Forms Services Deployment Guide
envFile=myEnvFile.env where myEnvFile.env is located in the formsserver directory.
5.
If you changed the Oracle 6i Forms Services HTML template files, then make the same changes to the Oracle Forms Services HTML template files.
6.
Start the application with this URL: http:hostname:portformsfrmservlet?
config=application
13.2.6 Upgrading the Forms Listener Servlet Architecture to Oracle Forms Services
In Oracle9iAS Forms Services Release 6i, the Listener Servlet, if not aliased, is accessed by the oracle.forms.servlet.ListenerServlet. The Listener Servlet
configuration exists in the jserv.properties file and the zone.properties file.
In Oracle Forms Services, the Forms Listener servlet is the same except for the servlet names, which are frmservlet and lservlet, and the servlet container. The
configuration is performed during installation. The Listener Servlet configuration in Oracle WebLogic Managed Server is stored in DOMAIN_HOMEserversWLS_
FORMStmp_WL_userformsapp_11.1.1random_ stringwarWEB-INFweb.xml. Some initialization parameters, like the
envFile parameter, need no longer be configured with the servlet engine, because they are moved to the formsweb.cfg file.
The Forms Listener servlet is automatically configured during the Oracle WebLogic Server installation. The installer creates a virtual path forms pointing to the Oracle
Forms Services configuration, formsapp and formsweb.
To access the Forms Listener servlet test form, request the following URL: http:hostname:portformsfrmservlet?form=test.fmx
Ability to access this page means that the Forms Listener servlet is configured and ready to use. frmservlet is the access name configured for the Forms servlet during
installation. The name of the Listener Servlet is lservlet.
Follow these steps to upgrade the Listener Servlet architecture to Oracle Forms Services:
1. Copy the Forms application files to a new directory and upgrade them to Oracle
Forms Services modules.
2. Edit the formsserverdefault.env file, adding the location of the upgraded
Forms application modules to the Forms_Path variable.
Note: If you need to change the underlying HTML files, you should
make a copy of the provided template files before editing them. Save the edited HTML files under a different name, and leave the default
templates provided with the installation unchanged. This prevents overwriting of your customized HTML template files when patch sets
are applied to the application.
To use your own template files with applications, use these parameters in the system section, or one of your custom application
definitions: baseHTML=your base template.htm
Upgrading to Oracle Forms Services 11g 13-9
3.
Copy all of the custom application settings from source_ OH
Forms60Serverformsweb.cfg and append them to destination_ Domain_Dir
configfmwconfigserversWLS_ FORMSapplicationsformsapp_11.1.1configformsweb.cfg.
4.
If an application requires its own environment file, then instead of defining a servlet alias for the Listener Servlet, set the envFile parameter in the custom
application definition section in destination_Domain_ Dir
configfmwconfigserversWLS_ FORMSapplicationsformsapp_11.1.1configformsweb.cfg to point
to the new environment file. For example: envFile=myEnvFile.env
where myEnvFile.env is located in the formsserver directory.
5.
If you changed the Forms Services Release 6i HTML template files, then make the same changes to the Oracle Forms Services HTML template files.
6.
Start the application with this URL: http:hostname:portformsfrmservlet?
config=application
13.2.7 Upgrading Load Balancing
