Oracle Fusion Middleware licensing, product by product. Where WebLogic and SOA Suite costs grow.

Oracle Fusion Middleware is a family name, not a license. Each product underneath it is licensed on its own metric, and WebLogic Server clusters are where the processor count most often outgrows what you bought.

Does Oracle sell one Fusion Middleware license?

No. Fusion Middleware is a marketing family, and every product inside it is licensed separately, on its own metric and its own price line. Nothing in the family comes bundled with the database, and nothing in it is free because it arrived on the same installation media.

The practical consequence is that your contract file has to be read product by product. A WebLogic domain, a SOA composite and an ODI agent on the same host are three separate license questions, with three sets of minimums and options.

What does each Fusion Middleware product cost at list?

These are the components that generate real invoices, with list prices from the Oracle Technology Global Price List. Support runs at 22 percent of the net license fee every year on top of each line, and Named User Plus carries a floor of 10 users per processor across these products.

Which components fall outside a negotiated middleware discount?

Buyers often negotiate a middleware discount as if it covered a stack, then deploy components that were never on the order. The account team has no obligation to point this out. The components below are the ones we most often find running without a matching order line.

• Identity components. Internet Directory, Access Manager and the identity governance products carry their own metrics. One exception worth checking: Oracle's licensing manual lists Internet Directory inside the Internet Application Server Enterprise Edition components that come with WebLogic Suite, so Suite owners may already hold it. Our identity and access management guide covers the rest.
• Adapters and packs. SOA Suite adapters for packaged applications are the single most overlooked cost line we find.
• Data movement. Oracle Data Integrator and Oracle GoldenGate each carry their own set of licensed machines, and GoldenGate counts both source and target.
• Analytics. Oracle Analytics Server sits on the same price list but is a different product, with a ratio of $221,250 per processor to $2,000 per user that makes the metric choice matter more than on any other line here.
• Coherence. Coherence Enterprise Edition lists at $11,500 per processor on its own and is included only in WebLogic Suite. Teams that switch it on under Enterprise Edition have bought nothing that covers it. See our Coherence cost guide.

What have we seen in recent Oracle middleware reviews?

The middleware tier is usually the blind spot. Across roughly 30 to 40 Oracle middleware engagements I reviewed in 2024 and 2025 (35 of them logged in our engagement file), the database was typically well managed while WebLogic and SOA Suite had grown without anyone counting cores.

• Clusters beyond the license. WebLogic clusters exceeded their licensed cores in roughly 6 out of 10 of the environments we reviewed.
• Restricted use breaches. Custom applications running on an application bundled WebLogic tier appeared in about half of them.
• Unowned adapter lists. Separately licensed SOA Suite adapters and packs were the most overlooked component cost, and in most organizations the list had no owner.

The price step behind the first pattern is steep. Moving from Standard Edition to Enterprise Edition costs 2.5 times as much per processor, and it is the step most clusters force.

Where does the WebLogic edition boundary sit?

The boundary sits at clustering. Standard Edition does not include clustering support, Enterprise Edition does, and WebLogic Suite adds Coherence Enterprise Edition and the Java SE Suite entitlement on top. Almost every expensive middleware surprise we see traces back to a cluster built on a Standard Edition or bundled entitlement.

The table follows the application server chapter of Oracle's Fusion Middleware Licensing Information User Manual. That manual, not the price list, decides what each edition permits, so keep the edition matching your release in the contract file.

What does the boundary cost on a two node cluster?

Take a two node cluster on 16 core x86 hosts. That is 32 cores, and at the 0.5 core factor it becomes 16 processors. On Standard Edition that would be $160,000 at list, except Standard Edition may not be clustered.

The compliant answer is Enterprise Edition at $400,000, or WebLogic Suite at $720,000 if Coherence is in the design. Pay the Suite premium only when the design needs something only Suite includes, such as a Coherence cache.

The Named User Plus row is the cheapest line when it applies. It suits internal applications where you can count every person and device using the system, directly or indirectly. If 120 employees use it, you still buy the 160 user floor, and the bill is $80,000. Anything facing customers or the internet goes on the processor metric.

How do you check your own clusters in five minutes?

