Oracle WebLogic licensing — bundled is not the same as free.

How is Oracle WebLogic licensed?

WebLogic Server is licensed per processor — physical cores × Oracle's core factor (0.5 for most x86) — or by Named User Plus for small, countable user populations. It ships in three editions. Standard Edition (~$10,000 per processor) runs a single server with no clustering. Enterprise Edition (~$25,000) adds clustering and high availability. WebLogic Suite (~$45,000) adds the Coherence in-memory data grid and management packs. All carry the standard 22% annual support. The same processor maths that governs the database governs the middleware, which is why our Oracle processor licensing explainer applies here too.

What separates Standard, Enterprise, and Suite?

Capability and clustering. The dividing line that matters at audit is clustering: the moment you run a WebLogic cluster, you need at least Enterprise Edition, and running a cluster on a Standard licence is a classic finding. Suite is bought for Coherence and the management packs, but many estates own Suite and use only Enterprise features — paying nearly double for capability that sits idle. Map the edition you own against the features you actually run before any renewal.

When does bundled WebLogic create a licence liability?

The instant it hosts anything other than the Oracle application it came with. WebLogic is embedded under a restricted-use grant inside E-Business Suite, PeopleSoft, JD Edwards, and most of Fusion Middleware — free to run that application, and only that application. Deploy a custom Java application, a third-party web app, or an internal API gateway onto the same WebLogic domain, and the restriction breaks: you now owe a full-use WebLogic licence by processor for that server. Because middleware is shared infrastructure by instinct, this is one of the easiest boundaries to cross without noticing. A periodic software license compliance assessment surfaces standalone WebLogic use before Oracle's auditors do.

The same discipline applies to the database beneath: the restricted-use Database EE that ships with the application is audited through DBA_FEATURE_USAGE_STATISTICS just as the middleware tier is reviewed for standalone use. The two together are why an applications audit reaches the full stack — see the Oracle Database options guide for the database side.

Processor or Named User Plus for WebLogic?

Processor for anything internet-facing or with an uncountable user population; Named User Plus only for small, internal, fully countable deployments — and even then subject to Oracle's per-processor NUP minimums. The Named User Plus rules count authorised users and multiplexing front-ends as users, so a web tier that fans out to thousands of end users almost always forces the processor metric. Choosing NUP for a public application is a frequent and expensive mis-step.

What does a clean WebLogic position look like?

Three parts. First, an inventory of every WebLogic domain marked bundled-restricted or full-use, with the application each one runs documented — so any standalone deployment is visible before an auditor finds it. Second, an edition reconciliation that matches owned licences to the features actually used, catching both Suite shelfware and Standard-licence clustering. Third, the right metric on each full-use domain, with processor counts derived from the same core-factor maths as the database. Hold those and the middleware tier stops being the quiet liability underneath the applications estate. The cross-cutting playbook is in our Oracle audit defence guide.