Oracle's middleware scripts count every managed server, partition, and adapter, then read the results in Oracle's favor. Build the evidence pack that splits production from non-production, proves your edition, and caps the claim before Oracle sets the number.
Oracle's middleware scripts count every managed server, partition, and adapter, then read the results in Oracle's favor. Build the evidence pack that splits production from non-production, proves your edition, and caps the claim before Oracle sets the number.
An Oracle SOA Suite or Oracle Integration (OIC) audit is not a licence-key exercise. It is an estate reconstruction, and Oracle intends to run it. The Global Licensing and Advisory Services (GLAS) collection scripts, formerly the LMS Collection Tool, detect which middleware products are installed, how many instances of each are running, which features and modules are enabled inside each instance, and which applications are deployed to each instance. In plain terms: every managed server, every partition, every adapter, and every clustered domain feeds the count. Left uncontested, that raw count becomes the claim.
The defensible position is not to argue with the scripts. It is to arrive with an evidence pack that has already done the interpretation Oracle will not do for you: production versus non-production, primary versus disaster recovery, active partitions versus idle ones, and edition proven by configuration rather than assumed. Over 25 years negotiating middleware claims with this vendor, the single largest lever on the final number is whether the buyer or Oracle controls the interpretation of the collected data. This page walks the estate Oracle examines and specifies the pack that caps exposure. For the metric mechanics underneath, start with the Oracle Integration and SOA licensing buyer guide.
The middleware scripts return a topology, not a licence position. A representative line reads: "Domain ProdDomain: WebLogic Server 12.2.1, 1 admin + 4 managed servers in cluster ProdCluster." Oracle reads that as an Enterprise Edition deployment, because clustering is not available in Basic or Standard. If your purchase records show only WebLogic Standard, that single line is a compliance gap Oracle will price at the delta between editions, multiplied across every processor in scope.
On a SOA estate the collection targets are consistent and they compound. Each of the following contributes to the licensable footprint Oracle asserts:
The critical point is that the script counts everything. It does not distinguish a production cluster from a decommissioned test node that was never uninstalled. It does not know that a partition holds one dormant composite. The buyer-side analysis makes those distinctions, and that analysis is the difference between a claim priced on real usage and one priced on raw discovery output.
The script counts everything. The evidence pack decides what actually counts. Whoever controls that interpretation controls the number.
You need the price list in front of you before you respond to a single Oracle email, because the exposure is not abstract. SOA Suite is one of the most expensive middleware products Oracle sells, and it drags a mandatory WebLogic Suite prerequisite behind it. The table below sets out the list figures our research confirmed. Note that support runs at 22 percent of net licence fee, billed annually and compounding, so every processor over-counted is a recurring liability, not a one-time settlement.
| Component | Processor licence (list) | NUP licence (list) | Notes |
|---|---|---|---|
| SOA Suite for Oracle Middleware | $57,500 | $1,200 | Most commonly cited figure; bundles BPEL, OSB, Business Rules |
| SOA Suite for Non-Oracle Middleware | $75,000 | $1,500 | Higher-priced variant; $16,500 processor support |
| WebLogic Suite (prerequisite) | $45,000 | $900 | Mandatory under SOA Suite; $9,900 processor support |
| Business Activity Monitoring (BAM) | $25,000 | n/a | Separate licence, NOT included in base suite |
| Premier Support | 22% of net licence fee | 22% | Annual, compounding over term |
Put the two mandatory layers together on a modest server. A four-core Intel box (0.5 core factor applied to cores per Oracle's Core Factor Table) at list needs 4 x $57,500 = $230,000 in SOA Suite plus 4 x $45,000 = $180,000 in WebLogic Suite, roughly $410,000 in licences before support. Now imagine the audit script finding four such nodes across production, DR, staging, and a forgotten test cluster. Un-triaged, that is a seven-figure claim built on nodes that may not all require full licensing. The buried WebLogic and database layer is where the real money hides, which is why we treat it as a dedicated workstream in the WebLogic and database buried under your SOA Suite stack analysis.
The suite model is one of the few Oracle mechanics that favours the buyer, and your evidence pack should exploit it. An organisation running BPEL orchestration, OSB routing, and BAM-style monitoring under a single SOA Suite licence gets multiple components for one suite fee. BPEL Process Manager and Business Rules are included with no separate licence. The trap is BAM, which is separate. Document exactly which included components you run, because a well-built inventory converts "three products" into "one licence," reducing the count Oracle can assert. Whether processor or NUP licensing minimises that count depends on your user population and cluster shape; the trade-off is worked through in the SOA Suite processor versus NUP decision.
Two figures you must nail down before conceding any NUP position, because sources conflict and Oracle will quote the one that favours the claim. Some Oracle advisors state a minimum of 10 Named User Plus licences per processor; others, including analysis on this site, state 25 NUP per processor for the middleware stack, the highest minimum in the portfolio. The practical instruction: force Oracle to cite the exact ordering document and price-list clause governing your contract, then hold them to it. Do not accept a verbal minimum. On a four-processor estate, the difference between a 10x and 25x minimum is 60 additional NUP licences per processor of exposure, applied to the entire footprint.
For processor counting, the method is fixed: count physical cores of every server running SOA Suite, apply the Core Factor Table (Intel typically 0.5), and multiply. Your evidence pack must show the core count and factor for each node in writing, because Oracle occasionally applies a factor of 1.0 by default and waits to see whether you challenge it. That challenge is worth exactly half your processor licence bill on Intel hardware.
Adapters are where a contained estate becomes an uncontained claim. Oracle's own documentation is explicit: technology adapters are included in the WebLogic Suite (and Internet Application Server) licence that SOA Suite depends on. Other adapter types are licensed separately. In practice this means the database, JMS, file, and similar technology adapters ride along, but each non-Oracle application adapter (SAP, Siebel, custom-built connectors) adds licensable scope that Oracle will price.
Your evidence pack must enumerate every adapter deployed, classify each as included-technology or separately-licensed application, and cross-reference against entitlements. The failure mode we see repeatedly: an SAP adapter deployed years ago for a pilot that never went live, still present on a managed server, counted by the script, and priced by Oracle at full scope. Remove dormant adapters before the collection runs where your contract permits, or document their inactive status with configuration evidence if removal is not possible in the audit window.
If you have migrated any integration to Oracle Integration 3 (Gen3), the audit surface shifts from processor counting to consumption reconstruction, and the rules live outside your contract. OIC is sold as an OCI service billed per hour across Standard, Enterprise, and Healthcare editions, each provisioned with message packs that scale throughput. A message pack includes 5,000 billing messages per hour, or 20,000 per hour if you brought an existing Fusion Middleware licence to the cloud (BYOL). You can subscribe to up to 100 packs.
The cost floor is unavoidable and worth stating in every OIC negotiation: a single instance at minimum configuration, production shape, Enterprise edition, one message pack, zero DR, costs $30.97 per day at zero usage, which is $11,304 per year before a single record is processed. That is the baseline infrastructure cost, not the usage cost. Edition gating forces the price up further: Enterprise Edition is required to connect to Oracle EBS, JD Edwards, Siebel, and SAP; Standard cannot reach those systems at all.
OIC's message-counting rules live in the service description, not your contract, and Oracle updates them sometimes without notifying you. That is the leverage gap you must close in the renewal.
The volume trap is definitional. Oracle counts a "message" as an integration invocation: one end-to-end flow execution is one message regardless of internal complexity. An EBS-to-Salesforce order sync running 10,000 times per day consumes 300,000 messages per month. The Gen2 to Gen3 migration is where this bites, because Gen3 counts file-based integrations separately from API-based ones, and enterprises have seen monthly bills rise 30 to 80 percent post-migration purely from counting methodology differences. Worse, the methodology is defined in the OIC service description document, not the standard licence agreement, and that document is updated periodically, sometimes without customer notification. Your evidence pack for OIC is a consumption baseline you control, not a bill you accept. Model your message volume before renewal using the message-pack pricing and overage guide, and if you are still mid-migration, cost the whole move with the SOA Suite to OIC migration cost analysis before you commit.
A comprehensive middleware baseline review, assembled before Oracle's data becomes the record, is the single most effective cap on exposure. Build it to the following scope and keep it version-controlled with dated screenshots and configuration exports:
The discipline mirrors what works against every capacity-based vendor. The same evidence-first method that reconstructed IBM sub-capacity positions in the flagship Oracle Java audit defense engagements applies here: you win by arriving with a better dataset than the auditor, interpreted in your favour on defensible grounds, before they anchor the number. If any part of your integration estate runs on public cloud, cross-check the tenancy and BYOL traps in the AWS audit defense analysis, because moving to the cloud moved the licence exposure with you, it did not remove it.
Do not wait for the audit letter to build the pack. The evidence you can assemble on your own timetable is worth far more than the evidence you assemble under a 45-day GLAS response clock. Run your own middleware inventory, tag production versus non-production, prove WebLogic edition by configuration, and remove or document every dormant adapter and idle partition. For OIC, capture your message-volume baseline and the current service description version before your renewal, so uplift and reclassification are negotiated from your data. If you are already in an audit, do not run the collection scripts until you understand what they will surface and how you will interpret it. The order of operations, evidence first, then response, is what caps the claim.
Oracle's GLAS collection scripts detect which middleware products are installed, how many instances run, which features and modules are enabled per instance, and which applications are deployed. On SOA it counts every managed server, partition, and adapter, and infers WebLogic edition from configuration signals such as clustering. It counts everything, including idle partitions and dormant adapters, which is why buyer-side interpretation is essential before the data becomes the record.
Yes. WebLogic Suite is a mandatory prerequisite for SOA Suite. At list it adds $45,000 per processor on top of the $57,500 SOA Suite processor licence, so a four-core Intel node runs roughly $410,000 in combined licences before support. The buried WebLogic and database layer is often the largest single component of a SOA audit claim.
Oracle counts one integration invocation as one message regardless of internal complexity, so a sync running 10,000 times daily consumes 300,000 messages monthly. Gen3 counts file-based integrations separately from API-based ones, and enterprises have seen bills rise 30 to 80 percent after migrating from Gen2 purely from counting methodology changes. The rules live in the service description document, not your contract, and Oracle updates that document periodically.
Sources conflict: some Oracle advisors cite 10 Named User Plus licences per processor, others cite 25 per processor as the highest minimum in the middleware stack. Force Oracle to cite the exact ordering document and price-list clause governing your specific contract and hold them to it. Never accept a verbal minimum, because the difference on a four-processor estate can be 60 additional NUP licences per processor of exposure.
Technology adapters (database, JMS, file) are included in the WebLogic Suite licence that SOA Suite depends on. Non-Oracle application adapters such as SAP, Siebel, and custom connectors are licensed separately and add scope Oracle will price. Enumerate and classify every adapter in your evidence pack, and remove or document dormant ones before the collection runs.
A single OIC instance at minimum configuration on a production shape, Enterprise edition, one message pack, zero DR, costs $30.97 per day at zero usage, which is $11,304 per year in baseline infrastructure before processing any records. Enterprise edition is mandatory to connect to EBS, JD Edwards, Siebel, and SAP, so Standard is not an option for most integration estates.
The strategic framework for Oracle audit defense across LMS, license verification, and contractual response. Beyond the tactical playbook.
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