Open the WebLogic administration console and look at the Clusters page. If any cluster has more than one managed server, every node in it needs Enterprise Edition or higher. If the entitlement behind that domain came with an application, read the restricted use section below before you relax.

• The domain file. Each domain's config/config.xml lists every cluster, every managed server, the machines they are targeted to and each application deployment. It is the fastest way to audit domains you cannot log in to.
• The installed products. Run opatch lsinventory in each Oracle home to see which middleware products are installed, then match every product to an order line.
• Fusion Middleware Control. Enterprise Manager shows domains, servers and deployed composites in one place, which helps when SOA and WebLogic share hosts.
• The Basic measurement script. For domains running on WebLogic Server Basic, Oracle publishes a feature usage measurement script on My Oracle Support under Doc ID 885587.1. Oracle notes it does not measure every restricted feature, so treat a clean result as partial evidence.

Does the WebLogic license cover the Java it runs on?

Yes, within limits. Each WebLogic edition includes a Java entitlement restricted to running WebLogic, so the JDK under a licensed domain does not need a separate Java SE subscription. The same JDK used by a batch job or another application on that host is outside the grant, which is how Java exposure surfaces during WebLogic migrations.

What is restricted use WebLogic, and how do companies breach it?

Restricted use WebLogic is a real license with real limits, granted so that one Oracle product can run and for no other purpose. The breach is almost always the same: someone deploys a second application into a domain that exists only to serve the first. Three different entitlements circulate, and they are not interchangeable.

What does WebLogic Server Basic allow, and what does it forbid?

Basic permits load balancing, failover, node manager lifecycle management and cluster management. That surprises people who assume every bundled WebLogic forbids clustering. It then forbids a specific list, and that list is where architects get into trouble without noticing.

• High availability. Whole server migration, service migration, managed server cloning, MAN and WAN state replication, singleton services and cluster constraints deployment are not permitted.
• Deployment. Production redeployment with application versioning, application administration mode, changing deployment order and FastSwap are not permitted.
• Server management. Server ADMIN and STANDBY modes, overload management and GridLink data sources for Oracle RAC are not permitted.
• Messaging and web services. Several JMS features, including store and forward agents, and asynchronous or buffered web services are not permitted.
• Tooling. Building custom domains or templates with the Configuration Wizard or the pack and unpack commands is not permitted, and neither are custom Work Managers or the WebLogic diagnostics service (WLDF).

Several of those, including WLDF, custom Work Managers and production redeployment, are features an experienced WebLogic administrator turns on by reflex. Oracle's WebLogic Server Basic licensing page is the authority. Print it and give it to the platform team.

How do you fix a breach without licensing the whole tier?

Separate the domains. A restricted use entitlement is perfectly usable when the product it came with is the only thing running in that domain. Moving one custom application out of a bundled domain onto a small full use footprint costs far less than licensing every core the bundled tier occupies.

As an illustration, say a custom portal sits inside an Analytics Server domain on two 16 core hosts. Licensing that tier for full use Enterprise Edition means 16 processors and $400,000. Rehosting the portal alone on a separate 4 core x86 server needs 2 processors, which is $20,000 on Standard Edition if it runs on one node.

What gets licensed separately around SOA Suite?

More than most companies expect. SOA Suite for Oracle Middleware lists at $57,500 per processor and includes the service bus, BPEL and the technology adapters. The application adapters, the B2B document protocols, the healthcare capabilities and the management packs are priced on their own lines.

Which adapters are included, and which cost extra?

Technology adapters for files, FTP, JMS, databases and web services are part of the SOA Suite entitlement. Adapters that speak to packaged applications are not. The developer tooling hides the difference by listing both kinds side by side in the same palette.

• Included: file, FTP, database, JMS, advanced queuing, socket and web service adapters used within SOA Suite.
• Separately licensed: adapters for packaged applications such as E Business Suite, PeopleSoft, Siebel, JD Edwards and SAP. The E Business Suite, SAP, Siebel and JD Edwards World adapters each list at $17,500 per processor or $350 per Named User Plus.
• Separately licensed: B2B for EDI and B2B for RosettaNet, each at $34,500 per processor.
• Separately licensed: the management packs used to monitor SOA and WebLogic from Enterprise Manager. SOA Management Pack Enterprise Edition lists at $25,000 per processor and WebLogic Server Management Pack Enterprise Edition at $12,000.
• Separately licensed: identity components, including Internet Directory, Access Manager and identity governance.

