How to configure Oracle Forms Standalone Launcher – FSAL

Quick Guide to Oracle Forms Standalone Launcher – FSAL

People have been hearing that Oracle Forms is dead for almost 10 years now. Little do they know that today Oracle Forms is a major participant in the cloud ecosystem! It’s imperative for organizations with major investments in Oracle Forms to understand that they do not need to throw away years of work,  and introduce risk and cost into the system. Their existing back-office system can be leveraged into the next-generation.

Today I would like to highlight a new runtime option to start your application: The Oracle Forms Stand-alone Application Launcher (FSAL) – Oracle definitely looked ahead towards the future with new operating system issues e.g. new browsers and their new behavior in Windows 10.

The Oracle Forms Stand-alone Application Launcher (FSAL)

The FSAL offers an alternative way for end-users to run Oracle Forms applications. FSAL offers a browser-less, more client/server-like interface. 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). All that is required to run FSAL on the end-user machine is a Java installation. This can be either the JDK or the JRE. To determine which Java versions are supported, please contact your administrator.

Starting from the fsal.htm you can load the associated frmsal.jar to the client. So quite simply, this method even works without a browser! But again with JDK or JRE on the client machine.

Sample Call in a command box: java -jar C:OracleMiddlewareOracle_Homeformsjavafrmsal.jar -url “http://w7x6412c-rdbms:9001/forms/frmservlet?config=daylightstandaloneapp&form=lab_540&userid=

user/passwort@db