In Oracle9i Forms Can I run Forms
using a Separate Forms Listener Process?
No. In later patches to Forms 6i, we introduced a new way of
running Forms on the web, without the need for a separate Forms Listener
process. This is a Java Servlet called the Forms Listener
Servlet. In Oracle9iAS Forms Services (the version of Forms in Oracle9iAS v2) the
Forms Listener Servlet is the only supported way of deploying Forms.
In Oracle9i Forms Can I call a
Forms application using the Forms CGI?
No. In later patches to Forms 6i, we introduced a new way of
building the start page for a Forms application, the Forms Servlet.
This Java Servlet does the same job as the Forms CGI, namely the
construction of an HTML page based on configuration information supplied on
the URL in combination with the formsweb.cfg file. In Oracle9i Forms, this Servlet should be used instead of the CGI.
Do I still need to download JInitiator on the client to run a Forms application?
JInitiator is a Java Virtual Machine (JVM) that plugs into either Netscape
Communicator or Microsoft Internet Explorer to provide an alternative
JVM to that which those browsers provide.
Depending on the client
platform the browser is running, we are supporting the following JVMs:
- Windows32
- Oracle JInitiator (with Netscape and Internet Explorer)
- Internet Explorer 5.x native JVM
- Macintosh
- Apple MRJ 2.2.3 (with Internet Explorer 5.0)
- Solaris
For more information on the level of certification and possible restrictions,
please refer to the "Client Platform Support" statement of direction
available on OTN ().
What is the difference between the Forms Servlet and the Forms Listener Servlet?
The Forms Servlet is in charge of dynamically generating the HTML page containing the necessary
Forms Client information.
The Forms Listener Servlet is the architecture for Internet deployment.
The Forms Listener Servlet manages the communication between the Forms
Java Client and Oracle9iAS Forms Services in Oracle9iAS.
Can I deploy my Forms application over the Internet through firewalls
and proxies?
Yes. Oracle9iAS Forms Services supports
a wide range of firewalls and proxy servers.
When will the Forms Listener Servlet use HTTP 1.1 requests to the Web
server,
and when will it use HTTP 1.0 requests?
The Forms Listener Servlet will always make HTTP 1.1 requests if the
Web server and any intervening proxies, support this protocol level. The
Servlet will drop down to using HTTP 1.0 if Web server or one of the proxies
can only support that level of the protocol.
How can I manage and monitor Oracle9iAS Forms Services activity remotely?
Oracle9iAS Forms Services is integrated with Oracle Enterprise Manager (EM)
to allow the administration and the monitoring of the Oracle9iAS Forms Services. From the
browser based EM console, you can monitor the client sessions running within
a Forms Service, viewing how much memory and CPU each is using.
Individual sessions can even be killed from the EM console.
How do I run my
Oracle9iAS Forms Services applications in several different languages on the same
machine?
Multiple entries for a particular application can be defined in the
formsweb.cfg file, with each application name suffixed with the country
code, for instance HR, HR.DE, HR.FR and so on. When a URL is
submitted with the value CONFIG=HR, the Forms Servlet will detect for
the submitting browsers language code and look for a suitable version of
HR with that code appended. Thus a user running a browser in
French would pick up the HR.FR version of the configuration. If a
particular configuration and language code combination is not found in
the formsweb,cfg, then the base configuration (in this case HR) will be
used. Each of the country specific versions of the HR application
can define settings such as the environment file accordingly.
How can I best measure the memory requirements if my application is
on the middle tier?
It is tempting to use operating
system tools such as Task manager
on Windows or ps on UNIX to provide a figure
for memory consumption, based on the amount of memory shown to be consumed
by a single session, and multiplying by the projected population.
However, these utilities give a misleadingly high figure for memory consumption,
as they fail to take into account the extensive sharing of memory that
takes place between concurrent Forms sessions.
The only way to test the scalability of an application is to define a realistic
usage scenario and simulate the activity of concurrent users by playing
back this scenario. When the performance degrades significantly, you have
reached the maximum number of users on the machine configuration.
You can then calculate the memory consumption per user accordingly.
Tools, such as Mercury LoadRunner,
are available to help simulate such user loads.
|
Bookmark
