Re: Dev6 deployment: appletviewer or static html

Markus,

You are getting confused here.

There are two types of implementation method, static and cartridge.

The static method requires you to have an HTML file in which you have created the correct parameters on your webserver which will cause the form to load in the chosen client.

The cartridge method refers to a cartridge supplied with OWS 3 and OAS 4, which basically supplies the same HTML by combining a base HTML file (i.e. some HTML with replaceable parameters) with the supplied parameters, form name etc.

The main reason you would use this method, is if you require to balance your load across multiple forms server machines. The reason for this being that the cartridge is the ONLY way that you can get at a parameter called LEASTLOADEDHOST. This parameter is used by the forms metrics server to decide which machine to hand a connection to.

You can mimic the same functionality (e.g. replacable params) by using any scripting language, you just cannot reproduce the LEASTLOADEDHOST

There are three types of client, appletviewer, jinitiator in a browser and native JVM in IE5 patch 1.

Appletviewer, must be installed on every machine and signed using javakey by you. In versions of ODS prior to 2.1 we did recommend the use of Appletviewer. This was due to the differences in the two browser JVM's. We received inconsistent performance from one or the other of them, this is when Jinitiator was introduced, this is a pluggable JVM which we use to provide a stable and performant platform for running forms.

The most recent advance was made with IE5 + Patch 1, this allowed us to run forms natively without installing Jinitiator, however this only works with 6.0 and does not provide the jar caching facility provided with Jinitiator.

In 6i (which has just gone production and will be orderable in a couple of weeks), we have removed the reliance on the OAS cartridge by providing a CGI which does exactly the same thing (and more) as the cartridge. This means that you can now deploy multi server ODS applications without requiring OAS, and using your favourite web server.

We now recommend using jinitiator + browser for all applications because of the performance enhancements we have built in, if you are running in a bandwidth constrained environment then jinitiator is a mandatory requirement, if you are running on a corporate LAN and don't mind downloading the JAR files each time you run, then you can run forms 6 inside the native IE5 JVM.

With patch 1 of 6i we will probably be shipping a CAB file specifically aimed at providing the JAR caching technology for IE5

--
Regards

Jason

____________________________________________________________________________
__

  Jason Pepper - Enterprise Internet Tools Product Management
____________________________________________________________________________
__

Opinions are mine and do not necessarily reflect those of Oracle Corporation

"Markus Janscha" <markus_at_janscha.co.uk> wrote in message
news:8ccreh$jev$1_at_gxsn.com...


> I have been looking at an Dev6 application using both appletviewer and

> static html deployment.

>

> Oracle recommends static and cartridge html files over appletviewer why?

>

> I found that using IE or Netscape the form looked like a picture badly

> pasted into the browser window with ugly edges.

> Also, the form did not re-draw correctly when a user moved the browser

> scroll-bar??  Is this standard functionality or did I overlook something

> with the configuration?

>

> Can someone please tell me why it is better to install a base html file

> rather than the appletviewer.

>

> Thanks

>

> Markus

>

>