Form Modes - Socket and Servlet

Form Modes in Oracle application:

1. Socket mode
2. Servlet mode

Oracle Applications Release12 by default configures Forms 10g stack in servlet mode, and this is the recommended deployment model for forms on the web. Java servlet called the Forms Listener Servlet manages the communication between the Forms Java Client and the OracleAS Forms Services. It uses the HTTP server port and does not need extra ports to handle the communication between client and the oracle application server.

There are circumstances, where we need to have socket mode. Socket mode allows desktop client to use Forms server directly. Hence, it has some positive impact as compared to servlet mode.

Servlet mode has high network traffic as it uses http protocol on each transaction between client and form server for exchanging cookies and https headers.

Listener executable name in 10g AS is frmsrv present in $ORACLE_HOME/bin.

$ ./adformsctl.sh status to check form status if it is in servlet mode.

$ ./adformsrvctl.sh status to check form status if it is in socket mode.

Manually Starting/stoping/status of Forms Server in socket mode:

$INST_TOP/admin/scripts/adformsrvctl.sh start

$INST_TOP/admin/scripts/adformsrvctl.sh stop

$INST_TOP/admin/scripts/adformsrvctl.sh status

Step to change the mode of forms as below:

1.Source the environment on the application tier.

2.Stop all the application tier services:

$ADMIN_SCRIPT_HOME/adstpall.sh

3.Run the following command to enable Forms Socket Mode:

$FND_TOP/bin/txkrun.pl -script=ChangeFormsMode \

[-contextfile=] \

-mode=socket \

[-port=] \

-runautoconfig= \

-appspass=

Note: appspass is required only if we choose runautoconfig=yes.

4.Start all the application tier services:

$INST_TOP/admin/scripts/adstrtal.sh

5.Check whether Forms Server is running:

On UNIX:

$INST_TOP/admin/scripts/adformsrvctl.sh status or INST_TOP/admin/scripts/adformsctl.sh status