Determine if Oracle Forms communication should be configured in “socket mode”

Issue 1: Determine if Oracle Forms communication should be configured in “socket mode”

In R12 the communication between the Forms java client and the Forms 10g server is by default configured in servlet mode. While this is the recommended deployment model for web forms, servlet mode is more bandwidth intensive and has a higher resource footprint on the JVMs.

Scripts recorded in servlet-mode are quite different than socket-mode. Failure to configure socket-level before script development will result in substantial script development rework. Socket mode allows desktop clients to access the Forms Server directly, by-passing the Apache web server. The key advantage of servlet mode is better load balancing across multiple app servers.

Three examples of script differences:

Statement in “servlet” mode             Equivalent statement in “socket” mode

web_url("frmservlet",… None;            this statement is no longer present

web_url("lservlet;jsessionid=… None;    this statement is no longer present

nca_connect_server("{url}", "9097",…    nca_connect_server("{url}", "8007",…

                                        <note different port number>

Practical Solution:

Have your Oracle Systems Administrator assess your customer’s needs and point him to Oracle Metalink Document ID 384241.1. If appropriate for this installation, have the system reconfigured in socket-mode before any serious script development.