Form Server Connection pooling - Urgent

Question

how does form server maintains connection pooling. I have defined a single db user through which form server establishes connections with the db, and created application users at application level. The information I like to know if form server maintains certain connection pooling and allow users to get connected if user limit exceeds but responed to them with delay. if it does maintains connection pooling then please elaborate how.???

Answer 1

Forms doesn't do connection pooling -- each user requires a separate database connection.
> Allowing remote Internet user connect directly to the
database appears to pose a serious security/denial-of-
service risk.
So this is one of the good reasons to move the web Forms architecture.
> It doesn't seem appropriate to ask unaffiliated remote
users to know about, let alone remember database
credentials for an external database, just to enable
them to use a simple web-enabled form. Embedding the
database credentials into the form appears to pose a
more obvious security risk.
With Forms on the web, you can hide the username/password/database details from the user. That information can be stored centrally -- either with Forms itself, or with an LDAP server. The end user doesn't have to know any of the details.
We have customers running their Forms applications on the internet, and the users have no idea of the connection details to the database.
For extra security, you can use SSL. Forms on the web, though, by default uses 40 bit encryption.
Why then does Oracle Forms use this client-server
architecture? Are there any plans to migrate away from,
or provide an alternative to, this architecture in
the near future?
We do have an architecture to resolve these issues. It's called the Forms Listener Servlet Architecture and it's been available for over 2 years.
If you go to the Forms area on OTN, you can read all about it:
http://otn.oracle.com/products/forms/content.html
Regards,
Robin Zimmermann
Forms Product Management