Oracle Fusion Middleware is a family name, not a license. Each product underneath is licensed on its own metric, and WebLogic Server is where the count quietly runs away. This guide maps the components, the edition boundary, and the restricted use traps.
Oracle Fusion Middleware is a family name, not a license. You license each product underneath it on its own metric, and WebLogic Server is where the count quietly runs away. This guide maps what actually gets licensed, where the edition boundary sits, and how restricted use entitlements get breached.
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 is bundled with the database, and nothing in it is free because it arrived on the same installation media.
These are the components that generate real invoices in real estates, with current list prices from the Oracle Technology Global Price List. Support runs at 22 percent of net license fees a year on top of every line.
The middleware map, with list prices
Processor and Named User Plus, list and before discount. Named User Plus carries a floor of 10 users per processor across these products.
| Product | Per processor | Per Named User Plus | Why it appears in your estate |
|---|---|---|---|
| WebLogic Server Standard Edition | $10,000 | $200 | Single node Java applications |
| WebLogic Server Enterprise Edition | $25,000 | $500 | Anything clustered |
| WebLogic Suite | $45,000 | $900 | Clustering plus Coherence Enterprise Edition |
| SOA Suite for Oracle Middleware | $57,500 | $1,200 | Integration, BPEL, service bus |
| Data Integrator Enterprise Edition | $30,000 | $900 | Batch ETL and data warehouse loads |
| GoldenGate | $17,500 | $350 | Change data capture and replication |
| Analytics Server | $221,250 | $2,000 | On premises dashboards and reporting |
| Analytics Publisher standalone | $46,000 | $460 | Pixel accurate document generation |
Buyers negotiate a middleware discount as though it applies to a stack, then deploy components that were never on the order. The account team is not obliged to point this out. Each component has its own metric, its own minimums and its own options, and the paperwork trail is per product.
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 above that. Almost every expensive middleware surprise we see traces back to a cluster built on a Standard Edition or bundled entitlement.
Oracle WebLogic Server edition boundary
| Capability | Standard | Enterprise | Suite |
|---|---|---|---|
| Java EE application server, JMS, JDBC drivers, admin console | Yes | Yes | Yes |
| Clustering support | No | Yes | Yes |
| Whole server migration and service migration | No | Yes | Yes |
| Oracle Coherence Enterprise Edition | No | No | Yes |
| Java SE Advanced or Java SE Suite, restricted to WebLogic use | No | Advanced | Suite |
| Forms, Reports, Portal and Discoverer | No | No | Yes |
Source: Oracle Fusion Middleware Licensing Information User Manual, application server products.
A two node cluster on 16 core x86 hosts is 16 processors after the 0.5 core factor. 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.
Open the WebLogic administration console and look at the Clusters page. If there is a cluster with more than one managed server, the estate needs Enterprise Edition or higher on every node in it. If the entitlement behind that domain came bundled with an application, see the next section before anyone celebrates.
White Paper · Oracle Middleware
Oracle Fusion Middleware Licensing
WebLogic, SOA and Coherence, priced. Read it free.
Restricted use WebLogic is a real license with real limits, granted so that an 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.
Full use, restricted use, and WebLogic Server Basic
| Entitlement | Where it comes from | What it permits | The usual breach |
|---|---|---|---|
| Full use WebLogic | Bought on its own price line | Anything the edition allows, any application | Undercounted cluster nodes |
| Restricted use WebLogic Standard Edition | Bundled inside products such as Analytics Server and Data Integrator | Running that product only. Clustering is commonly excluded | Clustering for high availability, or hosting another application |
| WebLogic Server Basic | Internet Application Server Standard Edition, Forms and Reports, BI Standard Edition | Those components plus custom Java applications, with basic clustering | Whole server migration, service migration, production redeployment |
Source: Oracle Fusion Middleware Licensing Information User Manual, WebLogic Server Basic and application server chapters.
Basic permits load balancing, failover, node manager lifecycle management and cluster management, which surprises people who assume all bundled WebLogic forbids clustering. It then forbids a specific list. That list is where architects walk into trouble without noticing.
Every one of those is a feature an experienced WebLogic administrator turns on by reflex. Oracle's WebLogic Server Basic licensing page is the authority, and it is worth printing and handing to the platform team.
Separate the domains. A restricted use entitlement is perfectly usable if 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 is far cheaper than licensing every core the bundled tier occupies.
More than most estates realize. 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 and healthcare capabilities, and the management packs are priced on their own lines.
Technology adapters for files, FTP, JMS, database and web services are part of the SOA Suite entitlement. Adapters that speak to packaged applications are not. That distinction is invisible in the developer tooling, which lists them side by side in the same palette.
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. That is the number to establish before anyone discusses a discount percentage.
Because SOA Suite requires WebLogic underneath it, price the pair together. A clustered SOA estate carries WebLogic Server Enterprise Edition or WebLogic Suite on the same cores, so the effective cost per node is the sum of both lines, not the SOA line alone.
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.
Oracle's failover allowance is narrow, time limited, and does not cover a warm standby with servers running. Decide deliberately whether the standby is cold, and evidence it. A tested, documented cold standby is defensible; an undocumented warm one is a finding waiting to be written up.
It changes the counting rule, and the rule depends on which cloud you are in. In Oracle's authorized cloud environments, which the policy names as Amazon EC2, Amazon RDS and Microsoft Azure, two vCPUs count as one processor license when multi threading is enabled, and one vCPU counts as one processor when it is not.
This is the detail buyers get wrong in both directions. Oracle's cloud licensing policy states plainly that the processor core factor table is not applicable when counting 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.
The practical worked example for the most common case sits in Oracle WebLogic licensing on AWS, and the wider policy position in our Oracle cloud licensing policy guide.
On Oracle Cloud Infrastructure the units are OCPUs rather than vCPUs. The Bring Your Own License ratio is defined per service, so confirm it in the service description and in the order document rather than assuming it matches AWS.
The standard architect assumption is that middleware licensing follows automatically from the database license, so it needs little separate attention. We disagree. In roughly six out of ten middleware estates Fredrik Filipsson reviewed, WebLogic clusters and SOA composites had grown well past the licensed cores while the database stayed clean, and the unlicensed middleware was the largest single finding. Treating middleware as free infrastructure is the error. The buyer side move is to inventory every WebLogic and SOA node, separate restricted use from full use, and license the components on their own metrics before the database audit pulls the middleware in with it.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Fusion Middleware is not free infrastructure that follows the database. It is a stack of separately licensed products, and WebLogic is where the count quietly runs away.
Use this sequence. It works whether you are 60 days or 270 days from a renewal or an audit.
No. Fusion Middleware is a family name and every product inside it is licensed separately on its own metric. WebLogic Server, SOA Suite, Data Integrator, GoldenGate and Analytics Server each have their own price line, minimums and options.
At list, Standard Edition is $10,000, Enterprise Edition is $25,000 and WebLogic Suite is $45,000 per processor, plus 22 percent a year for support. Named User Plus equivalents are $200, $500 and $900, with a floor of 10 users per processor.
No. Clustering support is an Enterprise Edition capability, and whole server migration and service migration sit there too. A cluster running on Standard Edition entitlements is a compliance gap regardless of whether it works technically.
It is a WebLogic license bundled inside another Oracle product and limited to running that product. Deploying anything else into the same domain, or clustering it where the terms forbid clustering, moves you outside the restriction and requires a full use license on those cores.
WebLogic Server Basic comes with Internet Application Server Standard Edition, Forms and Reports, and BI Standard Edition. It permits basic clustering with load balancing and failover, but forbids whole server migration, service migration, managed server cloning and production redeployment, among others.
Every node in the cluster is licensed on the appropriate edition, including nodes that only take load during a failover. Licensing only the active node is one of the most common middleware findings we see.
Under Oracle's cloud licensing policy for authorized cloud environments, two vCPUs count as one processor license when multi threading is enabled, and one vCPU counts as one processor when it is not. The processor core factor table does not apply, and you license the maximum configured capacity.
Yes. On premises, middleware uses the same processor core factor table as the database, so processor licenses equal physical cores times the factor, rounded up. On current x86 that factor is 0.5.
SOA Suite adapters and packs, identity components such as Access Manager and Internet Directory, Coherence where it was assumed to be included, and active disaster recovery nodes. Each is licensed on its own metric rather than bundled into a stack price.
Inventory every WebLogic and SOA node, classify each domain as full use, restricted use or Basic, count cluster nodes correctly, and separate custom applications out of bundled domains. Then license the remaining gaps before a database audit reaches the middleware tier.
The middleware layer is licensed like the database, per processor with the core factor, but the bundles pull you up to the $120,000 Suite. The edition ladder and how to license to need.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay Oracle for the next three years.
One email a month on Oracle database, middleware, and cloud licensing. Buyer side only.
