WebCenter on OCI Marketplace vs modernizing off it: Path A and Path B

Who this is for

You run WebCenter for AP imaging on 11g or 12c, on your own hardware, integrated to E-Business Suite or Fusion Cloud ERP. Fusion Middleware 12c Premier Support ends in December 2026 and you have narrowed the response to two candidates: lift the estate onto OCI, or move the AP automation layer off WebCenter altogether. This page puts the two beside each other so the decision can be made on facts about your estate rather than on which vendor got to you first.

Two paths, one date

Every WebCenter AP estate has to respond to December 2026. The two responses that get compared most often:

• Path A: lift and shift to the OCI Marketplace. Keep the WebCenter implementation as it is (architecture, customizations, Forms Recognition templates, SOA composites, ADF forms) and move it onto the Oracle WebCenter images on the OCI Marketplace. What changes is the infrastructure. Often paired with the 12c to 14c upgrade so there is one project, sometimes called Path A+.
• Path B: re-platform the AP layer. Keep the Oracle ERP (EBS or Fusion) as the system of record, keep Oracle-supported integration patterns, and move capture, extraction and approval to a different platform. What changes is the AP automation layer.

Both are legitimate. Path A preserves the WebCenter architecture and moves the platform. Path B preserves the ERP and audit posture and replaces the layer on top. Neither is a shortcut; both are projects.

What Path A actually is

Oracle publishes Linux images for WebCenter on the OCI Marketplace (release 24.11.1 onwards). Each contains the WebCenter product binaries (WebCenter Content 12.2.1.4), Fusion Middleware Infrastructure and the JDK, and deploys as a customer-managed system on OCI compute. You bring your database, your file store, your configuration and your customizations. OCI Object Storage becomes available as the content tier, and the rest of the OCI catalogue sits alongside.

The application does not change. The Forms Recognition templates still need maintaining, the SOA composites still encode the approval matrix, the ADF coding form still needs a developer to change. What you have removed is the hardware, the OS patching, and the data-centre dependency, and what you have gained is supported infrastructure with a straightforward path to 14c. The AP-to-OCI note covers the sequencing and the repository migration plan covers the content store in detail.

Path A+ adds the 12c to 14c upgrade to the same project. On most estates that is the better version of Path A, because the alternative is landing on OCI on a release that leaves Premier Support within months.

What Path B actually is

Path B is not one product; it is a category of decision. The AP automation functions WebCenter currently provides (capture, extraction, coding, routing, archive) move to a platform whose operating model fits the AP team better, while the ERP stays where it is and the integration stays on Oracle-supported interfaces: Payables Open Interface on EBS, Oracle Integration Cloud and FBDI on Fusion, no base-table writes. The options, Oracle's first:

• Fusion Cloud ERP's native Payables capabilities, where the organisation is moving to Fusion anyway. Capture and recognition come with the ERP; the question becomes what to do with the WebCenter archive. The WebCenter to Fusion AP migration guide is the detailed treatment.
• OCI services assembled into an AP pipeline. Document Understanding for extraction, Integration Cloud for routing and ERP integration, Object Storage for the archive. The WFR versus Document Understanding comparison covers the extraction question directly.
• A third-party AP platform integrated on the same Oracle-supported interfaces. Evaluate on the operating model (how extraction improves, who maintains what, how exceptions are handled) rather than on feature lists.

In every variant the WebCenter Content archive of record has its own decision, and frequently the answer is that it stays on 14c on OCI because that is where the retention and audit obligations attach.

The decision matrix

Choose Path A when

• The AP team is satisfied with current WebCenter functionality and the UX around it.
• The supplier mix is stable, so the Forms Recognition template library is not growing fast.
• The customizations are extensive, well-maintained and understood by people still on staff.
• There is no modernization budget in the next 6 to 12 months and supported infrastructure is the immediate need.
• The 12c to 14c upgrade is being used deliberately to defer the strategic decision to a date of your choosing.
• You have WebCenter operators in-house who will still be there in three years.

Choose Path B when

• The AP team is constrained by template maintenance or by the size of the verifier queue.
• Supplier-email triage (status chasing, missing PO numbers, remittance questions) is consuming a measurable share of the team.
• The people who built the templates, composites and ADF forms have moved on, and what they built is not documented.
• The ADF non-PO coding form needs a development cycle for routine changes.
• December 2026 is being used as the forcing function to change the platform rather than to defer.
• A Fusion Cloud ERP migration is planned, and the AP layer's future is part of that programme.

Path A first, Path B later

This sequence is common and it is defensible. The lift to OCI is faster and lower-risk, it lands the estate on supported infrastructure before December 2026, and it leaves the AP layer decision to a moment when budget and organisational appetite align. The cost is paying twice, once for the lift and once for the eventual re-platform. The mitigation is to do the inventory once, properly, at the start of Path A, so that Path B starts from a documented position rather than from another discovery pass. The TCO calculator models the two-phase cost against a single Path B project over your planning horizon.

How ECMWorks does this

We plan and deliver both paths, and the assessment is built to evaluate them neutrally against your estate rather than to arrive at a predetermined answer.

• Implementation read. A fixed-scope read of the running WebCenter estate: Forms Recognition templates and their maintenance load, SOA composites, ADF customizations, FIPSA configuration, supplier patterns, the AP team's actual workflow, the EBS or Fusion integration. Output: a forward plan that scores Path A, Path A+ and Path B in your context, with the reasons. Yours to keep whichever way you go.
• Path A / A+ delivery. OCI architecture and security setup, the repository and file-store migration, the 12c to 14c out-of-place upgrade, Forms Recognition rules audit, FIPSA assessment, cutover and validation.
• Path B delivery. The translation of the AP process (routing, hold codes, coding rules, exception handling) into the target platform; the Oracle-supported integration on EBS or Fusion; the archive decision and its migration; audit-trail continuity across cutover.
• After cutover. A support retainer for whichever estate you end up running.

The modernization map walks the same decision component by component, and the decision guide tool turns it into a scored recommendation.