Where does the SOA processor count land?

SOA Suite is counted on every machine where a composite runs, including the administration server host. A four node integration cluster on 16 core x86 hosts is 32 processors, or $1.84M at list before any adapter. Establish that number before anyone discusses a discount percentage.

SOA Suite also needs WebLogic underneath it, so price the pair together. Oracle's licensing manual names WebLogic Suite as the prerequisite for SOA Suite, which means the same 32 processors carry a second line. The effective cost per node is the sum of both lines, plus any adapter deployed on the cluster.

This is why a discount percentage on its own tells you little. A 60 percent discount negotiated on the SOA line alone applies to less than half of this bill. For the metric choice on the integration tier, see our note on SOA Suite processor against Named User Plus.

Where does Fusion Middleware licensing go wrong?

It goes wrong because middleware is treated as free infrastructure that follows the database. Teams stand up WebLogic clusters and SOA composites without counting cores, and the gap surfaces in an audit that started somewhere else entirely.

What are the recurring gaps, and what does each cost?

• Cluster node counting. Every node in a licensed WebLogic cluster needs a license, including the one that only takes load during failover. In a two node cluster, licensing only the active node leaves half the processors unlicensed.
• Restricted use breaches. Custom applications land on an application bundled WebLogic tier, usually because the domain was already there. The finding covers every core in that tier.
• Options on SOA Suite. Adapters for packaged applications and the management packs are licensed separately and rarely inventoried. Each adapter is priced on the full cluster.
• Disaster recovery. A standby with managed servers started is a running deployment, whatever the runbook calls it.
• Virtualization boundaries. Middleware on a shared VMware cluster carries the same exposure as the database under the Oracle partitioning policy, so every host the virtual machine could move to is in scope.

How should disaster recovery nodes be licensed?

Disaster recovery is a licensing decision as much as an architecture one. Oracle's data recovery policy says that on standby and remote mirror sites, every Oracle program that is installed or running must be licensed. A stopped server with WebLogic installed still counts.

The only exception is narrow and time limited. An unlicensed spare in a failover cluster may run the program for up to ten separate 24 hour periods a year, and only where the nodes share one disk array in a single data center. A WebLogic managed server that is running in a cluster is not that spare.

• License the standby. Simplest to evidence, and the right answer when the recovery time objective needs servers ready to start.
• Keep middleware off it. Rebuild the domains from images or backups when you invoke recovery, and accept the longer recovery time.

Whichever you choose, document it and keep the test records, because an undocumented warm standby is a finding waiting to be written up. Our disaster recovery licensing guide covers cloud standby options.

Why we reject the idea that middleware follows the database license

A common architect assumption is that middleware licensing follows from the database license and needs little separate attention. We disagree. In roughly six out of ten middleware environments I reviewed, WebLogic clusters and SOA composites had grown well past their licensed cores while the database stayed clean, and the unlicensed middleware became the largest single finding.

The better course is to inventory every WebLogic and SOA node, separate restricted use from full use, and license each component on its own metric before a database audit pulls the middleware in with it.

Fusion Middleware is a stack of separately licensed products, and WebLogic is where the count grows fastest.

How does cloud change middleware licensing?

Cloud changes the counting rule, and the rule depends on which cloud you run in. In Oracle's authorized cloud environments, which the current policy names as Amazon EC2, Amazon RDS, Microsoft Azure and Google Cloud Platform, two vCPUs count as one processor license when multi threading is enabled. One vCPU counts as one processor when it is not.

Why the core factor table does not apply in AWS, Azure or Google Cloud

Buyers get this wrong in both directions. Oracle's cloud licensing policy states that the processor core factor table is not applicable in authorized cloud environments. You cannot apply the 0.5 x86 factor on top of the vCPU division, and Oracle will not accept a count that does.

• Sixteen vCPUs with multi threading on. Eight processor licenses, with no further reduction.
• Sixteen vCPUs with multi threading off. Sixteen processor licenses.
• Autoscaling groups. License the maximum configured capacity, whatever the average running count. With multi threading on, a group of 8 vCPU instances set to scale between 2 and 6 needs 24 processor licenses, which is $600,000 on Enterprise Edition at list, even if 3 instances run most days.
• Policy status. The document is a policy and is not incorporated into your license agreement, so Oracle can change it. Put the counting rule that matters to you into your order document.

