Upgrading Common Gateway Interface CGI to the Oracle Forms Servlet

13-4 Forms Services Deployment Guide

13.2.3 Upgrading Common Gateway Interface CGI to the Oracle Forms Servlet

This section provides instructions to upgrade Forms CGI to the Forms servlet deployment. Follow these steps if you are using the Oracle 6i Forms Services Common Gateway Interface to dynamically render the Forms Applet start HTML file for applications. CGI deployment for Forms applications was introduced in Oracle Forms Services Release 6i to enable the Forms Applet Start HTML file to render dynamically. Forms CGI uses the formsweb.cfg configuration file and an HTML template to create the start HTML file for an application. The CGI interface is configured by an entry in the Forms HTTP configuration file 6iserver.conf it is referenced by an Include directive in the Oracle HTTP Server oracle_apache.conf file, which contains a ScriptAlias directive identifying dev60cgi for the directory structure containing the ifcgi60.exe file. The Forms servlet renders the HTML in the same manner as the CGI, but also provides an automatic browser type detection. The Forms servlet is configured when you install Oracle Forms Services, and is named frmservlet. To access the Forms servlet, request the URL: http:hostname:portformsfrmservlet This URL is similar to the URL used with the CGI Interface in Oracle 6i Forms Services. To call an application configured as myapp in the custom configuration section of the formsweb.cfg file, request the URL: http:hostname:portformsfrmservlet?config=myapp The Forms servlet is automatically configured during installation. The installer creates a virtual path forms pointing to the Oracle Forms Services configuration, formsapp and formsweb. Follow these steps to upgrade an Oracle 6i Forms Services Release 6i CGI environment to an Oracle Forms Services servlet environment:

1.

Copy all of the application-specific configurations from source_ OH Forms60Serverformsweb.cfg and append them to destination_ Domain_Dir configfmwconfigserversWLS_ FORMSapplicationsformsapp_11.1.1configformsweb.cfg.

2. Configure Forms_Path in the default.env file to point to the upgraded Oracle

Forms Services application modules. Note: Do not copy and replace the entire formsweb.cfg file in source_OH to destination_Domain_Dir. The file in Release 6i is different from the Oracle Forms Services file. Copy only the application configuration to destination_Domain_ Dir configfmwconfigserversWLS_ FORMSapplicationsformsapp_ 11.1.1configformsweb.cfg. Note: You can create a new environment file by copying default.env, modifying it for use with a particular application, and adding envFile=created environment file to the custom application section in the formsweb.cfg file. Upgrading to Oracle Forms Services 11g 13-5 3. If you changed the Oracle 6i Forms HTML template files, then make the same changes to the Oracle Forms Services HTML template files.

13.2.4 Upgrading Static HTML Start Files to Generic Application HTML Start Files