
Oracle WebLogic Server Licensing on AWS
Oracle WebLogic Server is fully supported on AWS but requires the Bring Your License (BYOL) model. AWS doesn’t offer managed WebLogic services, so clearly understanding licensing rules for EC2 deployments, containers, and marketplace images is essential.
This guide outlines how to license Oracle WebLogic Server on AWS, including editions, licensing metrics, container scenarios, and middleware products.
Read Oracle on AWS Licensing FAQs 3 of 4.
WebLogic Editions and Licensing Metrics
Oracle WebLogic Server is available in several editions:
- WebLogic Standard Edition
- WebLogic Enterprise Edition
- WebLogic Suite
Each clearly follows Oracle’s standard licensing models:
- Processor Licensing
- Named User Plus (NUP) Licensing
Processor Licensing Calculation (Clearly Explained)
Oracle applies the same two vCPU = 1 Processor license cloud rule on AWS:
- If the AWS EC2 instance has hyper-threading enabled (typical), then:
- 2 AWS vCPUs equal 1 Oracle Processor license for WebLogic.
- No Oracle core factor adjustments apply on AWS for WebLogic (same as Oracle DB).
Practical Example Clearly Explained
- AWS EC2 instance running WebLogic Server with eight vCPUs (hyper-threaded):
- 8 vCPUs รท 2 equals 4 WebLogic Processor licenses required.
- Alternatively, Named User Plus minimums typically are 10 NUP per Processor license:
- 4 processors ร 10 NUP = 40 Named User Plus licenses minimum.
Recommended:
Processor licensing is preferred for larger AWS instances due to NUP minimums.
BYOL WebLogic on EC2 Instances or Docker/Kubernetes Containers
EC2 Instances (Clearly Explained)
- You can install WebLogic Server on AWS EC2 (Windows or Linux).
- You must apply your existing Oracle WebLogic licenses (BYOL).
Docker/Kubernetes Container Licensing (Clearly Explained)
- Oracle currently provides no special container licensing rules.
- Licensing applies to underlying hosts (EC2 nodes), not individual containers or pods.
- License all vCPUs on nodes running WebLogic containers:
- Kubernetes requires Node Affinity rules to limit WebLogic pods to specific licensed nodes.
Practical Kubernetes Example Clearly Explained:
- Kubernetes cluster with clearly 3 EC2 worker nodes (each eight vCPUs):
- You run WebLogic containers pinned (Node Affinity) to 2 nodes only:
- License those two nodes (16 vCPUs รท 2) = 8 Processor licenses total.
- No license is required for the 3rd node (if no WebLogic containers ever run there).
- You run WebLogic containers pinned (Node Affinity) to 2 nodes only:
Important:
There is no sub-capacity licensing for WebLogic on Kubernetes unless Oracle explicitly certifies container partitioning (currently unavailable).
AWS Marketplace Images: BYOL (No Included Licenses)
AWS Marketplace offers Oracle WebLogic AMIs marked as BYOL:
- Simplifies installation and deployment.
- Does not include Oracle licenses.
- You must provide your WebLogic licenses.
Clearly Explained Example:
- Deploying WebLogic Server AMI from AWS Marketplace still requires BYOL licenses.
- No AWS Marketplace AMIs implicitly include WebLogic licenses.
Read Calculating Oracle Licenses for AWS EC2 Instances.
Oracle Middleware Suite Licensing (SOA Suite, Coherence, etc.)
Products clearly including WebLogic Server as components (like Oracle SOA Suite, Coherence, and WebLogic Suite) follow similar licensing rules:
- SOA Suite licensed per processor (same vCPU rule as WebLogic):
- 2 vCPUs = 1 Processor license for SOA Suite.
- Includes the underlying WebLogic Server entitlement.
Practical Example Clearly Explained (SOA Suite):
- AWS EC2 instance eight vCPUs running SOA Suite:
- 8 vCPUs รท 2 = 4 SOA Suite Processor licenses.
- WebLogic Server is includedโno additional WebLogic licenses are needed.
WebLogic Basic (Included Licenses with Oracle DB or EBS)
Some Oracle products (Oracle Database, E-Business Suite) include a limited-use WebLogic Basic license:
- Covers usage strictly for Oracle-provided tools (OEM, Forms, Reports).
- You do not need separate WebLogic licenses if using WebLogic only for DB or EBS purposes specified.
Clear Practical Example:
- Running Oracle Forms and Reports for E-Business Suite uses WebLogic Basic included licenses.
- Custom J2EE applications require full WebLogic licenses separately.
WebLogic Licensing and Operational Monitoring on AWS
- Track WebLogic license usage, especially on clusters.
- WebLogic has MBeans tracking user counts if using Named User Plus (rarely recommended for AWS).
- Fully licenseย all cluster nodesย if nodes are added or scaled manually.
Practical Example Scenario: WebLogic Licensing Calculation Clearly Illustrated
Example Scenario:
- WebLogic Enterprise Edition on AWS EC2 has:
- Two instances, each with 8 vCPUs.
Instance | vCPUs | Licenses Required (Clearly) |
---|---|---|
EC2 Instance 1 | 8 | 4 WebLogic Processor licenses |
EC2 Instance 2 | 8 | 4 WebLogic Processor licenses |
Total licenses | 16 | Clearly 8 Processor licenses total |
Common Misunderstandings Clarified
- Misconception: “AWS Marketplace WebLogic AMIs include Oracle licenses.”
- Clarification: AWS Marketplace provides only installation convenienceโlicenses are always BYOL.
- Misconception: “Containers reduce WebLogic licensing costs.”
- Clarification: There are no special container licensing rules; license full underlying EC2 nodes.
- Misconception: “WebLogic Basic covers custom apps.”
- Clarification:ย The limited-use license is included only for Oracle-provided tools; custom apps require separate licenses.
Read Running Oracle Fusion Middleware Products on AWS.
Summarized Checklist for WebLogic Licensing on AWS
Aspect | Licensing Rule Clearly Explained |
---|---|
Processor Licensing Metric | 2 vCPUs = 1 Processor license |
Container Licensing | BYOL only, no license included |
AWS Marketplace Images | Includes WebLogic Server entitlement |
Middleware Suites (SOA/Coherence) | Covers only Oracle-specified limited use |
WebLogic Basic Included | Clearly covers only Oracle-specified limited use |
Conclusion: Oracle WebLogic Server Licensing on AWS Clearly Explained
Oracle WebLogic Server requires BYOL licensing on AWS, with clear and simple rules aligning with Oracleโs standard cloud licensing policy (2 vCPUs = 1 Processor license). AWS marketplace AMIs simplify deployment but do not include licenses.
Containers require full node licensing, clearly with no special partitioning exceptions. Oracle middleware suites (SOA Suite, Coherence) include WebLogic entitlements, simplifying licensing using bundled middleware products.
Following these guidelines clearly ensures accurate licensing, compliance, and cost optimization when running WebLogic Server on AWS.