Oracle WebLogic Server runs on Java — but owning WebLogic does not licence Java everywhere. An independent guide to where the two licences meet.
Oracle WebLogic Server is Oracle's Java EE and Jakarta EE application server, and it cannot run without a Java SE runtime underneath it. To make that workable, a licensed WebLogic deployment carries the right to use the Java SE it needs to run WebLogic itself. In other words, WebLogic is one of the Oracle products that ships with restricted-use Java SE rights.
That right is genuine and useful: if a server is properly licensed for WebLogic, you do not also need a separate Java SE subscription for the JDK that powers that WebLogic instance. But the right is bounded by WebLogic. It does not stretch to the rest of the machine, to other applications on the same host, or to Java used anywhere else.
It helps to think of a WebLogic host as carrying two distinct licences that happen to overlap: the WebLogic Server licence (processor or, in some cases, named-user plus metrics) and the Java SE position. Where Java is used solely to run WebLogic, the WebLogic licence covers it. Where Java is used for anything else, Java SE licensing — today the Universal Subscription — applies independently.
Oracle's Java application server
Restricted to running WebLogic
Standalone apps, other JVMs on the host
Processor or named-user plus
Java SE Universal Subscription
Shared JDK across non-WebLogic apps
The friction point is almost always the shared host. WebLogic servers are rarely dedicated; they also run scripts, agents, monitoring tools, batch processes, and sometimes standalone Java applications. Every one of those that uses the Oracle JDK — even the JDK installed for WebLogic — sits outside the WebLogic restricted-use right and needs its own Java SE entitlement.
Another collision is the JDK download itself. Administrators often patch or replace the Oracle JDK on a WebLogic host from Oracle's general site. The restricted-use right travels with the Java that supports WebLogic in a supported configuration; substituting a separately downloaded Oracle JDK can change the licence that applies. OpenJDK builds, where supported for the WebLogic version in question, avoid the question entirely.
As with every restricted-use product, owning WebLogic is not a Java SE site licence. Developer laptops, build agents, other application servers, and desktop Java across the organisation are licensed separately. Treating a WebLogic entitlement as estate-wide Java cover is one of the most common findings in an Oracle Java audit.
Sharing the WebLogic JDK with non-WebLogic processes takes that use outside the restricted-use grant.
WebLogic covers Java for WebLogic. It does not licence Java on developer or application machines elsewhere.
Replacing the runtime with a separately obtained Oracle JDK can change which licence applies on a WebLogic host.
We map which Java on each WebLogic host is covered and which needs a separate licence.
DefendWebLogic hosts are a frequent audit focus. We defend the claim, with a money-back guarantee.
MigrateWhere supported, we move non-WebLogic Java workloads to free OpenJDK builds.
If we take on your Oracle Java audit and cannot reduce the claim, we refund our fees. See how the guarantee works →
We draw the exact line between WebLogic-covered Java and Java that needs its own subscription.
Weekly Oracle Java updates, audit alerts, and negotiation intel.