To successfully modernise Oracle Forms, think of the task as moving the key functionality and workflows to another platform, rather than simply updating each Form screen. Once you understand the business function supported, extract the logic and migrate to the DB layer. You can then develop and implement the new solution iteratively and have it run in parallel to the incumbent Forms environment. This approach allows you to minimise downtime. Minimising downtime is crucial given the many areas of the enterprise reliant on Oracle Forms, including billing, maintenance, health and safety, and estates.
As we supply and modernise IT solutions in these sensitive environments, our focus in developing this article is on those responsible for keeping those services running. Whether that's IT, facilities and safety, site leadership or senior management, we hope to help you make informed decisions if you consider Oracle Forms to be a technology you want to phase out.
PODTECH
Modernise Legacy Systems with Less Disruption
PODTECH modernises legacy software for mission-critical environments, helping teams plan staged changes while protecting essential operations.
VisitTL;DR
- Modernising Oracle Forms will require redevelopment and redesign. As per Oracle's recommendations, any logic contained within Forms, such as triggers, programs and events, should be migrated to the DB as stored procedures, functions or packages before the interface is rebuilt.
- No quick fix exists. Oracle's own panel discussion on Forms modernisation suggests that in most cases there will be significant redevelopment required, although existing Forms code should be leveraged wherever possible. Existing Forms blocks used in production also need to be identified.
- Develop incrementally. Identify a discrete block of Forms supporting a particular process, redevelop it, validate it, and implement it in parallel to the current live Forms instance while sharing the same DB.
- Scoping is the dominant cost driver. Determining the scope of work required will be the main factor in sizing cost and duration, so begin with an inventory of current Forms usage.
- PODTECH offers a staged modernisation service. We provide a service designed to help organisations undertake incremental modernisation in high-stakes settings.
Table of Contents
- Why organisations are replacing Oracle Forms now
- What modernisation actually involves
- Your options, by type
- A step-by-step route that limits risk
- The challenges that decide the outcome
- Cost, effort and timeline: what drives them
- Our perspective on Forms modernisation
- Modernise Forms without disrupting operations
- FAQ
- Sources
Why organisations are replacing Oracle Forms now
If anything, Oracle Forms is likely to comprise some of the longest-standing, poorest documented and highest-value systems in your organisation. The original developers will typically have long since departed, leaving opaque processes underpinned by undocumented rules to support core functions that cannot be switched off.
There are commonly 3 factors that lead organisations to seek to decommission Oracle Forms:
- End-user requirements. The Forms product does not offer an equivalent experience to the other digital channels employed by end users across the wider organisation. On Oracle's dedicated Forms modernisation webpage, the key motivations to migrate are highlighted as improved UX, alignment with modern cloud technology and lowering TCO.
- Limitations of the product. Oracle Forms 14.1.2 is the latest version and can only be reached via an upgrade path from 12.2.1.4 and 12.2.1.19. Earlier releases therefore require at least an initial jump to one of these. Oracle's planning document also discusses the need to allocate new Oracle Homes for in-place and out-of-place upgrades. Finally, Oracle has deprecated the use of the
sign_webutilscript and removed support for in-built Java Applets, as noted in the release notes. - Desire to extend data capture and connectivity. Many businesses want to empower their workforce with mobile devices, integrate data with other software suites, or connect to external systems such as BMS, electrical distribution and telecommunications. Using Forms as a springboard is unlikely to prove effective.
Naturally, upgrading to a later version of the Forms suite may address some of the above concerns. In particular, Oracle state that the 14.1.2 release builds on top of Oracle Database 23.5.0 and improves the efficiency of WebUtil file transfers by around 30%, as described in the release notes. However, the end user will continue to see the existing Forms screens, drive through the incumbent process flows and face similar restrictions around extending the system's reach. Modernisation therefore offers the opportunity to transform the capabilities of the system.
What modernisation actually involves
An Oracle Forms system comprises 3 components: the UI, the application logic and the underlying database. Clearly the latter two represent the bulk of the intellectual property and capability delivered.
It is therefore unsurprising that Oracle advise that the process of migrating an Oracle Forms environment is not as simple as converting the relevant files to another format. Rather, the application logic resident in the Forms, including triggers, programs and events, needs to be lifted into the database as stored procedures, functions and packages prior to commencing work on the UI. Importantly, this gives rise to 2 considerations:
Undocumented logic — Whether that relates to an ad-hoc business decision to enforce an action against records where a certain form item was not populated, a conditional based on the logged-in user's privileges, or a piece of formula code executed as part of a WHEN-VALIDATE-ITEM event. These actions and dependencies will not be readily apparent from reviewing the current UI, but could result in serious compliance issues or disruption if inadvertently dropped.
Existing logic in the DB — As Oracle highlight, if there are any existing programs, including stored procedures and packages, in the database, these can be invoked by a web-based replacement of the Forms interface with no modification. Thus, significant amounts of logic developed over the lifetime of the current system may be transferable.
As such, the initial output from your programme will typically be an audit. What forms, reports, common libraries, navigational structures, background processes and related assets does your environment contain? Are these in active use, by whom, for what input and output, and what else relies on them?
How to proceed
You will generally see one of four paths taken. Which is appropriate will vary based on the depth of embedded logic, expected life of the current application and required connectivity.
| Path | Description | Applicable to |
|---|---|---|
| Upgrade existing Forms | Migrate to an actively supported version of Oracle Forms and retain current functionality | Systems unlikely to require significant overhaul for a period |
| Web-based, DB-centric redevelopment | Retain PL/SQL, create a new web front-end, and operate concurrently against the existing DB | Applications with a high degree of DB dependency |
| Custom build | Develop a new web and potentially mobile solution using APIs, based on current key processes | External connectivity, mobile requirements, or strong commercial drivers |
| Off-the-shelf | Stop developing internally and migrate to a third-party solution | Lower-value, repeatable functions |
It's worth noting Oracle's guidance that Forms and APEX may be run concurrently against a set of common database tables and views to fulfil complementary functions. This is a desirable arrangement regardless of destination, allowing incremental migration of user groups.
In many instances, an optimum combination of the above will emerge. Existing DB logic should be preserved as far as possible; some elements will require new development to meet connectivity, mobile and efficiency demands; others can simply be dropped. As discussed earlier, this requires informed judgement and the input of experienced engineers. We have dedicated Web Development and Mobile Development practices to undertake these aspects.
Recommended programme flow
This reflects Oracle's guidance, with some additional considerations for live business systems:
- Audit all areas and determine level of utilisation
Oracle suggest evaluating the degree of utilisation of individual Forms components prior to undertaking redevelopment. For many mature systems there will be considerable inactivity, representing development savings if removed. Do not assume knowledge from existing records. Corroborate with live data, key personnel and static inspection.
- Identify and capture DB logic
Catalogue all logic implemented in triggers, PL/SQL and shared objects. Determine where this should be retained, moved or removed. Redesign will often become apparent at this stage, as will the need to demonstrate continuity of control in certain industries.
Avoid a direct "lift and shift" of legacy logic.
- Define initial focus point
Identify a suitably scoped area to prepare for redevelopment, including associated DB tables and views to streamline or remove. Ideally this should be sufficiently material to justify effort, but not so high-priority as to preclude later activity.
- Develop and validate
Complete the new solution, migrating and or exposing the relevant logic. Rigorously validate in all respects, including exceptions, security and downstream impact. Running alongside production datasets will give significantly better insight than limited test scenarios.
- Cutover
With the ability to leverage common underlying DB assets, you can migrate successive cohorts of end-users. Remain able to revert at least until you can observe one complete business interval, such as month-end, a routine cycle or a compliance check.
- Decommission
Once confirmed that no activity remains and associated reporting has been signed off, begin to de-provision Forms resources and associated costs.
There are precedents for successful execution even with limited resources. For example, Oracle cite the Louisiana Office of Technology Services' programme to update 37 Forms and 58 Reports, completed by 2 engineers. Clearly each situation will differ, but it's possible to achieve significant benefit if the remit is clearly bounded and existing DB assets can be maximised.
Key issues to consider
The extent of logic embedded within the system, spanning database triggers, navigation, LOVs and notifications, will shape the programme. There will need to be suitable software support and staff with the requisite technical knowledge and commercial insight.
Integration. Almost certainly, your application will integrate with other applications: finance, business intelligence, estates, fixed assets or IT assets. If you're working in the datacentre, they may well be BMS, PMS and or NMS. You'll want to consider API exposure from the outset. We have extensive experience of BMS and PMS integration.
Web security and identity. You'll need to factor in SSO, user entitlements, logging and encrypted storage into your development process.
Latency and volume. While the Forms client will happily hammer the DB over a LAN, web-based clients can suffer if there's distance involved or significant data to return. Be thoughtful about database queries and splitting results across multiple requests.
People. Long-serving operators will have deeply ingrained muscle memory from their use of Forms. Get them engaged in the project, replicate key functionality in the replacement solution and compare how quickly they complete core tasks. Don't make the lives of busy administrators worse.
Data collection in the field. This is likely to be a frequent requirement for construction, facilities and health and safety functions. See our post on considerations for collecting data in the field. A longer read on developing fit-for-scale enterprise solutions, incorporating mobile, can be found here.
Migrating the existing database. This may be straightforward if you retain the current DB, but otherwise you'll need to plan data translation and perform dry-runs of the cutover. We've published blueprints for migrating databases for high-stakes scenarios.
Factors affecting cost and duration
As noted above, there are few public data points to reference. Instead, consider these:
- The volume of live Forms and Reports
- Complexity of each component, including the number of input items and the volume of PL/SQL in triggers and custom programs
- The number of external applications requiring integration
- The replacement target. APEX comes at no additional cost with Oracle Database. However, you'll need an Oracle Forms licence to run the status quo. While licensing is a material consideration, the balance will typically fall towards the work required to build and migrate the solution and train users.
- Whether you run the new and old in parallel. This will increase the overall timescale, but reduce the commercial impact of failure. We'd expect this to be a standard requirement.
- Resource continuity. Having a core team of consultants committed through the full lifecycle of the programme will ensure greater transfer of learnings than intermittent teams.
You won't be able to get a realistic assessment prior to completing an audit of the current estate. Expect a sequence of milestones, with the initial output achievable within a matter of weeks.
Why we focus on Oracle Forms
Oracle Forms applications are arguably the most relied upon, yet opaque, technology in place across much of the corporate world. As long as they continue to perform, there is little impetus to look further. Once some limiting factor of the current stack becomes apparent, or a new capability is required, the opportunity arises.
We begin our analysis by seeking to understand the functional requirements of each application. Having identified areas of strength and weakness, we then proceed to rebuild iteratively, ensuring continued availability throughout. This is a position we've reached after delivering 250+ projects, frequently in highly regulated industries.
Furthermore, we recognise that the modernised application will need to interface with a host of supporting systems. Depending on the circumstances, we can deploy specialist resources or augment your internal teams to embed capability locally.
Finally, our guarantee of 99.9% availability demonstrates our confidence in the resilience and level of cover provided for mission-critical software.
Harry
How we help
Through our Legacy Modernisation offering, we enable Enterprise, Data Centre and Estates IT groups to transition legacy systems to contemporary, future-proofed architectures. We can provide both fully dedicated and augmented teams, leveraging our track record of delivering in mission-critical settings. Alternatively, review a similar recent project via our Legacy Modernisation case study and get in touch at podtech.com.
Frequently asked questions
Will my PL/SQL be preserved during the move away from Oracle Forms?
In many cases, yes. Per Oracle, all existing programs residing in the DB, such as stored procedures and PL/SQL packages, can be called from a web application, obviating the need to recode those. Any code embedded within Forms Triggers and Program Specifications will require translation to the DB first. See Oracle's Migration Guide.
Does the whole system need to be decommissioned immediately?
No. The prudent option is to proceed incrementally. Since both the existing Forms implementation and the target system will be using shared schema, you can transition each logical component in turn while retaining the legacy module in place until it completes its next instance of the process.
Will simply moving to Forms 14.1.2 suffice?
Of course you will continue to receive updates and support. However, this will have no impact on the look and feel, processes or connectivity of your systems. Upgrading may therefore form part of the interim solution. You will only be able to perform this if you are currently running at least version 12.2.1.4 or 12.2.1.19. See Oracle's guidance on planning an upgrade.
Can I buy a tool to convert my Forms to another technology?
As described in Oracle's Modernizing Oracle Forms resource, unfortunately the answer is "not really". Expect to undertake significant redevelopment and re-engineering, maximising any opportunity to leverage existing code, and to establish what parts of your current system remain in use. Various tools will allow you to assess and collate the inventory of these.
How do I begin?
Identify all live Forms-based functionality, reporting and other external dependencies. Select a single self-contained set of functions to migrate first. This will provide you with a baseline for the expected costs and timescales for converting the balance of your applications.
References
- Modernizing Oracle Forms, Oracle APEX
- Partner panel discussion on Forms modernisation, Oracle
- Move Oracle Forms applications to Oracle APEX, Oracle documentation
- Planning an upgrade of Oracle Forms, Oracle documentation
- Lifecycle management information, Oracle Forms 14.1.2
- Deprecated and desupported features, Oracle Forms 14.1.2
- Louisiana Office of Technology Services case, Oracle APEX blog
- Enterprise software for scale
