Oracle middleware reads through WebLogic Server: a tier choice between Standard, Enterprise and Suite, a Java SE relationship under the same chassis, and a panorama of additional options that layer onto the tier. The Admodum read on the metric, the minima, the layering and the audit posture.
WebLogic Server is the Java EE / Jakarta EE application server at the centre of the Oracle middleware portfolio. It is the runtime container for Java enterprise applications: servlets, EJBs, JMS, JTA, JPA, web services and the modern Jakarta EE equivalents. It is also the runtime for many Oracle Fusion Middleware products (SOA Suite, Identity Management, BPM).
The wider Fusion Middleware family includes Oracle SOA Suite, Oracle BPM Suite, Oracle Service Bus, Oracle Identity Governance, Oracle Access Manager, Oracle Forms and Reports, Oracle GoldenGate and Oracle Data Integrator. Each is separately licensed; many require WebLogic underneath as the runtime container.
The wider editorial sits in the Oracle pillar; the related Java relationship sits at Java SE Universal Subscription.
WebLogic Server ships in three tiers. WebLogic Server Standard Edition is the entry tier: the core Java EE / Jakarta EE runtime, no clustering, no transactional services beyond the single-server transaction manager. WebLogic Server Enterprise Edition adds clustering, distributed transactions, advanced security and the Oracle Coherence integration. WebLogic Server Suite adds the full Oracle Coherence Enterprise Edition, the Java SE Subscription rights for the WebLogic JVM, and the management packs.
The tier choice is the first commercial decision. The buyer-side discipline is to characterise the workload (single-server, clustered, distributed transactional, in-memory grid) and to size the tier against that characterisation, rather than to default to the highest tier for ease.
The pricing arithmetic between tiers is material: WebLogic Server Suite is typically two to three times the per-Processor price of WebLogic Server Standard Edition.
WebLogic Server is licensed against either the Processor metric or the Named User Plus metric. Processor reads against the processor metric and the core factor table. NUP reads against the Named User Plus metric with the published per-processor minima: ten NUP per Processor for WebLogic Server Standard, Enterprise and Suite.
The ten-NUP-per-processor minimum is materially lower than the Database EE twenty-five-NUP-per-processor floor. NUP therefore reads as a more attractive metric for development, test and small production WebLogic deployments than it does for Database EE.
The buyer-side discipline is to run the NUP arithmetic against the deployed processor count first, before assuming Processor licensing is the only commercial path.
WebLogic Server Suite includes the right to run Java SE on the WebLogic Server JVM, under a bundled-use entitlement. The bundled-use entitlement does not extend to other Java SE deployments on the same host (a separate Java SE application running outside the WebLogic Server JVM still requires its own Java SE licence).
Standalone Java SE is the separate Java SE Universal Subscription, sold per employee since the January 2023 pricing reset. The wider migration read sits at Java SE migration.
The buyer-side discipline is to enumerate every Java SE deployment in the estate against the licensed entitlement, and to keep the WebLogic-bundled Java SE installations clearly distinguished from standalone Java SE installations.
WebLogic Server layers additional options at each tier. WebLogic Server Enterprise Edition layers Coherence integration (against a separately-licensed Coherence position for the in-memory grid). WebLogic Server Suite includes the WebLogic Diagnostic Framework and the Java Management Service.
Adjacent middleware components (Oracle SOA Suite, Oracle Service Bus, Oracle Identity Management, Oracle Access Manager, Oracle Data Integrator, Oracle GoldenGate) each carry their own licence on top of the WebLogic foundation. The deployment is a stack: WebLogic underneath, the middleware component above, and (in many configurations) integration into the Database EE position via JDBC and JMS.
The wider option panorama (Database EE options, not WebLogic options) sits at database options and management packs; the audit-side read on activated middleware features sits at the LMS audit anatomy.
The audit-quality inventory for WebLogic Server reads four things: the deployed tier (Standard, Enterprise, Suite), the host core count and chip family (against the core-factor table), the activated options (Coherence, the diagnostic framework, the management packs) and the wider middleware stack on top (SOA Suite, Service Bus, Identity Management, etc.).
The audit-quality discipline is to hold a current inventory of all four readings, to reconcile each against the Schedule A entitlement, and to surface any drift before the next audit moment. The deeper read on the Schedule A reconciliation sits at Schedule A, anatomised.
The wider engagement sits in the Oracle practice; the aggregated reading list sits in the Oracle knowledge hub; active audit moments route to Audit Defence; active renewal moments route to renewal programme.
The standalone Java SE position under the per-employee model.
The wider Database EE option panorama that layers under middleware.
The metric with the ten-NUP-per-Processor minimum for WebLogic.
A senior Admodum Oracle advisor will read the WebLogic tier, the activated options and the wider middleware stack on a private call. Active audit moments route to Audit Defence; active renewal moments route to the Renewal Programme.