Proactive insights, news and tips from Oracle Fusion Middleware Support. Learn Oracle from Oracle.

Forms Standalone Launcher (FSAL) FAQ

Alexandra David
Principal Technical Support Engineer

What is the architecture of the Forms Standalone Launcher (FSAL)? Is it an applet?

The Forms Standalone Launcher, also known as FSAL offers a modern style of client/server. FSAL allows users to run Oracle Forms 12c applications similarly to how a typical Java application might be run from their local machine. With FSAL, no browser is used to launch the application. As a result of not using a browser, FSAL does not use the Java Plugin component of a Java Runtime Environment (JRE) or Java Developer Kit (JDK). Information on how to use FSAL can be accessed from a running server using this URL -> http://<server>:<port>/forms/html/fsal.htm

So, is it an applet? Technically, yes, but because of its deployment architecture it has many characteristics of a typical Java application running on a local machine.

What versions of the JRE/JDK does FSAL require?

All that is needed is a certified Java SE installation on the end-user machine. The Java installation needs to be either the Java Development Kit (JDK) or Java Runtime Environment (JRE) or Server JRE.

How do I run/use FSAL?

Basic instructions can be found from every Forms installation on this page -> http://<server>:<port>/forms/html/fsal.htm

java -jar frmsal.jar -url "http://<HOSTNAME>:<PORT>/forms/frmservlet?config=standaloneapp"

Can the frmsal.jar downloaded from one Forms server be used to run against a different Forms server?

Yes, with some restrictions - the versions must match, of course.
In general, you cannot use frmsal.jar that was downloaded from a Windows server to run an application against a UNIX server.

Since FSAL does not run in a browser can one still use it with Single Sign On (SSO)?

This is not possible unless on or higher.

Can FSAL be used with a Load Balancer?

FSAL does not support cookie-based routing using a Load Balancer. Other types of Load Balancing such as IP based or URL Rewrite should work.

How does jar file caching work with FSAL?

Jar files are downloaded as specified using the archive parameter in the formsweb.cfg.
By default, jar files are downloaded in the following locations on the client:

Windows: %USER_HOME%\AppData\Local\Temp\frmsal\<server>\<Forms Version>
UNIX: /tmp/frmsal/<server>/<Forms Version>

Are url redirects or rewrites supported with FSAL?

No. FSAL expects to receive a fully qualified URL that points to the Forms environment.

Will web.show_document() work with FSAL?

Yes. The default browser will be called to bring up the specified url.

What are key configuration files associated with FSAL?

As with other 12c deployment methods, the formsweb.cfg is key. Note that it comes with two configuration sections specific to FSAL:

[standaloneapp] which references FORMS_INSTANCE/server/basesaa.txt


[webutil_standaloneapp] which references FORMS_INSTANCE/server/webutilsaa.txt and contains other webutil related parameters.

Note that like other key configuration files, these files should never be modified manually.  Fusion Middleware Control (FMWC)/EM should always be used.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.