Oracle Forms

Oracle Forms & Webswing

Oracle Forms & Webswing

Oracle Forms in an open world with Webswing and HTML5. Modernise, mobilise, and integrate Oracle Forms without code changes.

Why Webswing for Oracle Forms

Run your Oracle Forms in any browser, on any device, Java-free. Deliver a modern HTML5 experience, integrate APEX (and other web apps) side-by-side, and keep your proven Forms logic intact. All with zero client installs and enterprise-grade operations.

If your teams rely on Oracle Forms but are stuck with FSAL/JWS launchers, per-machine Java, and an aging UI, Webswing gives you a safe, incremental path forward. Your Forms continue to run server-side; users get a pure HTML5 UI in any browser. No JRE, no plugins, no extensions. You keep proven PL/SQL logic and triggers while opening the door to modern UX, testability, and enterprise-grade operations.

public

Use on all platforms - Java-free

Your users only need a browser. No JRE, no FSAL/JWS, no plugins. Roll out to Windows, macOS, Linux, iPadOS, Android without touching your Forms code.

auto_awesome

Modernise UI without a rewrite

Refresh your UI with HTML5/CSS step-by-step. Render Forms controls as web components and apply styles; or go further with an HTML panel to embed modern content right in the Forms window.

sync_alt

Forms + APEX in one window

Run APEX, reports, charts, maps or your React/Angular pages together with Forms in a single browser tab. Pass events both ways to create seamless flows.

Why this matters now

The classic Forms model isn’t natively portable to the browser, doesn’t embed easily inside modern web apps, and isn’t touch-friendly. Applets are long gone; FSAL/JWS complicate rollout and updates, and it’s hard to add progressive features or test at scale. Many teams want a web experience without a risky migration, a way to modernise step-by-step while maintaining the business logic that works.


Teams want a web experience without a risky migration. A way to modernise step-by-step while maintaining the business logic that works.

How it works

Webswing executes Oracle Forms on the server and renders the UI as HTML5 in the browser.

End-users need only a standard browser. No client Java, no FSAL/JWS, no extensions. Despite running in the browser, you keep "desktop-like" comfort: printing, clipboard, secure file upload/download (including drag-and-drop), and reports opening as PDF in a new tab. Operations are enterprise-ready from day one: SSO, reverse proxy, clustering, auditing, metrics, cloud-friendly delivery.

When you're ready, you can refresh the look via CSS and Web Components or inject HTML content directly into the Forms window.

For hybrid scenarios, the JavaScript ⇄ Forms bridge lets you pass values and trigger events between web content and Forms (e.g., using dispatchCustomEvent/FBean or the JS link described in the deck).

That's how you can place APEX reports or other web pages alongside Forms and orchestrate a seamless flow.

Common use cases

devices

Mobile Access

Straight-through mobile/web access to existing Forms - fastest path to "Forms on iPad/laptop/anywhere."

auto_awesome

Modernisation

UI modernization with HTML5/CSS while keeping your PL/SQL and Forms triggers.

sync_alt

Hybrid apps

Hybrid apps that combine Forms with APEX, reports, dashboards, maps, docs, and videos - all in one tab.

Do you have a special use case? Book a scoping call and we'll map your path from "as-is" to "modern" with minimal change.

What your team gets

business_center

For IT leaders

  • check

    Extend life of critical Forms systems without a risky rewrite

  • check

    Cut rollout headaches. No JRE on clients, updates deploy once to everyone

  • check

    Enterprise-grade ops: SSO, reverse proxy, clustering, metrics, and cloud options

code

For developers

  • check

    Keep your Forms code as-is; iterate UI with HTML/CSS when ready

  • check

    JS bridge for tight integration with web stacks and APEX

  • check

    First-class testing support: Webswing Test Tool, JMeter plugin, QF-Test

Integration & modernization without the big rewrite

The most popular pattern is Forms + APEX in a single browser tab. You can also embed React/Angular or plain HTML to enrich a legacy process, pass data both ways via the JS bridge, and progressively move the pieces that benefit most from the web while leaving core PL/SQL where it shines. As you go, you can render Forms controls as HTML Web Components and apply CSS for a fresher, accessible look.


Deployment and delivery

cloud_done

Deploy anywhere

Run on-prem or in the cloud (OCI-ready), with ready-to-run images if you want a head start.

dns

Works with what you have

Oracle Forms 14.x, side-by-side with APEX, reports, and charting tools.

widgets

Flexible rollout

One app, multiple configurations for different teams, regions, or customers.

Ready to see your Forms in a modern browser on any platform and device?

Quick FAQ

Do we need to change our Oracle Forms code to use Webswing?

No, in most cases. You can put your existing Forms into a browser with Webswing without changing the Forms code. Not sure if your customisations need changes? Please contact us and we’ll review your specific Forms setup together.

Is the client really Java-free?

Yes. End users only need a browser. No JRE, no FSAL/JWS, no plugins or extensions. If you need to validate browser and device compatibility for your environment, please contact us and we’ll walk you through the options.

What about printing, clipboard and file upload/download?

Printing, clipboard and file transfers are supported directly from the browser, including drag-and-drop and opening reports as PDF in a new tab. If you have special printing or file-handling needs (e.g. label printers, legacy drivers), please contact us so we can propose a suitable setup.

OR READ OUR FAQ

Support & limitations

Today Webswing supports Oracle Forms 14.1.2 and 12.2.1.19 and runs with Java 8, 11, 17, and 21 (with 25 planned in future releases). Because the UI runs in the browser sandbox, standard web security rules apply (CORS, CSP, cookies). That means limited access to local file systems, network drivers, registry, and external desktop apps, and WebUtil usage is therefore constrained. If you rely on deep OS integrations, let's discuss patterns that fit your use-case.