Forms Server

http://download.oracle.com/docs/cd/A97335_02/apps.102/a86202/toc.htm

Oracle Forms in Applications FAQ [ID 177610.1]

COMPONENTS OF ORACLE FORMS PRODUCTS :

1. The standalone Oracle Forms product is composed of the following:

   1. Forms Builder            - this program is used to create and modify Forms modules. 

   2. Forms Compiler         - this program is used to generate your FMX files. 

   3. Forms Runtime          - this program is the engine that runs your Form logic when you form is deployed in client/server. 

   4. Forms Metric Server  - this program is used in Forms load balancing. 

   5. Forms Metric Client   - this program is used in Forms load balancing. 

   6. Forms CGI                 - this program dynamically generates the applet html that defines your form. 

   7. Forms Server             - this program listens for Forms Runtime engine requests. 

   8. Forms Web Runtime  - this program is the engine that runs your Form logic when your form is deployed over the web. 

2. These are the various Forms component names on Unix and Windows:

3.  

4.   

5.   

6.   

7.   

8.   

9.   

10.   

11.   

12.   

13.   

14.   

15.   

16.   

17.   

18.   

 What is f60webmx?

The f60webmx is your web forms runtime executable, similar to f60webm except that it has Apps specific user exits linked into it. 

 How can you recreate the f60webmx executable?

To do this you issue the following command: adrelink force=y "fnd f60webmx" 

What are some of the related Forms/Apps files?

adfmcctl.sh - located in $COMMON_TOP/admin/scripts, this script starts and stops the Forms Metric Client for your Apps instance; it uses the Forms d2lc60 executable to accomplish this.

adfmsctl.sh - located in $COMMON_TOP/admin/scripts, this script starts and stop the Forms Metric Server for our Apps instance; it uses the Forms d2ls60 executable to accomplish this.

adfrmctl.sh - located in $COMMON_TOP/admin/scripts, this script starts and stops the Forms Server Listener; similar to and actually calls the f60ctl found in $ORACLE_HOME/6iserver/bin of IAS.

appsweb.cfg - located in $OA_HTML/html/bin, this file defines parameter values used by the Forms Web CGI, similar to formsweb.cfg found in $ORACLE_HOME/6iserver/forms60/server of IAS.

appsbase.html - located in $OA_HTML/<language>, this is the default HTML file for starting an applet using Jinitiator, similar to basejini.htm found in $ORACLE_HOME/forms60/server of IAS.

d2lc60.txt - located in $COMMON_TOP/admin/install, this is the Forms metric client log file.

d2ls60.txt - located in $COMMON_TOP/admin/install, this is the Forms metric server log file.

f60svrm.txt - located in $COMMON_TOP/admin/install, this is the adfrmctl.sh log file. This is not the same as the Forms server log file which not only logs startup and shutdown info but also client connectivity (which client IP is associated with which f60webm process) and debug stack trace info.

OracleApplications.dat - located in $JAVA_TOP/oracle/apps/fnd/formsClient, among other things this file determines the path Apps uses to find their icons; its similar to and supplements registry.dat found in $ORACLE_HOME/forms60/server of IAS.

What is the ICX: Forms Launcher system profile option for?

This profile option is used by the Self Service Web Applications Personal Home Page (also known as ICX) to determine the base URL needed to launch an application, which in this case is a Forms application. 

?ICX: Forms Launcher? is set to ?http://machine_name:port/dev60cgi/f60cgi?. In Apps release 11i you can add some parameters to this URL to enable some Forms features like tracing.