The most common case is worked through in Oracle WebLogic licensing on AWS, and the wider policy is covered in our Oracle cloud licensing policy guide.

On Oracle Cloud Infrastructure the unit is the OCPU rather than the vCPU. The Bring Your Own License ratio is defined per service, so confirm it in the service description and your order document instead of assuming it matches AWS.

What will the Oracle account team say, and how should you answer?

Expect a handful of recurring lines once middleware comes up in a renewal or an audit. Each has a precise answer, and in most cases the right reply is to ask for the document that settles the point.

• "Your discount covers Fusion Middleware." Ask for the order with every product, metric and quantity listed line by line. A product absent from the order is unlicensed, whatever discount the proposal quoted.
• "WebLogic came with your application, so you are covered." Ask which entitlement: restricted use Standard Edition, WebLogic Server Basic or full use. Then ask for the section of the licensing manual that grants it for the way you run it.
• "Move to WebLogic Suite and the cluster problem goes away." Enterprise Edition already covers clustering at $25,000 per processor. Suite at $45,000 is only worth it if you run Coherence, need Zero Downtime Patching or are licensing SOA Suite on those cores.
• "Your disaster recovery site must be fully licensed." True where middleware is installed there. Ask whether any node qualifies for the failover allowance, and price the option of keeping the standby empty until recovery.
• "12c support is ending, so this is the time to move to cloud." Premier Support for Fusion Middleware 12c ends in December 2026 and Extended Support in December 2027. Upgrading to a current release is covered by the support you already pay, so compare that cost with any subscription offer before you accept the framing.

Upgrade projects create their own exposure. New domains usually run beside the old ones for months, and every installed copy counts, as our note on middleware audits during migration explains.

Which contract terms should you ask for?

Ask for six terms that put your understanding of the license into the order itself, where an auditor has to accept it. Oracle rarely offers them unprompted, and most are easier to win at renewal than during an audit.

1. Product by product order lines. Each product, edition, metric and quantity named. This stops a "middleware" discount being read as a license.
2. Named restricted use scope. Where WebLogic comes bundled, name the application it hosts and the domains it may run. This settles later arguments about what the grant covered.
3. Cloud counting in the order. Write the vCPU to processor ratio for your instance types into the order. The policy can change, and the order cannot without your signature.
4. Disaster recovery rights. Name the standby hosts and the failover arrangement you rely on. It turns a runbook description into a contractual term.
5. A migration window. For 12c upgrade projects, ask for a defined period in which old and new domains may run in parallel on one set of licenses. Without it, the parallel run is a second deployment.
6. Support treatment on reduction. Agree in advance how support is repriced if you retire a product or reduce processors. Oracle's standard repricing rules can erase the saving you expected.

For the broader reference across every middleware family, keep our complete middleware licensing guide and the Oracle knowledge hub to hand. The subscription side of the analytics decision is covered in Oracle Analytics Cloud licensing, and our WebLogic Suite against Standard Edition decision guide works through the edition choice for an existing domain.

What to do next

This sequence works whether you are 60 days or 270 days from a renewal or an audit.

1. Inventory every node. List every WebLogic and SOA Suite node across development, test, staging, production and disaster recovery, with physical core counts.
2. Classify each domain by entitlement. Mark it full use, restricted use or WebLogic Server Basic, and write the source order number beside each one.
3. List the clusters and what else runs in bundled domains. Any cluster on a Standard Edition or restricted use entitlement needs a decision this quarter, and one custom application in the wrong domain can put an entire tier in scope.
4. Inventory the SOA adapters and packs. Name an owner for the list, because in most companies it has none.
5. Check disaster recovery. Record for each standby whether middleware is installed, whether servers run, and when it was last tested, with dates and test records.
6. Recount anything in AWS, Azure or Google Cloud. Count vCPUs without the core factor and at maximum configured capacity.
7. Fix the cheap breaches first. Moving an application out of a bundled domain usually costs less than licensing the tier.
8. License the remaining gaps deliberately. Close them before a database audit pulls the middleware tier in alongside it.

Frequently asked questions