Oracle Fusion Middleware 12c end of support: each component's 14c path

Who this is for

You run some part of Oracle Fusion Middleware 12c in production: WebCenter, SOA Suite, WebLogic Server, BPM, ADF applications, Forms and Reports, Identity and Access Management, Data Integrator, or Oracle BI. You need one plan for the whole estate, not a separate conversation per product, and you need it defensible in front of procurement and your Oracle account team. This is the umbrella guide. Each component below links to its own detailed path.

The dates that frame every decision

Oracle's Lifetime Support Policy runs every product through the same three stages: Premier, Extended, Sustaining. For Fusion Middleware 12c the boundaries fall like this.

Two consequences follow. The planning year is 2026; the execution boundary is December 2027. And the 12c stack moves together: the WebLogic domain under a WebCenter estate is on the same clock as the WebCenter software running in it.

The support-dates table keeps the per-component dates in one place, and the Sustaining versus Extended note covers what each tier does and does not deliver after December 2026.

Fusion Middleware 12c is not Oracle Database 12c

A large share of the people who arrive at this page searched for "Oracle 12c end of support" and meant the database. They are different products with different lifecycles. Oracle Database 12c's support windows closed years ago. This guide is about Oracle Fusion Middleware 12c, release 12.2.1.4: the middleware layer that WebCenter Content, WebCenter Imaging, SOA Suite, WebLogic Server, Forms, Identity Management and Data Integrator all run on. If you run any of those, you are in the right place.

Every 12c component, and where it goes next

This is the map. Find the components you run, note whether each has a 14c release, and follow the link to the detailed forward path.

Two of the entries carry dates outside the December 2026 / 2027 pattern, and those two are what most often catch an estate plan out. Forms 14c and IAM 14c shipped in 2025 with their own runways; OBIEE's window closed before the rest of the stack.

Two kinds of decision

The 12c estate splits cleanly. Naming which kind each component is, and writing it down, is what turns a list of products into a plan.

Upgrade: most of the stack

WebCenter, SOA Suite, WebLogic, BPM, ADF, Forms and Reports, Identity and Access Management, and Data Integrator all move 12c to 14c (14.1.2) with Oracle's Upgrade Assistant and supported patterns. The work is real: inventory, an out-of-place or side-by-side upgrade, customization migration, re-certification of the database and Java tiers, and validation against production-shaped volume. But the architecture and the investment in it carry forward, and the component lands on a fresh support window. For WebCenter Content specifically, the out-of-place upgrade procedure and the validation checklist are the two documents to read next.

Replace: BI and Endeca

Two components have no 14c release. OBIEE / Oracle BI 12c moves to Oracle Analytics Server or Oracle Analytics Cloud. Oracle Endeca has no successor, so the search and discovery capability it provided needs a new home. These are re-platforming projects with their own data-migration and user-acceptance shape, and they sit on a different clock from the rest of the estate. In practice BI leads the sequencing for that reason alone.

Before you plan a single 14c upgrade: the 12.2.1.4 baseline

Oracle supports the upgrade to 14.1.2 from 12.2.1.4 (or 12.2.1.19 where a component ships that line). A component still on an older 12c release, 12.2.1.3 or earlier, has to move to 12.2.1.4 first, and only then to 14c. That changes the number of steps in the path, the test effort, and the calendar.

So the first thing an inventory establishes is not "what do we run" but "what release is each thing on". The WebCenter Content component inventory tool and the content-server inspector exist to pull that answer out of a running WCC instance quickly; for SOA, WebLogic and the others, the Oracle Home version and the domain's registered components give the same answer.

Sequencing an estate into the window

No two estates are the same, but the dependency graph usually produces the same order.

1. Inventory and baseline. Every component, every release, every customization and integration point. Confirm the 12.2.1.4 baseline. This is two to four weeks on most estates, and it is the step that stops the rest of the plan from being a guess.
2. The replacements. BI (and Endeca, if present) start first because they are re-platforming projects with their own timelines and because their support windows do not line up with the rest of the stack.
3. The foundation. WebLogic 14c is what every other 14c component runs on. The domain and the Java tier (17 or 21) go first; the database tier is re-certified alongside.
4. The integration tier. SOA Suite and BPM as one workstream, with the composite-by-composite validation that 11g-era patterns require.
5. The application tier. WebCenter (Content, Imaging, Capture, Forms Recognition, Portal) as an out-of-place domain upgrade, then ADF customizations against the 14c runtime.
6. The independent products. Forms and Reports and Identity and Access Management can run in parallel with the above where the teams allow it; ODI once its repository backup is verified.
7. Parallel run and cutover. 12c and 14c side by side through UAT, then a cutover per component or per workstream, never for the whole estate in one weekend.

For a WebCenter-centred estate the 12c end-of-support decision guide works through the same sequence with the WebCenter-specific dependencies (Inbound Refinery, Imaging, Capture, Portal) drawn in. The decision guide tool turns it into a scored answer for your estate.

What "supported until" actually buys you

The dates above are worth reading precisely, because the tiers behind them are not the same thing. Premier Support delivers new fixes, new certifications and new regulatory updates. Extended Support narrows to security patches and Severity 1 fixes, for one further year at an uplift. Sustaining Support runs indefinitely but delivers only patches that already exist: no new security fixes, no new certifications, no new regulatory updates. Market Driven Support is a negotiated, year-by-year arrangement that Oracle approves case by case.

For most estates the useful read is: December 2026 is when new fixes stop; December 2027 is when new security patches stop. Where a component upgrades cleanly to 14c, the upgrade is the cheaper way to stay patched. Where it does not, or where the estate is being retired on a known date, the Sustaining versus Extended analysis sets out when the wait-it-out math works and when it does not. The TCO calculator puts numbers beside the two.

How ECMWorks does this

Two decades of Fusion Middleware delivery, most of it inside WebCenter estates that also carried SOA, WebLogic, ADF and an ERP integration, is the background we bring to an estate plan. The engagement shape is the same on most estates.

• The estate read. We read the running 12c implementation directly: the Oracle Homes and their releases, the WebLogic domains, the SOA composites, the WebCenter components and Forms Recognition projects, the ADF customizations, the EBS or Fusion integration code. No documentation hunt and no workshops asking your team to reconstruct decisions from years ago. Output: a component-by-component map, each one marked upgrade or replace, each one with its baseline and its dependencies.
• The sequenced plan. The map becomes a dated plan into the December 2026 / 2027 window: which workstream leads, what runs in parallel, where the irreversible steps are and what backs them up, what test scope each cutover needs. It is written to be handed to procurement and to your Oracle account team as-is.
• Delivery and support. For the components you want delivered rather than planned, we run the upgrade workstreams, and after cutover the estate can move onto a support retainer so the 14c environment has someone who knows it.

The 12c end-of-support decision guide is the WebCenter-specific companion to this page, and the hub for every 12c to 14c upgrade path lists the per-component guides.