SOA Suite is an option on WebLogic, not a product, so a compliant four-core node costs roughly $410,000 in license before the $47,500 per processor database is even counted
Oracle's own Fusion Middleware Licensing Information document states that WebLogic Suite is a prerequisite to license BPEL Process Manager, and that BPEL PM requires a separate Oracle Database license. Most SOA estates were bought as a single line item at $57,500 per processor and never had the two prerequisites purchased underneath. The gap only surfaces in an audit, at list price, with backdated support at 22 percent.
Prepared by Redress Compliance · August 23, 2026 · Oracle middleware advisory. SOA Suite and WebLogic audit defense engagements, 2024 to 2026.
Executive summary
The single largest SOA finding is not SOA at all: it is the WebLogic Suite layer at $45,000 per processor that nobody bought.
SOA Suite for Oracle Middleware at $57,500 per processor is priced as an option on top of a licensed WebLogic Suite estate, and quantity counts must match one to one under both Processor and NUP.
Yet the most common purchase pattern is SOA Suite alone with WebLogic assumed to be included in the media pack.
A second prerequisite, Oracle Database, adds $47,500 per processor for Enterprise Edition and is not a restricted-use grant in SOA Suite.
The SOA infrastructure database holds process state, BPEL dehydration data, business rule definitions, and BAM telemetry, and unlike Oracle Transportation Management, which grants an explicit restricted-use license to Database 19c for installer-created schemas.
The SOA documentation carries no equivalent wording.
The restricted-use grants that do exist inside SOA Suite are narrow, and one custom EAR breaks the whole domain.
Coherence Enterprise Edition, Enterprise Scheduler, Data Integrator for BAM, and OWSM inside OSB are all bundled but ring-fenced to internal SOA use, and deploying a non-bundled application into the same WebLogic domain triggers full-use WebLogic licensing across every core in that environment.
Not only the cores running the extra application.
A fully-loaded compliant SOA node exceeds $240,000 per processor before support, so a four-core deployment carries roughly $410,000 in SOA plus WebLogic alone.
Add the database and 22 percent annual support with typical 8 percent uplift, and a modest two-node integration tier that was budgeted as a $230,000 purchase becomes a seven-figure lifetime obligation the first time Oracle counts it properly.
The published price list contradicts widely circulated advisory figures, and buyers who cite the wrong number lose credibility in the room.
One advisory puts WebLogic Suite at approximately $120,000 per processor on the theory that it bundles WebLogic EE, Coherence Grid Edition, Enterprise Gateway, and Traffic Director, against $45,000 in the current Technology Global Price List effective April 16, 2026.
Always price from the dated price list you can produce, not from secondary sources.
The prerequisite chain: what SOA Suite actually requires underneath it
Oracle's Fusion Middleware Licensing Information document does not describe SOA Suite as a self-contained product.
It describes it as a set of options sitting on top of WebLogic Suite.
And the language is not ambiguous: "A license for Oracle WebLogic Suite is a prerequisite to license Oracle BPEL Process Manager Option," followed immediately by "A license for Oracle BPEL Process Manager Option requires a separate license for Oracle database." That is a three-layer dependency chain written into Oracle's own documentation.
Not an advisory opinion.
In twenty-five years of unpicking these estates, the pattern is monotonous: a project buys SOA Suite for Oracle Middleware at $57,500 per processor as one line on one ordering document.
The WebLogic Suite entitlement underneath is never purchased because the installer quietly deploys a WebLogic domain, and the repository schemas land on an Oracle Database instance somebody assumed came with the middleware.
None of those assumptions survive contact with an audit script. The compliance position is that you owe all three layers, at the same processor count, for the same hardware.
| Component | Metric | List price | Support at 22% | Prerequisite it depends on |
|---|---|---|---|---|
| SOA Suite for Oracle Middleware | Processor (25 NUP per processor minimum) | $57,500 | $12,650 | WebLogic Suite, same counts |
| BPEL Process Manager Option | Processor | $60,000 | $13,200 | WebLogic Suite plus separate Database license |
| WebLogic Suite | Processor | $45,000 | $9,900 | None (the base layer) |
| WebLogic Suite | Named User Plus | $900 | $198 | Counts must equal SOA Suite NUP counts |
| Oracle Database Enterprise Edition | Processor (25 NUP per processor floor) | $47,500 | $10,450 | Repository schemas for SOA, BAM, rules |
| SOA Suite for Non-Oracle Middleware | Processor | $75,000 | $16,500 | Standalone, no WebLogic Suite required |
Read the last two rows against each other, because that is where the only genuine arbitrage in this price list lives.
WebLogic Suite plus SOA Suite for Oracle Middleware is $90,000 per processor against $75,000 for the non-Oracle Middleware SKU, so the bundle is more expensive on paper and cheaper in practice only when you were already going to run WebLogic anyway, which almost every SOA estate is.
If you bought the $75,000 SKU and then deployed onto WebLogic regardless, you paid the standalone premium and still owe the app server.
The quantity-matching rule is the one that generates the largest true-up numbers. Under Processor, WebLogic Suite counts must equal SOA Suite counts; under NUP, the same.
Mismatches are near-universal, and I have seen cases where Oracle Sales itself sold WebLogic Enterprise Edition rather than WebLogic Suite, producing a configuration that was invalid from the day the order was signed.
On a four-core node, the arithmetic is $230,000 of SOA Suite plus $180,000 of WebLogic Suite, roughly $410,000, before the $47,500 per processor database is counted at all. Model the count question before you model the price using the processor versus NUP decision and how clusters change the count.
Restricted use is a whitelist, not a permission: reading the five embedded grants
The restricted-use rights inside SOA Suite are frequently misread by internal architects as "this comes with it, so we can use it." That is exactly backwards.
Oracle drafts these grants as whitelists: a short, closed list of permitted uses, followed by a trigger clause that converts anything outside the list into a full-use liability. The five that matter are narrow to the point of being brittle.
Coherence Enterprise Edition is granted only for clustering, Portable Object Format, and local caching in support of internal SOA usage, which means the moment a developer uses the same Coherence cluster to cache application data for a non-SOA workload, the restricted grant has been exited.
Enterprise Scheduler is limited to scheduling BPEL Process Manager internal jobs and composite services, so batch jobs for a finance application scheduled through the same ESS instance are not covered.
Oracle Data Integrator is restricted to use with BAM only, not to general ETL work, however convenient the installed binaries make it. The UDDI client libraries from HP SOA Systinet in BPEL PM 11g are restricted to connecting to and communicating with the Oracle Service Registry and nothing else.
Oracle Web Services Manager inside Oracle Service Bus covers policy enforcement, with authoring and management confined to the base OSB console screens, so a team that stands up the full OWSM policy manager console has stepped outside the grant.
The clause that gives all five their teeth reads: "Any use of Oracle SOA Suite for Oracle Middleware components not listed above requires a full use license for Oracle SOA Suite for Oracle Middleware." That is a trigger, not a warning.
It converts a technical decision made by an engineer into a per-processor purchase obligation across every core on the machine, at list, with backdated support at 22 percent. There is no partial exit and no proportionality: a single use outside the whitelist prices the whole component.
The contrast that settles the database argument is Oracle's own drafting elsewhere.
In the Transportation Management licensing document, Oracle grants "a restricted use license to Oracle Database 19C solely to host the schema or objects created by the Oracle Transportation Management installer." That is what an intentional embedded database grant looks like: named product.
Named version, named permitted purpose.
No comparable sentence exists for SOA Suite. Oracle demonstrably knows how to write a restricted-use database grant when it means to give one, as it does across several of its application stacks, including the pattern documented in the database and integration licensing hiding under the OTM stack.
The absence of that sentence in the Fusion Middleware document is not an oversight, and it should not be argued as one in a negotiation.
Treat the SOA repository database as a separately licensed prerequisite in every model you build, and price it at $47,500 per processor with the 25 NUP per processor floor applied.
Oracle Fusion Middleware Licensing: WebLogic, SOA & the Suite Trap
Oracle Fusion Middleware is licensed per processor with the core factor. WebLogic editions from $10,000 to $45,000, the SOA Suite drag, Coherence, and how to license middleware to
Get the white paper →Why the domain, not the application, is the unit of exposure
The single most expensive sentence in Oracle's Fusion Middleware Licensing Information document is not a price.
It is the scoping language: "Any use of Oracle SOA Suite for Oracle Middleware components not listed above requires a full use license for Oracle SOA Suite for Oracle Middleware." Read that carefully and notice what it does not say.
It does not say "any use by the offending application." It does not say "the cores serving that workload." Oracle wrote the restriction around the runtime container, and in practice the container is the WebLogic domain. That choice is not accidental drafting.
It is the mechanism by which a technically trivial deployment decision becomes a license event priced at $57,500 per processor for SOA Suite plus $45,000 per processor for the WebLogic Suite entitlement underneath it.
Consider how this plays out. SOA Suite, Oracle Service Bus, and BPM each ship with a WebLogic runtime that is restricted, not free. The restriction governs what runs inside that runtime.
The moment an engineer deploys a custom EAR or WAR alongside the bundled Oracle application, whether it is a Spring service, an internal admin console, or a reporting servlet someone wrote to expose composite state to a dashboard, the restricted grant is broken. Not partially. Not proportionally.
The domain now hosts a workload the grant never covered, and the WebLogic underneath it is retroactively full-use. Oracle does not then ask which cores served the extra WAR. It counts every core in that environment.
That asymmetry is where the audit revenue lives. The trigger is invisible to the person who pulls it. No warning fires at deployment. No license manager blocks the operation. WebLogic will happily start the application, and it will run correctly for four years.
The breach is discoverable only by domain inspection, meaning someone reads the deployment list against the entitlement, which is exactly what Oracle's collection scripts do and exactly what almost no internal ITAM process does.
By the time it surfaces, the finding is priced at current list with backdated support at 22 percent, and the customer has no technical defense because the technical facts are not in dispute. Only the interpretation is, and the interpretation was drafted by Oracle.
The strategic consequence is uncomfortable, because it puts license safety in direct opposition to infrastructure discipline. Every consolidation instinct a competent platform team has, fewer domains, higher density, shared runtimes, better cost per core, pushes more workloads into fewer containers.
Under a per-core metric that is the correct engineering answer. Under a domain-scoped restricted grant it is the maximally expensive one. A team that consolidates six sparse domains into two dense ones has just multiplied the blast radius of any single non-compliant deployment by three.
The same logic applies to how you count processors versus named users across a cluster, where consolidation changes the arithmetic in ways procurement rarely models.
Active GridLink is the cleanest illustration of the design. The feature is present in the binary across Standard Edition, Enterprise Edition, and Suite. Nothing in the product prevents an administrator from configuring an Active GridLink data source in an EE domain.
The entitlement, however, exists only at Suite. So a routine RAC connectivity improvement, made by a DBA optimizing failover behavior, silently converts an EE-licensed estate into one that requires Suite.
The delta per processor is real money, and it was created by a configuration change nobody logged as procurement-relevant.
The defensive posture that actually works is architectural, not contractual. Arguing about scope after the collection script has run is a losing position, because the facts are logged in config.xml and the contract language favors Oracle.
What works is segregation: bundled Oracle workloads in domains that contain nothing else, custom code in separately licensed full-use domains, and a change-control gate that treats "deploy anything to a SOA domain" as a licensing decision rather than an operational one.
That gate costs some efficiency. It costs far less than the retroactive Suite uplift across an entire environment.
The features that are switched on but not licensed
None of the findings below require anyone to have done anything deliberate. Every one of these features is compiled into the binaries you already downloaded, exposed through the standard console, and functional without a key, a flag, or a support request.
The entitlement boundary exists only in the licensing document.
Oracle's LMS collection scripts and the review tooling for WebLogic parse the domain configuration, the deployment inventory, and the MBean state to establish which of these are in use, and the evidence is unambiguous once collected because the configuration files are the evidence.
In our experience across SOA audit defense engagements, these five account for the large majority of middleware findings that were not caused by a missing prerequisite purchase.
| Feature | What is technically enabled | What the grant actually permits | Typical remediation exposure |
|---|---|---|---|
| Active GridLink data sources | Configurable in SE, EE, and Suite binaries via the standard admin console | Entitled only at WebLogic Suite | Uplift from WebLogic EE to WebLogic Suite at $45,000 per processor list, across every core in the domain |
| Coherence | Full Enterprise Edition cache functionality in the runtime | Clustering, POF, local caching, internal SOA usage only | Coherence Grid Edition at $25,000 per processor where used as a general application cache |
| Oracle Data Integrator | Full ODI installed and usable alongside BAM | Restricted to use with BAM only | Full ODI licensing where ODI moves any non-BAM data |
| Enterprise Scheduler (ESS) | Any job type schedulable through the console | BPEL PM internal jobs and composite services only | Full-use SOA Suite trigger at $57,500 per processor |
| OWSM inside Service Bus | Full policy authoring and management tooling | Policy enforcement in OSB, authoring limited to base OSB console screens | Full OWSM entitlement plus the WebLogic Suite prerequisite beneath it |
The compounding case, and the one that produces the largest single numbers, is the WebLogic edition mismatch. Oracle's own rules require WebLogic Suite quantities to match SOA Suite or BPEL PM quantities under both Processor and NUP metrics.
Yet Oracle Sales has, on documented occasions, sold WebLogic Enterprise Edition alongside SOA Suite, producing a configuration that is invalid on Oracle's own paperwork from the day the order form was signed.
If that is your estate, the shortfall is not a compliance failure you created, it is a mis-sold order form, and that distinction is genuine negotiation leverage.
Pull the original ordering documents before you concede anything, and read them against the prerequisite chain described in our Oracle integration and SOA licensing buyer guide. A vendor error in the sale is one of the few facts that meaningfully shifts the price of the remedy.
What the price list says versus what advisories repeat
There are two WebLogic Suite numbers circulating and you need to know which one you are holding before you sit down.
The Oracle Technology Global Price List effective April 16, 2026 carries WebLogic Suite at $45,000 per Processor (support $9,900) and $900 per NUP (support $198), against SOA Suite for Oracle Middleware at $57,500 per Processor.
SOA Suite for Non-Oracle Middleware at $75,000 per Processor ($1,500 NUP), BPEL Process Manager Option at $60,000 per Processor, and Coherence Grid Edition at $25,000 per Processor.
One widely circulated advisory instead quotes WebLogic Suite at approximately $120,000 per Processor, reasoning that Suite bundles WebLogic Server Enterprise Edition, Coherence Grid Edition, Enterprise Gateway, and Traffic Director, so the price should reflect the sum of the parts.
That reasoning describes the content of the bundle correctly and the price incorrectly. The published list price is the price.
This matters commercially, not academically.
If you open a remediation negotiation with a $120,000 figure, you have anchored Oracle's own exposure math nearly three times higher than the LMS spreadsheet will, and you have handed the account team a free credibility win the moment they produce the PDF.
In practice, in our audit-defense work, the side that produces the dated price list controls the arithmetic for the rest of the conversation. Download the Technology Global Price List, note the effective date on its face, and price every processor and NUP line from that single document.
Where your SOA Suite metric choice between Processor and Named User Plus is still open, run both against the same dated sheet, remembering the 25 NUP per Processor floor. Never price from an advisory blog, including ours, when the vendor publishes the number.
Evidence base: the findings that repeat across SOA audits
4 Processors of SOA Suite at $57,500 plus 4 of WebLogic Suite at $45,000, before the $47,500 per Processor Database EE line.
Every unlicensed prerequisite carries support at 22 percent of net license fee, applied retroactively to first deployment in most audit findings.
Across Oracle Fusion Middleware Licensing Information, the April 2026 price list, and SOA audit defense engagements from 2024 to 2026, five findings recur with enough consistency to be treated as the default assumption about any SOA estate you have not personally inventoried.
First, SOA Suite processor or NUP counts that do not match WebLogic Suite counts underneath, because the prerequisite was never a line item on the original order.
Second, no Oracle Database license anywhere for the SOA infrastructure repository holding process state, BPEL execution data, business rule definitions, and BAM telemetry.
Third, custom applications co-resident in a domain that also runs SOA composites, which converts a restricted grant into a full-use trigger.
Fourth, Standard Edition 2 used for the repository, which is functionally unsuitable for production SOA and fails on the technical argument before the licensing one.
Fifth, and this is the leverage point, Oracle Sales having sold WebLogic Server Enterprise Edition instead of WebLogic Suite, producing a configuration that was invalid on the day it was quoted.
The fifth pattern is the one the table cannot show, and it is worth more to you than the first four combined. When the wrong SKU came from Oracle's own quote, the compliance gap is a vendor error with a documentary trail, not a customer control failure.
That reframes the entire remediation from penalty pricing to correction pricing, and it is the single strongest basis for waiving backdated support.
Evidence caps exposure and nothing else does.
Collect domain deployment inventories showing which applications sit in which WebLogic domain, Oracle Diagnostic Assistant output, dated ordering documents and the original quotes behind them, and installer logs establishing when each component was first deployed.
The same discipline applies across the broader Oracle integration and SOA licensing estate. Without dated artifacts, Oracle prices from first install date at list.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
Your first five moves
- Inventory every WebLogic domain within 30 days, owned by the middleware architect, flagging every domain where SOA Suite, Service Bus, or BAM binaries sit alongside a custom application, because that co-tenancy is what converts a restricted-use grant into a full-use claim.
- Reconcile SOA Suite quantities against WebLogic Suite quantities line by line on the ordering documents, not on the invoice summary, since Oracle's own Fusion Middleware Licensing Information makes WebLogic Suite a prerequisite and we have repeatedly seen Oracle Sales deliver WebLogic Enterprise Edition instead, leaving an invalid configuration the customer paid for.
- Confirm a full Database entitlement for every repository schema, owned by the DBA lead, and stop assuming a restricted-use grant exists: SOA Suite has no wording equivalent to the Transportation Management grant of "a restricted use license to Oracle Database 19C solely to host the schema or objects created by the installer," so the SOA infrastructure database is a separate $47,500 per processor Enterprise Edition purchase.
- Segregate custom applications into separately licensed domains or dedicated hosts before any audit notice arrives, because remediation done under a Section 4 review letter is priced as a backdated settlement with 22 percent support arrears, while the same architectural change done in a quiet quarter costs only the migration effort.
- Price every remediation option from the dated Technology Price List you can cite, comparing the bundled path at roughly $102,500 per processor (SOA Suite at $57,500 plus WebLogic Suite at $45,000) against SOA Suite for Non-Oracle Middleware at $75,000, and take the gap to Oracle as a forward-looking purchase decision rather than an admission, using the processor versus Named User Plus counting analysis to test whether the metric itself should change.
The sequence matters more than the individual steps. Every move above is cheap and reversible until Oracle sends an audit notice, at which point the same facts become discovery material and the same purchase becomes a settlement.
In 25 years of these negotiations, the single largest variable in the final number has not been the size of the gap, it has been whether the customer found it first.
Note also that a compliant four-core node runs roughly $410,000 in middleware license alone before the database, so consolidation onto fewer, cleanly partitioned hosts is usually a larger saving than any discount you will negotiate. Fix the topology, then talk price.
Frequently asked questions
Does Oracle SOA Suite include a free WebLogic license?
No. SOA Suite ships with a restricted-use WebLogic runtime that permits only the bundled Oracle application to run in that domain.
Oracle's Fusion Middleware Licensing Information states that a license for WebLogic Suite is a prerequisite to license the BPEL Process Manager Option, and WebLogic Suite lists at $45,000 per processor.
Deploying any custom EAR or WAR into that domain requires a full-use WebLogic license for every core in the environment.
Do I need a separate Oracle Database license for the SOA repository?
Yes. Oracle's documentation states that a license for the BPEL Process Manager Option requires a separate license for Oracle Database, and there is no restricted-use database grant in the SOA Suite licensing chapter.
Compare that with Oracle Transportation Management, where Oracle explicitly grants a restricted-use license to Database 19c solely to host installer-created schemas.
Enterprise Edition lists at $47,500 per processor, and Standard Edition is generally unsuitable for production SOA due to functional limitations.
What exactly is restricted-use inside SOA Suite?
Five grants matter: Coherence Enterprise Edition limited to clustering, Portable Object Format, and local caching for internal SOA use; Enterprise Scheduler limited to BPEL PM internal jobs and composite services; Oracle Data Integrator restricted to use with BAM.
UDDI client libraries restricted to communicating with Oracle Service Registry; and OWSM inside OSB limited to policy enforcement through base console screens.
Oracle's catch-all clause states that any use of components not listed requires a full use license for SOA Suite for Oracle Middleware.
How much does a compliant SOA Suite node actually cost?
A fully-loaded per-processor stack of SOA Suite, WebLogic Suite, and Oracle Database typically exceeds $240,000 before support.
On a four-processor node, SOA Suite at $57,500 gives $230,000 and WebLogic Suite at $45,000 gives $180,000, totaling roughly $410,000, plus 22 percent annual support and the database layer on top. Budget the prerequisites at architecture stage, not at audit.
Is WebLogic Suite $45,000 or $120,000 per processor?
The Oracle Technology Global Price List effective April 16, 2026 lists WebLogic Suite at $45,000 per processor with support at 22 percent of net.
One advisory circulates approximately $120,000 per processor on the basis that Suite bundles WebLogic EE plus Coherence Grid Edition, Enterprise Gateway, and Traffic Director.
Price from the dated price list you can produce in the room; using an inflated secondary figure damages your credibility with Oracle's LMS and sales teams.
Why does one custom application trigger licensing for the whole environment?
Because the restricted-use grant is scoped to the WebLogic domain, not to the individual application.
The moment a non-bundled application is deployed to the same managed server, full-use WebLogic licensing is triggered for every core in that environment, not just the cores running the additional application.
Most middleware audits include deep inspection of WebLogic domains specifically to find non-bundled deployments.
Do SOA Suite and WebLogic Suite quantities have to match?
Yes. Under Named User Plus, WebLogic Suite counts must match SOA Suite and BPEL Process Manager counts, and the same one-to-one rule applies under the Processor metric.
Mismatches are one of the most common audit findings, and in some engagements Oracle Sales itself sold WebLogic Enterprise Edition instead of WebLogic Suite, producing a configuration that is invalid on Oracle's own paperwork.
Reconcile ordering documents line by line before any audit notice arrives.
