Oracle middleware licensing, family by family. Three states for every component you run.

Oracle sells no license to Fusion Middleware as a whole. Each of roughly eight product families has its own metric and rules, and most audit findings come from components running on a restricted grant or a lower edition.

How is Oracle middleware licensed?

Oracle middleware is licensed product by product, never as a whole. Fusion Middleware is an umbrella over roughly eight product families, each with its own metric, its own line on the price list and its own audit behavior. Oracle does not sell a license to the umbrella itself.

Every middleware component on your servers therefore sits in one of three states: fully licensed, restricted use, or not licensed at all. Most organizations we review cannot say which state a given component is in, and the software offers no help.

What are the eight families, and where does each one cost you?

Two rows cause most of the trouble, and neither is the application server. Data integration counts both ends of every feed, which doubles what intuition prices. The development and web tier is almost entirely restricted use: real products doing real work on entitlements that lapse the moment the work spreads beyond the parent product.

What do the main middleware products cost at list?

These figures come from Oracle's Technology Global Price List dated September 15, 2026. Annual support is 22 percent of the net license fee, so a license discount carries into every year of support.

What is a restricted use license, and what breaches it?

A restricted use license is a real license, valid only in support of the product that shipped it. The restricted component behaves exactly like the full version, and nothing in the product tells you which entitlement you are running on.

When does bundled WebLogic need a full license?

That depends on which of two commonly confused grants you hold. Oracle's manual says WebLogic Server Basic comes with Forms and Reports and with Business Intelligence Standard Edition. Basic includes basic clustering but excludes whole server migration, service migration, custom Work Managers and many other features.

WebCenter, Identity Management and similar products carry a different grant: a restricted license to a full WebLogic edition, usable only as the host for that product. Your own applications in that domain need a full license, and where the grant is Standard Edition, which has no cluster support, a cluster needs Enterprise Edition.

Can the database that ships with a middleware product hold other data?

No. A restricted use Oracle Database is licensed for the product's own repository schemas and nothing else. Oracle's wording for Directory Services Plus is typical: the included Standard Edition database may only store LDAP data for Internet Directory, and storing any other data requires a full use license.

The breach usually starts small, with a reporting schema, a staging table or a monitoring tool writing its history. Any one of them turns the whole instance into a full use database requirement. If Oracle prices that at Database Enterprise Edition, $47,500 per processor at list, a 4 processor repository host becomes a $190,000 license claim before support.

What does the Java SE that ships with middleware cover?

Oracle's Java SE FAQ says you may use the Oracle Java runtime with, and for the sole purpose of running, the Oracle product that requires it. Any other Java workload, on any machine, falls under the Java SE Universal Subscription.

Our Java audit defense guide covers the employee metric and how Oracle pursues it.

How do the counting rules differ across middleware families?

Each family counts differently, and four rules produce most of the arithmetic errors. Named User Plus minimums alone differ by family, at 10 per processor on WebLogic and 25 on SOA Suite.

• Both ends of the feed. GoldenGate is licensed on the processors of the source and of the target.
• SOA Suite contains Service Bus. Oracle lists Service Bus as a component of SOA Suite for Oracle Middleware, but a Service Bus license gives no rights to BPEL, Mediator or Business Rules. Composites running on hosts licensed only for Service Bus need SOA Suite.
• Both sit on WebLogic Suite. Oracle licenses SOA Suite and Service Bus as options to WebLogic Suite, so every processor that runs them needs WebLogic Suite as well.
• Minimums decide small deployments. On a small host, the minimum sets the bill and your real user count stops mattering.

Worked example: SOA Suite on one host

Say your integration team runs SOA Suite on one 8 core x86 host and has 40 named users. The x86 core factor is 0.5, so the host counts as 4 processors. The table prices both routes at list.

The minimum turns 40 real users into 100 licensed ones, and $48,000 into $120,000, before WebLogic Suite users at $900 each. Once other systems call the host, Processor is usually the only workable route, because Named User Plus also counts devices and automated callers. Our SOA Suite metric comparison works through that choice.

Worked example: one GoldenGate feed

Say you replicate from a 16 core x86 database host to an 8 core reporting host. The source counts as 8 processors and the target as 4. Priced on both ends, GoldenGate needs 12 processors at $17,500, or $210,000.

Priced on the source alone, it would have been $140,000, a $70,000 gap plus $15,400 a year in support for one feed. The GoldenGate licensing guide covers the remaining counting rules.

How are Enterprise Manager packs for middleware licensed?

Per processor of the managed target, and they switch on from a link in the Enterprise Manager console with no warning and no license check. The WebLogic Server Management Pack Enterprise Edition lists at $12,000 per processor. On the 4 processor SOA host above, one enabled pack adds $48,000 in license and $10,560 a year in support.

