Re: Dev/2000 Applet generation questions.

Jason,

You've correctly described the architecture: Forms server and all program code (fmx, mmx, and pll files) are on the server. A Java applet is downloaded to the client. You are also correct about re-thinking parts of your application in order to minimize network traffic. The examples you give, however, (mouse enter and mouse leave triggers) are not implemented in the Java applet because they would generate excess network traffic. This means that things such as bubble help don't work. Perhaps this functionality can be moved into the Java client at some time (anybody from Forms development listening?).

The amount of network traffic between the Forms server and the Database server will be the about the same as in client/server deployment. So the same types of tuning issues apply. Basically you end up with a bunch of clients doing small network I/O to an application server. Then the application server does LOTS of network I/O to the db server. This can be a good thing: it's much easier to optimize the network between two servers than between 100 PCs and a server.

The biggest thing in deploying using the Forms server and Java applet is to appropriately size your application server. There are some guidelines in the documentation. If you don't have it handy, email me and I think I have it HTML somewhere.

Tim

Martin Bronstein wrote:

> Jason,
> From what I learned so far about running Forms on the Web, the form executes
> on the forms server, while the client only runs a small Java applet that
> manages the GUI interface to your form. Initially a subset of the Java
> classes are downloaded to your browser, with additional classes loaded when
> required, say when an LOV is activated. This will cause a delay the first
> time, but subsequent uses of the LOV will already have the appropriate
> classes available on the client. I think you can specify that all the
> classes load upon initilization of the form, taking the overhead hit up
> front. Since none of the Form application code is processed locally, every
> action on the client requires a trip to the forms server (and possibly the
> database server) and back for the result. You might have to re-think your
> application to minimize this traffic, particulary with mouse triggers (enter,
> leave, etc.)
>
> Martin Bronstein

--
+--------------------------------------------------------------+
|                  http://govt.us.oracle.com                   |
 +--------------------------------------------------------------+
|Timothy E. Taylor             Internet: ttaylor_at_us.oracle.com |
|Technical Account Manager     Office:   301-907-2395          |
|Oracle Government             Fax:      301-657-0037          |
+--------------------------------------------------------------+