News, tips and technical guidance to help you run Oracle E-Business Suite on Oracle Cloud.
-
E-Business Suite and Oracle Cloud,
General Information and Resources
November 3, 2016
Licensing EBS on Oracle Cloud
[Guest Authors: Terri Noyes and Robert Farrington]
This article describes how you license Oracle E-Business Suite to run in Oracle Cloud. The licensing terms depend on your deployment choice, so let's start by revisiting EBS Deployment Options on Oracle Cloud.
Deployment Options
Running Oracle E-Business Suite on Oracle Cloud requires, at minimum, a subscription to the Oracle Compute Cloud Service (Compute), part of Oracle's Infrastructure as a Service (IaaS), to provide the resources you need. You can then choose to run EBS on a single node (left-hand figure below) or multiple nodes (middle figure below). In these two scenarios, your application and database tiers both run on IaaS.
An alternative is to run your EBS database on Oracle's Database Cloud Service (DBCS) or Oracle Database Exadata Cloud Service (Exadata CS), by subscribing to whichever of these best meets your needs. This is shown in the right-hand figure below.
|
Single node on Compute |
Multiple nodes on Compute |
Multiple nodes on Compute + Database Cloud Service (DBCS or Exadata CS) |
|
|
|
Licensing Models
Oracle E-Business Suite is licensed by user per product or module, and EBS licenses are required for production use only (whether in the cloud or on-premises). Oracle E-Business Suite comes with restricted-use Database Enterprise Edition (DB EE) and Application Server Enterprise Edition (AS EE) licenses. Full licenses for DB EE and AS EE are required to run EBS with customizations.
Oracle Compute Cloud Service follows the Bring Your Own License (BYOL) licensing model. This means that if you choose to run EBS on Compute only (as seen in the left-hand and middle figures above), you can use your existing EBS, Database and Application Server licenses.
If you choose to run your EBS database on DBCS or on Exadata CS (as shown in the right-hand figure above), you subscribe to the database service separately. On-premises database licenses can be exchanged for DBCS and Exadata CS licenses, using the BYOL to PaaS offering as described in this FAQ: Oracle Bring Your Own License (BYOL).
[Blog article update on March 25, 2021: Added the BYOL to PaaS offering: "On-premises database licenses can be exchanged for DBCS and Exadata CS licenses, using BYOL to PaaS offering as described in this FAQ: Oracle Bring Your Own License (BYOL)"]
[Blog article update on August 25, 2020: Removed no longer applicable statement "When the EBS database runs on DBCS, EBS today requires either the DBCS Enterprise Edition - High Performance option or DBCS Enterprise Edition - Extreme Performance option." The table below has been updated accordingly.]
The following table summarizes licensing information for the three main categories of EBS components (EBS, FMW and Database), based on the following available deployment options: on-premises, IaaS only, IaaS + DBCS, or IaaS + ExaCS. It also distinguishes between a lift and shift migration, and a new cloud implementation.
| EBS Licensing | FMW Licensing | Database Licensing | |
| On-Premises | |||
|
Purchase licenses for EBS products used in production. Licenses not required for non-production environments. | FMW runtime licenses included with EBS licenses. Purchase full use licenses if customized mid-tier components (Forms, Reports, Java). | Database runtime licenses included with EBS licenses. Purchase full use licenses if customizing database (code, schema, tables, etc). |
| Oracle Cloud (Lift and Shift Migration) | |||
|
EBS licenses transferable from on-premises. Licenses not required for non-production environments. |
FMW licenses transferable from on-premises. | Database licenses transferable from on-premises. |
|
Subscribe to DBCS EE-GP, EE-HP or DBCS EE-EP. | ||
|
Subscribe to Exadata CS. | ||
| Oracle Cloud (New Implementation) | |||
|
Purchase licenses for EBS products used in production. Licenses not required for non-production environments. | FMW runtime licenses included with EBS licenses. Purchase full use licenses if customizing application tier components (Forms, Reports, Java). | Database runtime licenses included with EBS licenses. Purchase full use licenses if customizing database (code, schema, tables, etc). |
|
Subscribe to DB EE-GP, DB EE-HP or DB EE-EP. | ||
|
Subscribe to Exadata CS. | ||
References
- Oracle Cloud Infrastructure as a Service (IaaS)
- Oracle Database Cloud Services
- Oracle E-Business Suite on Oracle Cloud Landing Page
A customer is asking whether they have "RAC licenses for EBS application" or not...
Please advise how or what to check and confirm that customer has RAC licenses for EBS or not ?
Thank you and Regards,
Narendra
Technically, the customer can review their license contract document and they should find easily if they licensed RAC or not. Otherwise, the customer should reach out to their Oracle Sales Rep who will in turn reviews the license contract doc.
As EBS doesn't need Non-production license. Can you please confirm of this is applicable to databases and middeware products of EBS NON-PROD instances.
Just to be more precise, We have procured full licenses for Oracle DB EE and Oracle AS EE for our Production EBS instance and we have 3 nonprod instances supporting production. Does this mean, we need to take separate licenses for DBEE and ASEE for all the three nonprod EBS Databases and middleware.
Thank you.
Oracle E-Business Suite is licensed by user per product or module, and EBS licenses are required for production use only (whether in the cloud or on-premises). However, the technology licenses, needed to customize EBS, are required for ALL env, i.e. production and non-production. So yes, you need to take separate licenses for DBEE and ASEE for all the three nonprod EBS Databases and middleware. This has always been the case since the beginning of EBS and it is the same on the Cloud.