1. Working with Oracle Forms
  2. Integration
  3. Configuring and Managing Java Virtual Machines
  4. Managing JVM Pooling from Fusion Middleware Control
  5. Forms Configuration File Settings

Forms Configuration File Settings

This section describes the JVM pooling parameters that are used in the Forms configuration file (formsweb.cfg) to enable or disable use of JVM controller for applications. The parameter names are not case-sensitive. You can use Fusion Middleware Control to administer the Forms configuration file.

For information about modifying the parameters in formsweb.cfg, see Managing Parameters.

The following table describes the startup options that you specify in the formsweb.cfg file.

Table -38 Oracle Forms JVM Controller Startup Parameters

Parameter Description
jvmcontroller

Valid values: name of jvmcontroller. In addition, you can specify no JVM by leaving it blank.

Default value: none

Note: To specify this parameter in formsweb.cfg, you must first specify this parameter in otherparams in the form jvmcontroller=%jvmcontroller%. See otherparams in Web Configuration Parameters.

This parameter can be set globally in the default section, or any application section can choose to override it. This tells the Forms runtime process which JVM controller to use. It corresponds to the jvmcontroller parameter for the dejvm executable.

If jvmcontroller does not have a value (jvmcontroller=), then the Forms runtime process will start its own in-process JVM, which means that the Java Importer uses pre-10g behavior.

allowJVMControllerAutoStart

Valid values: true, false

Default value: true

This parameter enables Oracle Forms to run the JVM controller if Forms is configured to use the JVM controller which is not already running.