On AWS, Azure and Google Cloud the Processor Core Factor Table does not apply, so the same physical cores can need twice the WebLogic licenses. The counting rules, the OCI marketplace images, and the restricted use trap.
Oracle counts WebLogic differently in the cloud than it does in your data center, and the difference is not a discount. On AWS, Azure and Google Cloud the Processor Core Factor Table does not apply, so the same physical capacity can need twice the licenses it needed on premises.
This is the broad guide to WebLogic in every cloud. If your target is Amazon specifically, the WebLogic licensing on AWS guide goes deeper on EC2 instance families, autoscaling groups and Optimize CPUs. Read this one first, then that one.
For the support stage question that runs alongside the migration, see the WebLogic support tiers guide. The counting logic here mirrors the database, which the Oracle Database licensing guide covers in full.
You license the edition, on the metric, for the counted processors. The cloud changes only the third of those, but it changes it enough to break a business case built on data center arithmetic.
WebLogic Server Standard Edition does not permit clustering. Enterprise Edition does, and adds dynamic clusters, failover, whole server migration and Java SE Advanced. WebLogic Suite adds Coherence Enterprise Edition, Active GridLink for Real Application Clusters and iAS Enterprise Edition on top of Enterprise Edition.
That boundary matters more in the cloud than on premises, because cloud reference architectures default to clustered, multiple availability domain designs. An architect who draws a resilient design has also chosen an edition, usually without knowing it.
Processor is the default metric for anything reachable by an unbounded user population. Named User Plus is priced at $200, $500 and $900 for the three editions, with a floor of 10 Named User Plus per processor.
The floor is the part that catches cloud estates. Because the cloud counting rule inflates the processor number, it also inflates the Named User Plus minimum, so a metric that looked cheap on premises can be the more expensive of the two after migration.
Oracle counts vCPUs and ignores the core factor. The rule sits in Oracle's Licensing Oracle Software in the Cloud Computing Environment policy, which names Amazon Web Services, Microsoft Azure and Google Cloud as the Authorized Cloud Environments.
Where hyperthreading is enabled on the instance, two vCPUs count as one Oracle Processor license. Where it is not enabled, one vCPU counts as one Processor license. The count is taken per instance and summed across the estate.
On premises you multiply physical cores by the factor in the Processor Core Factor Table, which is 0.5 for most x86 cores. In an Authorized Cloud Environment that table is expressly not applicable.
Work the same hardware through both rules. A 16 core x86 server on premises is 8 Processor licenses. The same 16 cores presented as 32 vCPUs in the cloud is 16 Processor licenses. Identical compute, double the license.
Same 16 physical x86 cores, four counting regimes, WebLogic Enterprise Edition at list
| Where it runs | Counting unit | Core factor applies? | Processor licenses | License at list |
|---|---|---|---|---|
| Own data center, x86 | Physical cores | Yes, 0.5 | 8 | $200,000 |
| AWS EC2, hyperthreading on | vCPU | No | 16 | $400,000 |
| Microsoft Azure, hyperthreading on | vCPU | No | 16 | $400,000 |
| Google Cloud, hyperthreading on | vCPU | No | 16 | $400,000 |
| Oracle Cloud Infrastructure | OCPU | No, but an OCPU is a full core | 8 | $200,000 |
That last row is the reason Oracle sales teams open every middleware migration conversation with OCI. The counting unit, not the compute, is the commercial argument.
The policy names AWS, Azure and Google Cloud. Everything else, including VMware Cloud on AWS, private hosting providers and any sovereign or partner cloud, falls outside it and is treated as ordinary third party hosting under your existing agreement.
Outside the policy the core factor comes back, but so does the partitioning position, which usually means licensing the whole underlying cluster. Getting a written confirmation of the counting basis for a non listed provider is not optional.
Oracle's cloud licensing document is published policy. It is not incorporated into the Oracle Master Agreement, it carries no commitment to remain in force, and Oracle has revised it before, including when Google Cloud was added.
The practical response is to put the counting basis into the ordering document for any material cloud deployment. A sentence naming the conversion you relied on converts a policy you cannot enforce into a term you can.
They include the WebLogic binaries, the domain provisioning automation and the surrounding OCI plumbing, and they include no license at all if you pick the bring your own license variant. Oracle documents the stack in Using Oracle WebLogic Server for OCI.
Two commercial models sit behind the same marketplace listing. Under bring your own license you are billed for compute only and you supply the WebLogic entitlement. Under Universal Credits the WebLogic Enterprise Edition or Suite license is metered per OCPU hour alongside the compute.
One asymmetry is worth knowing before you plan. WebLogic Server Standard Edition is available only as bring your own license, so there is no license included route to the cheapest edition. If the workload is genuinely single instance, the saving only exists if you already own Standard Edition.
A restricted use WebLogic license may run only the Oracle product it was bundled with, and moving that product to a cloud does not widen the grant by a single application. The restriction travels with the software, not with the infrastructure.
Several Oracle products ship with a WebLogic entitlement scoped to themselves. Oracle applications, Fusion Middleware components and various Oracle appliances all do it, which is why so many estates hold WebLogic they never bought.
The cloud makes all three easier and all three more visible. Instance counts and images are logged, tagged and billable, so the evidence trail that proves the breach is the same evidence trail your finance team built for cost allocation.
WebLogic includes a restricted Java SE entitlement scoped to running WebLogic itself. Using that Java runtime for anything else, including other applications on the same instance, falls outside the grant and lands in the Java subscription conversation instead.
White Paper · Oracle Middleware
Oracle Fusion Middleware Licensing
WebLogic, SOA and Coherence, priced. Read it free.
They overspend on shape, on edition, and on environments nobody counted. In that order, and by a wide margin on the first.
The common advice is to move WebLogic to Oracle Cloud Infrastructure because the counting is more favorable there, and the OCPU arithmetic in the table above appears to prove it. We disagree, and not because the arithmetic is wrong. The arithmetic is right and it is also the smallest term in the equation. In the estates we reviewed, right sizing the instance shapes and correcting the edition delivered a larger reduction than the counting difference between OCI and AWS, and those actions are portable to any cloud. Choosing a cloud to fix a licensing problem hands Oracle your exit leverage for the next renewal in exchange for a saving you could have had anyway. Fix the shape and the edition first, then choose the destination on merit, and if OCI still wins, negotiate knowing the alternative was viable.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The cloud question is not which provider is cheapest. It is how many processors your architecture will be counted at, and whether you agreed that count in writing before you moved.
Build the license line into the migration model at shape level, not at estate level. One table with an instance per row and a Processor count per row will change the architecture faster than any policy summary.
Take an estate of twelve WebLogic domains on Enterprise Edition, running on 96 physical x86 cores across production, test and a standby site. On premises that is 48 Processor licenses.
Lift the same design to an authorized cloud on hyperthreaded shapes and it presents as 192 vCPUs, which counts as 96 Processor licenses. Nothing about the applications changed. The license position doubled and the support line doubled with it.
Twelve domains, three routes, WebLogic Enterprise Edition at list
| Route | Counted processors | License at list | Support per year at 22 percent |
|---|---|---|---|
| Stay on premises, unchanged | 48 | $1,200,000 | $264,000 |
| Lift and shift to an authorized cloud | 96 | $2,400,000 | $528,000 |
| Right size shapes by one third, then move | 64 | $1,600,000 | $352,000 |
The third row is the one to put in front of the migration board. Right sizing is engineering work you control, and it recovers most of what the counting rule takes away.
If the migration paper cannot answer those three, it is a compute plan rather than a business case. Send it back.
The sequence below runs a WebLogic cloud position before the migration board signs the business case, not after.
We map feature use to edition, separate restricted use from full use, and convert the target architecture to a counted processor position before the migration is committed. We do not resell Oracle and we do not implement it.
Oracle WebLogic advisory runs inside the Vendor Shield subscription, the Renewal Program and the Benchmark Program, led on the buyer side by a former Oracle licensing executive.
For the wider picture, see the Oracle services page, the Oracle knowledge hub and the benchmarking page. If you want a position reviewed before a board date, use the contact page.
WebLogic is licensed by edition on the Processor or Named User Plus metric, and in an Authorized Cloud Environment the processor count is derived from vCPUs rather than physical cores. Two vCPUs equal one Processor license where hyperthreading is enabled, and one vCPU equals one Processor license where it is not.
No. Oracle's cloud licensing policy states that the Processor Core Factor Table is not applicable to Authorized Cloud Environments. That is why a 16 core x86 server needing 8 Processor licenses on premises needs 16 in the cloud once it is presented as 32 vCPUs.
Amazon Web Services, Microsoft Azure and Google Cloud. Oracle Cloud Infrastructure is Oracle's own cloud and is governed by its service descriptions instead. Any other provider, including VMware based services and private hosting, sits outside the policy and is treated as ordinary third party hosting.
On the counting rule alone, yes, because OCI counts OCPUs and one OCPU is a full physical core rather than a hyperthread. For the same 16 physical cores that is 8 Processor licenses on OCI against 16 on an Authorized Cloud Environment. Whether the total cost follows depends on shape, edition and the commercial terms you negotiate.
It depends on the listing. The Universal Credits variants meter the WebLogic Enterprise Edition or Suite license per OCPU hour alongside compute, while the bring your own license variants bill compute only and require you to own the entitlement. WebLogic Server Standard Edition is offered as bring your own license only.
No. Clustering, failover and whole server migration are Enterprise Edition features. Suite adds Coherence Enterprise Edition, Active GridLink for Real Application Clusters and iAS Enterprise Edition, so it is only worth the $20,000 per processor premium if those components actually run.
Yes. Oracle provides no free development or test entitlement for WebLogic, so every running non production instance counts on the same metric as production. A warm standby with WebLogic installed and started counts too, which is why disaster recovery designs need pricing before they are approved.
No. A restricted use WebLogic entitlement may run only the Oracle product it was bundled with, and moving that product to a cloud does not widen the grant. Deploying a second application into the same domain, or reusing the build as a golden image, requires full use WebLogic licenses for the affected processors.
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.
Independent. Buyer side. Built for Oracle customers running the next renewal cycle.
Open the white paper in your browser. Corporate email only.
Open the Paper →
Renewal in twelve months. Audit notice in the inbox. RFP on the desk. We start where you are.
WebLogic edition benchmarks, restricted use rules, the embedded Java right, cloud conversion math, and middleware intelligence from every Oracle engagement we run on the buyer side.
