Fusion Middleware Control provides a Web-based environment to manage all available JVM pooling options. It also lists all JVM controllers in your environment and allows you to (remotely) manage them.

For example, you can start and stop JVM controllers; add new ones; or reconfigure existing ones. In addition, Fusion Middleware Control also provides metric information such as resources (memory and CPU) that are consumed by JVM controllers, number of Forms connected, total JVMs, and so on.

While the Forms runtime process interacts directly with a JVM, the JVM controller manages the JVM, such as starting and stopping a JVM, or getting the state of one, and so on. For example, when an administrator stops the JVM controller, the JVM controller ensures that all child JVMs are terminated. You use Fusion Middleware Control to manage the JVM controller.

The JVM controller can be started in three ways:

• From Fusion Middleware Control

• When a Forms application that is bound to an existing JVM controller requests that the controller start up

• From the command line

Fusion Middleware Control reads the JVM controller configuration file. The configuration contains name-value pairs, has a default section, and has named sections. The parameters contained in jvmcontrollers.cfg correspond to the start parameters of the JVM controller.

When you start a JVM controller, it takes its settings from the configuration file. You may specify none, some, or all options in this file, both in the default section and in named sections.

Use the JVM Configuration and JVM Controller pages in Fusion Middleware Control to manage JVM pooling tasks:

• Common Tasks in the JVM Configuration Page

• Managing JVM Configuration Sections

• Managing Parameters

• JVM Configuration Parameters and Default Values

• Starting and Stopping JVM Controllers with Fusion Middleware Control

• Forms Configuration File Settings

• Startup Example