Running Oracle Fusion Middleware Products on AWS (BYOL Model)

Running Oracle Fusion Middleware Products on AWS (BYOL Model)

Yes, all Oracle Fusion Middleware (FMW) and Business Intelligence (BI) products—such as SOA Suite, OBIEE, Oracle Analytics Server (OAS), Oracle Identity Management, and WebCenter—can run on AWS using the Bring Your Own License (BYOL) approach.

Oracle software is not restricted by AWS infrastructure, and Oracle’s licensing covers these middleware products under standard cloud licensing rules.

Here’s a practical breakdown of licensing and deployment considerations for each Oracle Fusion Middleware product on AWS.

Read Oracle on AWS Licensing FAQs 3 of 4.

Oracle SOA Suite & Oracle Service Bus on AWS

• Oracle SOA Suite and Oracle Service Bus run on WebLogic Server.
• Licensing follows the same processor licensing as WebLogic:
  • AWS rule: 2 vCPUs = 1 Processor license.
  • SOA Suite licensing includes WebLogic entitlement.

Clear SOA Suite Example:

• AWS EC2 instance has eight vCPUs (hyper-threaded):
  • 8 vCPUs ÷ 2 = 4 SOA Suite Processor licenses are required.
  • WebLogic Server is included, but no extra licenses are required.
• For clusters or multiple nodes:
  • License all nodes individually.

Oracle Business Intelligence (OBIEE / Oracle Analytics Server) on AWS

• OBIEE or a newer Oracle Analytics Server (OAS) can deploy on AWS EC2 instances.
• Licensed by Processor or Named User Plus (NUP):
  • Processor licensing follows the cloud vCPU rule (2 vCPUs = 1 Processor license).
  • Named User is viable if the user count is predictable (minimum typically 10 NUP per Processor).

Practical OBIEE Licensing Example (Clearly Explained):

• Deploy OBIEE/OAS on AWS clearly with an EC2 instance of 8 vCPUs:
  • 8 vCPUs ÷ 2 = 4 Processor licenses.
  • Alternatively, 40 NUP licenses (10 NUP × 4 processors) are required.
• If scaling OBIEE across multiple AWS VMs:
  • License each VM separately by its vCPU count.

Oracle Identity and Access Management (OAM / OID) on AWS

• Oracle Identity & Access Management products (OAM, OID, OIM) run on AWS.
• Licensed clearly by Processor or Named User:
  • The processor license is the same as the vCPU rule (2 vCPUs = 1 Processor).
  • User-based licenses are counted by actual users/employees.

Clearly Explained Licensing Example:

• Running OAM clearly on AWS instance with eight vCPUs:
  • Requires 4 Processor licenses.
  • If licensed per user, count the total internal users managed.

Oracle WebCenter, BPM, and Content Management Products

• Products like Oracle WebCenter, Oracle BPM, and WebCenter Content run on WebLogic and follow similar licensing:
  • The processor is calculated (2 vCPUs = 1 Processor).
  • Named User Plus clearly as an alternative (rarely optimal in larger AWS setups).

Clearly Explained Example (Oracle BPM):

• AWS EC2 instance has eight vCPUs running Oracle BPM Suite:
  • 4 Processor licenses are required.
  • WebLogic is included—no additional WebLogic licenses are needed.

Read Oracle WebLogic Server Licensing on AWS.

Special Considerations: Third-Party External Users

• Note: Oracle middleware licensing for external user access (B2C portals using WebCenter, for example) may require special licenses:
  • Use Processor-based licenses for external-facing applications.
  • Named User licenses are intended for internal users only.

Clear Practical Advice:

• If deploying customer-facing Oracle middleware on AWS, clearly use processor licenses.
• Named User licensing is not typically permitted for external users without special agreements.

Read Licensing Oracle E-Business Suite (EBS) on AWS.

Oracle Middleware and AWS Operating System Support

• Ensure Oracle middleware products run on Oracle-certified operating systems:
  • Amazon Linux, Oracle Linux, Red Hat Enterprise Linux (RHEL), Windows Server.
• Confirm that the chosen OS matches Oracle’s certification for middleware products.

Example Clearly Explained:

• Oracle SOA Suite 12c certified on Linux x86-64:
  • Deploy SOA Suite on Amazon Linux or Oracle Linux EC2 instance for full Oracle support.
  • Avoids support issues with Oracle by adhering to certified environments.

AWS Performance and Instance Sizing for Middleware

• Middleware products memory-intensive; choose EC2 instances accordingly:
  • Licensing is based only on vCPUs, not directly on memory.
• Be careful when choosing large EC2 instances purely for memory; more vCPUs mean increased licensing cost:
  • Bare metal EC2 has many vCPUs—evaluate clearly if smaller instances are more license-efficient.

Practical Licensing Scenario (Clearly Explained):

• Large EC2 instance (bare metal with 32 vCPUs):
  • 16 Processor licenses (32 vCPUs ÷ 2).
  • Alternatively, multiple smaller instances (2×8 vCPUs = 8 licenses) may reduce the total cost.

Practical Licensing Examples: Fusion Middleware on AWS

Licensing Checklist Clearly Summarized: Oracle Middleware on AWS

✅ Middleware Products Clearly Eligible for AWS Deployment (BYOL)
✅ Processor Metric Licensing Clearly Recommended (2 vCPUs = 1 Processor)
✅ Named User Clearly Allowed (Internal Users Only, Minimums Apply)
✅ Certified OS Clearly Required for Oracle Support (Linux, Windows)
✅ External User Access Clearly Requires Processor Licensing
✅ Clearly Monitor Middleware Deployments and Track Licensing Carefully

Common Misunderstandings Clearly Clarified

• Misconception: “AWS middleware deployments require special licenses.”
  • Clarification: Clearly standard Oracle BYOL rules apply—AWS treated like standard cloud environment.
• Misconception: “Middleware named user licenses cover external customers.”
  • Clarification: Named User licensing clearly restricted to internal employees unless explicitly licensed otherwise.
• Misconception: “Containers or Kubernetes reduce middleware licensing costs.”
  • Clarification: Clearly no special container licensing rules; full EC2 node licensing applies.

Conclusion: Oracle Fusion Middleware on AWS Clearly Explained

Oracle Fusion Middleware products—including SOA Suite, OBIEE/OAS, WebCenter, Identity Management, and BPM—clearly run fully supported on AWS using standard BYOL licensing rules. Licensing clearly matches Oracle’s cloud policy (2 vCPUs = 1 Processor license).

Adhere to certified operating systems, choose licensing metrics appropriate for user counts or external-facing apps, and carefully manage vCPU licensing for optimal cost efficiency. Following these guidelines clearly ensures compliant, efficient Oracle middleware deployments on AWS infrastructure.

Do you want to know more about our Oracle Advisory Sevices?

Please enable JavaScript in your browser to complete this form.

Name *

Email *

Company

Message *

Submit