Treat the Management Pack Access page in Cloud Control, under Setup and then Management Packs, as a purchase screen. Access is set per target: disable packs wherever you hold no license, and reconcile the page against entitlements every quarter.

What have we seen in recent Oracle middleware reviews?

Edition boundaries and restricted use grants drove most of the surprises. Across roughly 30 to 45 Oracle middleware reviews I led between 2024 and 2025, the money sat at the edges between products and entitlements and rarely in the processor arithmetic. Four findings came up again and again.

• Edition creep. In 5 of 10 environments, WebLogic Suite features were running on a lower edition entitlement.
• The repository breach. In roughly 1 in 3, a restricted use database carried other application schemas, a full use claim usually larger than the finding that triggered the review.
• The console click. In roughly 4 of 10, management packs were active in Enterprise Manager with no matching entitlement behind them.
• The product boundary. Counting SOA Suite and Service Bus as one product masked 20 to 35 percent of integration demand.

If you record each component's state before Oracle asks, the audit becomes a reconciliation of your records against theirs. Those settle for a fraction of what an open ended exploration costs.

The exposure in Oracle middleware sits at the boundaries between products and entitlements, and none of those boundaries shows while the software is running.

Why we would not start audit preparation with a core count

The usual advice is to begin with a hardware inventory and a processor count, because that is how Oracle prices. For middleware we disagree. In our reviews, edition mismatches and restricted use breaches produced more exposure than miscounted cores. Classify every component into a family first, settle its entitlement state second, and count cores last.

How does an audit read what you own?

The contract names a processor metric, some minimums and a handful of products. The audit reads the whole umbrella, including the parts you were told came free. Middleware is one of the five Oracle bills in our Oracle licensing guide, and it was missing from more internal license positions than it appeared in. It was never missing from audit scope.

How do you check which state each component is in?

Start with what the software records about itself, then compare it with what you bought. Every check below uses a script, view, file or console page you already have access to.

How does support status change a middleware renewal?

It gives you grounds to cut or move support on releases Oracle has stopped developing. Premier Support for Fusion Middleware 12c ends in December 2026, and Extended Support in December 2027. For SOA Suite 12.2.1.4, Oracle gives December 31, 2026 as the end of Premier Support and points customers to 14.1.2, a long term support release.

Components in Sustaining Support still carry the full support fee, yet they no longer receive new patches or security fixes. Few customers raise that at renewal, and it is one of the better arguments available. Our third party support analysis prices the alternative.

What should you plan before December 2026?

• List every 12c domain by release. Support dates attach to the release, so a domain on 12.2.1.3 or earlier may already be past Premier Support.
• Decide per product. Upgrade to 14.1.2, pay for Extended Support, move to third party support or retire it. Extended Support can carry an extra fee, so get Oracle's figure in writing.
• Recheck the grants on 14.1.2. The grants change between releases, and the 11g manual named more sources of WebLogic Server Basic than today's does. Confirm every restricted grant you rely on still appears in the 14.1.2 edition.

What will Oracle say in a middleware review, and how should you answer?

Oracle's positions in a middleware review rest on the licensing manual, so your answer usually sits in the same manual. These are the lines we hear most often.

• "Clustering is configured, so these hosts need Enterprise Edition." Ask which grant Oracle is reading. Basic includes basic clustering, so the question is which excluded features are configured, and the measurement script answers it. On a restricted Standard Edition grant the point stands, and you choose between removing the cluster and licensing it.
• "The repository database holds other schemas, so it needs full licenses." Ask for the schema list and object creation dates, move the foreign schemas out, and hold Oracle to the edition of the original grant, which is Standard Edition for some products.
• "Management packs were used on these targets." Ask for the target list and access dates from the Enterprise Manager repository, settle on targets with recorded use, and disable access everywhere else the same day.
• "Java on these servers means a subscription for all your employees." Separate the runtimes that serve only the Oracle product from the rest. The claim rests on the second group, and moving that group to an OpenJDK build before you sign changes what you owe from then on.

What to do next

1. Read the manual first. Download the Licensing Information User Manual for each release you run and list the restricted grants you rely on.
2. Classify every component. Give each one a family and a state: fully licensed, restricted use, or not licensed.
3. Audit the repository databases. Compare installed schemas with the registry and move foreign schemas out.
4. Pull the pack access settings. Reconcile Enterprise Manager pack access with your entitlements and switch off what you have not bought.
5. Map support status against Premier Support dates. Bring the December 2026 date into your next renewal discussion. The Oracle practice can run the review with you.

Frequently asked questions