Hi,
Could you please help me to understand the process when starting with FSAL?
Following is pick up from deployment guide, but the blue description maybe is suit to HTML starting, what about the FSAL starting?
e.g
1.The user starts the frmsal.jar and goes to a URL such as:
http://xxxxxx:9001/forms/frmservlet?config=standaloneapp
-->Q1:Then how did the weblogic managed server know the request?
2.
Oracle WebLogic Managed Server maps the request to the Oracle Forms Services application that has a context root named /forms.
It maps the request to the Forms servlet using the frmservlet mapping specified in the application.xml file.
3.
The Forms servlet running on the Oracle WebLogic Managed Server processes the request.
The Forms servlet:
- Opens the servlet configuration file (formsweb.cfg by default), which is located in
$DOMAIN_HOME/config/fmwconfig/servers/WLS_FORMS/applications/formsapp_12.2.1/config.
- Determines which configuration section to use in the formsweb.cfg file. In FSAL, the URL contains the query parameter config=standaloneapp,
therefore, the [standaloneapp] section is used.
- Determines which baseHTML file to use, in FSAL default is basesaa.txt.
Reads the basesaa.txt file, and returns the contents as an HTML (or JNLP) page to the user's Web browser, after performing variable substitutions as follows:
Whenever a variable (like %myParam%) is encountered, the Forms servlet looks for a matching URL query parameter (for example, &myParam=xxx), or, failing that,
looks for a matching parameter in the formsweb.cfg file. If a matching parameter is found, the variable (%myParam%) is replaced with the parameter value.
-->Q2:There is no web browser in FSAL, so how to describe the above blue description?
4. Depending on which baseHTML the Forms servlet selected, the HTML page returned to the Web browser contains an applet, object embed, or jnlp tag to start the Forms applet
(thin client). The Forms client runs in the JVM environment provided by standalone Java executable.
-->Q3:For FSAL, how to describe the above blue description?
5.To start the Forms applet, its Java code must first be loaded. The location of the applet is specified by the applet codebase and archive parameters. The virtual path
definition in the weblogic.xml file for /forms/java allows the applet code to be loaded from the Web server.
-->Q4: Is FSAL the same behavior? how can I check this in weblogic.xml?
6. Once the Oracle Forms Services applet is running, it starts a Forms session by contacting the Forms Listener servlet at URL
http://example.com:9001/forms/lservlet.
7.The Oracle HTTP Server listener receives the request. It forwards the request to Oracle WebLogic Managed Server, since the path /forms/lservlet matches a servlet
mapping in the web.xml file (the one for the Forms Listener servlet)
-->Q5: Is OHS listener inside weblogic even though OHS is not installed?
8.The Forms Listener servlet (lservlet) starts a Forms run-time process (frmweb.exe or frmweb) for the Forms session.
9.Communication continues between the Forms applet and the Forms run-time process, through the Listener Servlet, until the Forms session ends.
Thank you and regards,
Emily