FireFox, IE crash with Forms 10g, Replace Jinitiator with JRE. Basics of Deploying Oracle Forms Applications. Once you have created your application in Forms Developer, you are ready for application Web deployment. Oracle Forms Services accesses an application in Oracle Fusion Middleware through a specified URL. The URL then accesses the HTTP Listener, which communicates with the Listener Servlet. The Listener Servlet starts a Forms run time process frmweb. Windows or frmweb on UNIX and Linux for each Forms Services session. Deploying Your Application. To deploy a basic form with the default parameters set up by the installer Create your application in Forms Developer and save it. The. fmb file is a design time file that can only be opened in Forms Developer. The. fmx file is the run time file created when you compile the. Web deployment. For more information about Forms Developer, see the Help menu in Forms Developer. Modify the formsweb. Oracle Forms Services can access your application module. You edit this file in the Web Configuration page of Fusion Middleware Control. For more information, see Section 4. Fmx Is Not A Forms Runtime File' title='Fmx Is Not A Forms Runtime File' />, Download last version of tools components. Configuring Forms Services. Table 3 1 shows the configuration of an application called myapplication with a form module called formhrapp. Table 3 1 Example of Configuration Section Parameter Values. Configuration Section Name. Forms Module Name Valuemyapplicationhrapp. When configured, the Oracle Forms Services module hrapp. Web by entering. URL the name of the Web Configuration section in formsweb. Note The name of the configuration section must not include spaces and must contain only alphanumeric characters. Make sure the. fmx file location is specified in the FORMSPATH environment variable. For example, in Windows, if your. FORMSPATH, include d myfilesapplications. On Windows, use semi colons to separate directory locations if specifying multiple locations. On UNIXLinux, use colons for separators. Specify this information in the Environment Configuration page for the environment file. To modify an environment file, select the file in the Environment Configuration page of Fusion Middleware Control and add or edit environment variables as needed by your application. For example, you can add the environment variable shown in Table 3 2. Table 3 2 Example of Environment Variable Values. Environment Variable Name. Environment Variable Value. NLSLANGNLSLANGGERMANGERMANY. Dota Games Frozen Throne. WE8. ISO8. 85. 9P1. If you specified these environment variables in an environment file, specify this environment file in the respective configuration section of the formsweb. Web Configuration page. Enter the name of your application in the URL as shown http example. HTTP Listener. Once you have created a configuration section, add config and the name of the configuration section. In this example, the URL to access hrapp. Specifying Parameters. There are two ways to predefine parameter values for your Oracle Forms Services applications. You can define parameters by Editing your application settings in the default section of the Web Configuration page of Fusion Middleware Control. The default configuration section displays the default values that are used by Oracle Forms Services. Managing adding, editing, copying, deleting other system and user parameter values in the named application configuration section see Section 3. Creating Configuration Sections in Fusion Middleware Control. For example, in the configuration section you create for my. App, you can add or change these parameters and their values, as shown in Table 3 3. Table 3 3 Example Configuration Section Parameter Values for my. App. Parameter Name. Parameter Valuebase. HTMLmybase. htmbase. HTMLjpimybasejpi. Note Parameters specified in the named configuration section of a Web Configuration override the settings in the default section. Note System Parameters cannot be overridden in the URL, while user parameters can. Creating Configuration Sections in Fusion Middleware Control. Under the configuration sections you created in step 2 of Section 3. Deploying Your Application, you can specify parameters for your Oracle Forms Services applications. You can specify any application and system parameters that are available in the default section for Web Configuration page. For example, you can set the look and feel of the application to the Oracle look and feel by setting the look. And. Feel parameter to the value of oracle and clicking Apply. You can also override the default parameter values in the named configuration section. For example, to predefine the connect information of an application to scotttigerorcl, the parameter value for userid must be set in the named configuration section by changing the parameter value of userid to scotttigerorcl. For other parameters that you can edit, see Chapter 4, Forms Configuration Parameters. Editing the URL to Access Oracle Forms Services Applications. You can directly type parameters in the URL that accesses your Oracle Forms Services application. N Lite Page. Using the previous example, instead of specifying the form parameter in your configuration file, you could also type it into the URL as follows. You can use the ampersand to call a combination of a form and named configuration parameters. In the above example, you are calling the form hrapp with the parameter settings you specified in myapplication. Specifying Special Characters in Values of Runform Parameters. Certain considerations apply if values passed to runform parameters contain special characters. This section describes these considerations, and compares the default behavior in this release with the behavior in prior releases. Runform parameters are those that are specified in the server. Args applet parameter of the template HTML file. The value specified for the server. Args parameter in the template HTML file, after variable substitution, is sometimes referred to as the command line parameters string. It consists of a series of blank separated namevalue pairs. The name must consist solely of alphanumeric or underscore characters. The value portion of a namevalue pair can be an arbitrary string. Default Behavior in the Current Release. The value of a runform parameter can be specified in one of three places In the value of the server. Args parameter in the template HTML file for example, base. In the value of a variable specified in the configuration file for example, formsweb. Such values are typically maintained using Fusion Middleware Control see Chapter 4, Configuring Forms Services. As an attribute value in a URL, which is substituted directly for a variable reference in 1 or 2. For case 3, URL syntax rules as enforced by the browser and the application server require that certain characters be entered as URL escape sequences followed by 2 hexadecimal digits representing the ASCII value of the character, for a total of three characters. This requirement includes the character itself which must be entered as 2. In addition, Oracle Forms Services currently requires that the quote character be entered as 2. URL syntax rules also allow a space to be entered as a as an alternative to the URL escape sequence 2. However in the value of the otherparams configuration parameter, a is treated specially it separates namevalue pairs as opposed to indicating a space embedded in the value of a runform parameter. For example, if a runform application has user parameters param. URL. otherparamsparam.