Licensing PeopleSoft, JD Edwards, Siebel, and Other Oracle Apps on AWS (Step-by-Step Guide)

Licensing PeopleSoft, JD Edwards, Siebel, and Other Oracle Apps on AWS

Oracle enterprise applications like PeopleSoft, JD Edwards EnterpriseOne, Siebel CRM, and other industry apps (e.g., Hyperion/EPM, Retail) can all run effectively on AWS. Each app has similar licensing principles: typically, licenses for the applications include restricted-use Oracle Database and middleware licenses specifically for running the application itself.

This guide clearly explains the licensing rules for each major Oracle application on AWS, including practical examples and conditions where additional licenses might be required.

Read Oracle on AWS Licensing FAQs 3 of 4.

1. PeopleSoft Licensing on AWS

Licensing Model:

• Typically licensed per module/user (e.g., HR, Financials, Campus Solutions).
• Oracle often includes restricted-use Oracle Database Enterprise Edition licenses specifically for hosting the PeopleSoft schema.
• Oracle Middleware (WebLogic or Tuxedo) licenses may also be included (for PeopleSoft Internet Architecture – PIA).

When No Additional Licenses Are Needed:

• Running standard PeopleSoft modules on AWS.
• Oracle DB and WebLogic are used only for PeopleSoft data and applications.
• Minor standard customizations (reports, workflows, standard tools).

When Additional Licenses Are Required:

• If the database is used beyond PeopleSoft schemas (custom non-PeopleSoft apps).
• Extensive schema modifications beyond Oracle-approved PeopleSoft guidelines.

Practical Example

• AWS EC2 running PeopleSoft Financials with Oracle DB housing only PeopleSoft data:
  • No additional DB licenses are required (including restricted-use).
• Adding non-PeopleSoft custom apps or schemas on the same DB:
  • Additional full Oracle DB EE licenses are required.

2. JD Edwards EnterpriseOne Licensing on AWS

Licensing Model:

• Typically licensed by named user or concurrent user.
• May use Oracle Database or non-Oracle databases (SQL Server, IBM DB2).

Oracle DB Licensing (JDE on AWS):

• Oracle historically provided restricted-use DB licenses specifically for JD Edwards use:
  • Verify that your contract includes restricted-use Oracle DB licenses.
  • There are no additional DB licenses if the database only hosts JDE data.
• If using a non-Oracle database (e.g., SQL Server), Oracle DB licensing is irrelevant.

Middleware Licensing

• JD Edwards middleware (Enterprise Server, WebLogic for web tier) included for standard JDE usage.
• Additional middleware licenses are only required if hosting non-JDE apps.

Practical Example

• AWS EC2 hosting JD Edwards EnterpriseOne database (Oracle DB) and Enterprise Server (WebLogic):
  • If they are used only for JD Edwards data/apps, no additional Oracle DB/WebLogic licenses are needed.

Read Oracle Database Licensing for Oracle E-Business Suite on AWS.

3. Siebel CRM Licensing on AWS

Licensing Model:

• Typically licensed per named user, concurrent user, or CPU-based.
• Oracle often includes restricted-use Oracle Database licenses for the Siebel repository.

Oracle DB and Middleware Licensing Clearly Explained:

• No additional DB licenses are needed for Siebel-only database instances.
• Middleware (such as WebLogic or Siebel’s proprietary middleware) included for Siebel usage.
• Additional licenses are required if DB or middleware is used beyond Siebel-specific usage.

Practical Example Clearly Explained:

• AWS EC2 hosting Siebel CRM and Oracle DB (Siebel schemas only):
  • No additional Oracle licenses are required.
• Running custom apps on the same DB requires additional licenses.

Read Oracle Java SE Licensing on AWS.

4. Hyperion/EPM and Retail Application Licensing on AWS

Licensing Model:

• Varies by app—usually named users, processors, or business metrics.
• Typically includes restricted-use Oracle DB and middleware for application-specific usage.

DB and Middleware Licensing Conditions

• If Oracle DB/WebLogic hosts only Hyperion/EPM/Retail data/apps, no extra licenses are required.
• Additional licenses are required for DB/middleware if extended beyond the standard application scope.

Clear Practical Example:

• Hyperion Planning using Oracle Database on AWS (restricted-use included license):
  • There is no additional DB license if it is only used by Hyperion Planning.
• Adding non-Hyperion schema/app requires separate full DB licenses.

5. Support and Certification

Oracle explicitly supports running PeopleSoft, JD Edwards, Siebel, and other enterprise apps on AWS infrastructure:

• Documented support policies are available from Oracle.
• Ensure AWS deployments use certified OS and Oracle software versions (Oracle Linux, RHEL, certified DB, and middleware).

Practical Example:

• PeopleSoft Financials supported on AWS if using certified combinations:
  • Oracle Linux or RHEL OS, Oracle DB 19c, WebLogic Server 12.2.

6. Database Options Licensing

• Included DB licenses typically cover basic DB functionality only.
• Additional DB options (like RAC and Partitioning) require separate licenses:
  • RAC for high availability is not included; a separate license is needed.
  • Partitioning tables clearly for performance requires a separate Partitioning license.

Clear Example:

• Deploying RAC for PeopleSoft DB on AWS requires separate RAC licenses.

Summarized Practical Scenarios for Major Oracle Apps on AWS

Summarized Licensing Checklist for Oracle Apps on AWS

✅ Use included restricted-use Oracle DB/middleware licenses (application-specific usage only).
✅ Confirm restricted-use license terms in your Oracle contracts.
✅ adhere to Oracle-approved customization boundaries (or license separately).
✅ Use certified OS/DB/App versions for Oracle support compliance.
❌ No custom/non-app schemas on the same DB without clearly separate licenses.
✅ License additional DB options separately (RAC, Partitioning, etc.) if needed.

Common Misunderstandings

• Misconception: “AWS migration requires new Oracle DB licenses for these apps.”
  Clarification: Included restricted-use DB licenses cover standard app use—no additional licenses unless extended use.
• Misconception: “Minor customizations require separate licenses.”
  Clarification: Oracle permits minor customizations; only extensive schema changes trigger additional licenses.
• Misconception: “Oracle doesn’t support these apps on AWS.”
  Clarification: Oracle supports PeopleSoft, JD Edwards, Siebel, etc., on AWS with clearly documented certified configurations.

Conclusion: Oracle Enterprise Applications Licensing on AWS

Oracle enterprise applications—PeopleSoft, JD Edwards, Siebel, Hyperion/EPM, Retail, and others—can clearly run fully supported on AWS. Oracle typically includes restricted-use Oracle Database and middleware licenses specifically for these applications, requiring no additional DB/middleware licenses if used exclusively for standard application purposes.

Clearly understand and adhere to Oracle’s defined usage boundaries to avoid extra licensing. Confirm the exact terms in your Oracle contracts to ensure compliance and optimized license management on AWS.

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