Oracle JD Edwards prerequisite products and licensing involve:
- System Foundation License: Required for all JD Edwards modules.
- Service Management Foundation: Needed for Service Management and Capital Asset Management modules.
- CRM Foundation: Essential for Case Management.
- Correct Licensing: Ensuring licenses for prerequisites match those for the main modules.
JD Edwards Prerequisite Products and Licensing
Many JD Edwards products require other software as prerequisites, meaning you cannot use a particular module without licensing its foundational components.
Understanding these dependencies is critical for ensuring compliance and avoiding licensing mismatches.
Here’s a detailed breakdown of how JD Edwards prerequisites work and the common challenges organizations face.
What Are Prerequisite Products?
Prerequisite products are foundational software components required to activate or run specific JD Edwards modules. These prerequisites ensure the primary module has the infrastructure and functionality to operate effectively.
Examples of Prerequisites:
- System Foundation
- Required for all JD Edwards modules.
- Serves as the base layer for the entire JD Edwards ecosystem, providing essential tools and capabilities.
- Service Management Foundation
- Mandatory for using:
- Service Management
- Capital Asset Management
- Mandatory for using:
- CRM Foundation
- Required for modules such as:
- Case Management
- Other CRM-related functionalities.
- Required for modules such as:
Common Licensing Challenges
Organizations frequently encounter issues with prerequisite products due to licensing mismatches. Here are the most common scenarios:
- Owning Module Licenses Without Prerequisites
- Organizations may inadvertently license a JD Edwards module (e.g., Service Management) without realizing they must also license the associated prerequisite (e.g., Service Management Foundation).
- Impact: This results in non-compliance, as the module cannot legally or functionally operate without the prerequisite.
- License Quantity Discrepancies
- There may be fewer licenses for the prerequisite product than for the main module.
- For example, an organization might have 100 user licenses for Capital Asset Management but only 50 for Service Management Foundation.
- Incorrect License Migration
- Prerequisites may not be accounted for or migrated correctly during a pricing model transition (e.g., moving from perpetual to subscription licenses).
- Impact: This leads to compliance gaps and potential penalties during an audit.
Key Licensing Principles for JD Edwards Prerequisite Products
To ensure compliance and optimize licensing, organizations must adhere to the following principles:
- System Foundation as a Universal Requirement
- System Foundation is a prerequisite for all JD Edwards modules.
- The number of System Foundation licenses must equal the total number of authorized users across the organization.
- Matching Prerequisite Licenses with Main Modules
- The number of licenses for a prerequisite product must match the licenses for the associated primary module.
- For example, if you have 200 user licenses for Service Management, you must also have 200 licenses for Service Management Foundation.
- Understand Module Dependencies
- Before purchasing or deploying a JD Edwards module, identify all associated prerequisites.
- Review Oracle’s licensing documentation or consult licensing experts to ensure you fully understand the dependencies.
Steps to Address Licensing Issues
If your organization discovers mismatches or gaps in its JD Edwards prerequisite licenses, follow these steps to resolve the issue:
- Audit Existing Licenses
- Conduct a thorough audit of your JD Edwards licenses to identify discrepancies between primary modules and their prerequisites.
- Reconcile License Quantities
- Adjust license quantities to ensure that prerequisites match the main modules.
- Example: If you discover that your System Foundation licenses do not cover the total number of users, acquire additional licenses.
- Update Licensing During Migrations
- When migrating from one pricing model to another, carefully review the prerequisites to ensure all licenses are carried over correctly.
- Engage Licensing Experts
- Consult independent Oracle licensing specialists to verify compliance and optimize your license usage.
Practical Examples of Licensing Dependencies
Scenario 1: Capital Asset Management and Service Management Foundation
- A company licenses 150 users for Capital Asset Management but only owns 100 licenses for Service Management Foundation.
- Solution: To match the primary module’s user count, the organization must purchase an additional 50 licenses for Service Management Foundation.
Scenario 2: System Foundation Across Multiple Modules
- A company uses multiple JD Edwards modules (e.g., Financial Management, Supply Chain Management) with a combined total of 300 users.
- Requirement: The organization must hold 300 System Foundation licenses, prerequisites for all modules.
Scenario 3: Case Management and CRM Foundation
- An organization deploys Case Management for 200 users but doesn’t license CRM Foundation.
- Impact: This results in non-compliance and could lead to penalties during an audit.
Read about JD Edwards Concurrent Licensing.
Providers for Core Tools & Infrastructure
JD Edwards World and EnterpriseOne software programs are built on a foundation of interconnected components, enabling seamless business operations.
While JD Edwards develops some of these components, others—such as database and application servers—must be sourced from third-party providers. This setup requires careful licensing management to ensure compliance and optimize costs.
Key Components of Core Tools & Infrastructure
JD Edwards software relies on several essential components to function effectively:
- JD Edwards-Developed Components
- These include proprietary tools and features to manage business logic, workflows, and system integration.
- Examples:
- Workflow Management Tools
- Custom Reporting Features
- Third-Party Components
- Many critical elements of the platform, such as databases and application servers, are provided by third-party vendors.
- Common third-party components include:
- Database Servers: Oracle Database, IBM DB2.
- Application Servers: Oracle WebLogic, IBM WebSphere.
EnterpriseOne Core Tools and Infrastructure Licensing
To use the JD Edwards components, end-users must license a product called EnterpriseOne Core Tools and Infrastructure.
This licensing bundle is designed to:
- Support Essential Functionality
- The core Tools and Infrastructure license covers the foundational elements for the operation of JD Edwards software.
- Examples of included components:
- Development tools for creating and customizing business processes.
- Middleware for connecting different systems and databases.
- Bridge JD Edwards and Third-Party Components
- The license provides a framework for integrating JD Edwards-specific components with third-party software like databases and application servers.
Licensing Alternatives for Core Tools and Infrastructure
Licensing for Core Tools and Infrastructure is a critical consideration for organizations using JD Edwards EnterpriseOne. These tools can be licensed as standalone modules or as part of technology bundles.
Misunderstanding licensing options can lead to compliance issues and unexpected costs.
Here’s an expert breakdown of the available options and the challenges organizations face:
Understanding the Licensing Options
- Technology Foundation (Blue Stack)
- This licensing model includes Core Tools and Infrastructure alongside IBM components.
- Components typically included are:
- IBM WebSphere Application Server
- IBM DB2 Database
- IBM Collaborative Portal
- Commonly referred to as the “Blue Stack,” this option was historically aligned with the initial development of JD Edwards products, designed to run on IBM infrastructure.
- Oracle Technology Foundation (Red Stack)
- This model includes Core Tools and Infrastructure paired with Oracle technologies.
- Components in the Red Stack typically include:
- Oracle Database Standard Edition
- Oracle Internet Application Server Standard Edition
- Oracle WebLogic Server Standard Edition
- Known as the “Red Stack,” this option has become Oracle’s preferred technology bundle since acquiring JD Edwards.
Evolution of Licensing Practices
- Historical Context
JD Edwards products were originally developed for IBM infrastructure. As a result, EnterpriseOne licenses historically included the Technology Foundation (Blue Stack). - Post-Acquisition Shift
Following Oracle’s acquisition of JD Edwards, the emphasis shifted from IBM-based Technology Foundation licenses to Oracle Technology Foundation licenses. Oracle has since ceased selling the Blue Stack, making the Red Stack the standard offering.
Common Licensing Challenges and Mismatches
Many organizations struggle with mismatches between their license entitlements and the technology stack deployed.
This often occurs due to the following scenarios:
- Migration from IBM to Oracle Infrastructure
- Organizations that originally installed EnterpriseOne with IBM infrastructure and licensed Technology Foundation (Blue Stack) may have later migrated to Oracle infrastructure (Red Stack) without updating their licensing.
- For example, an organization may upgrade its EnterpriseOne installation to leverage Oracle Database but continue using IBM licenses, leading to a compliance gap.
- Mixed Licensing Environments
- Some organizations inadvertently mix Red and Blue Stack licenses, creating a mismatch between their software entitlements and deployed infrastructure.
- This often happens when additional licenses are acquired without aligning them to the updated technology stack.
- Expansion Without Proper Adjustments
- Companies that previously purchased Technology Foundation licenses may need to expand their user base. Since Oracle no longer sells Blue Stack licenses, they must transition to Red Stack licenses, often requiring costly adjustments.
JD Edwards Prerequisite Products and Licensing FAQ
What is the System Foundation License in JD Edwards? The System Foundation License is required for all JD Edwards modules. It acts as the base license upon which other modules depend.
Why do I need the Service Management Foundation? It must use the JD Edwards service Management and Capital Asset Management modules.
What is the CRM Foundation used for? The CRM Foundation is essential for using the Case Management module in JD Edwards.
What happens if I don’t have the correct prerequisite licenses? Without them, your organization may face compliance issues and the associated costs of rectifying these gaps.
How can licensing mismatches occur? Licensing mismatches often happen during migrations from one pricing model to another or when expanding user bases without updating all necessary licenses.
What are JD Edwards’s core tools and infrastructure? Core Tools and Infrastructure provide the essential components and business logic platform for JD Edwards software.
What is the Technology Foundation? It includes Core Tools, Infrastructure, and licenses for IBM components like WebSphere Application Server, DB2, and Collaborative Portal.
What is the Oracle Technology Foundation? It includes Core Tools and Infrastructure and licenses for Oracle components such as Oracle Database Standard Edition, Oracle Internet Application Server Standard Edition, and Oracle WebLogic Server Standard Edition.
Why is it important to distinguish between the Red and Blue Stacks? Understanding the difference between the Red (Oracle) and Blue (IBM) Stacks is crucial to ensuring that your licenses match your infrastructure and avoiding compliance issues.
What should I do if my organization has mismatched licenses? If you discover mismatched licenses, take immediate action to align your licenses with your current infrastructure and usage to avoid non-compliance.
Can I still purchase the original Technology Foundation licenses? No, Oracle no longer sells the original Technology Foundation programs. Only Core Tools and Infrastructure or Oracle Technology Foundation licenses are available now.
How can I ensure I have the correct number of licenses? Ensure that the number of System Foundation and Core Tools and Infrastructure licenses matches the total number of authorized users and that prerequisite product licenses match the main module licenses.
What are some common licensing issues in JD Edwards? Common issues include owning licenses for specific modules without the necessary prerequisites or having fewer licenses for prerequisites than for the main modules.
How can I resolve incorrect license combinations? Review your current installations and licensing agreements and adjust them to ensure all necessary prerequisites and main module licenses are correctly matched.
