JD Edwards

Oracle JD Edwards Concurrent Licensing

Licensing Analysis for Concurrent Users: Ensuring Compliance with JD Edwards

As companies increasingly rely on enterprise software solutions, the importance of software licensing compliance has grown exponentially.

JD Edwards is no exception, and organizations need to adhere to its licensing policies to avoid costly legal disputes and penalties.

While there are various licensing metrics for JD Edwards users, Concurrent User licenses are the most likely to report compliance issues.

In this article, we’ll explore the significance of Concurrent User licensing, the risks involved, and the steps organizations can take to ensure compliance with JD Edwards.

What Are JD Edwards Concurrent User Licenses?

A Concurrent User license is a full-use user that executes an application in a licensed product or accesses JD Edwards business or data objects associated with a specific licensed product.

In simple terms, a Concurrent User can access JD Edwards at any given time. When using a licensed product on a single device, a user profile is counted as one Concurrent User.

However, users who initiate sessions using more than one device or user profile will count as multiple Concurrent Users.

What Are the Advantages of Concurrent User Licenses with JD Edwards Products?

Concurrent User licensing has several advantages for end-users. With Concurrent User licenses, organizations only pay for active users instead of possible authorized usage.

This provides cost savings for companies with a large workforce or many users who do not use JD Edwards consistently.

These Are the Caveats to Concurrent JD Edwards User Licenses

Oracle no longer sells Concurrent User licenses. Organizations still using this historical metric must migrate to one of the new metrics if they exceed their entitlements.

Another caveat is the absence of technical restrictions to limit the number of Concurrent Users.

In older versions of JD Edwards, there is a limitation to the number of Concurrent Users. However, with the introduction of three-tier architectures, keeping these mechanisms in place is no longer practical.

This mismatch between expectations and reality generates risks for companies using Concurrent User licenses.

Administrators familiar with older versions of the application may still expect these limitations to exist, which could lead to non-compliance with licensing policies.

Hanging sessions, which remain on a server when users exit an application incorrectly, can also be a technical risk.

Oracle determines concurrency by looking at server sessions. This can be challenging, as it counts hanging sessions as concurrent users, even if they are not actual users.

Managing Mixed Licensing Metrics with JD Edwards Products

Where end-users own a mix of Concurrent and other user-based licensing metrics such as Named, Moderate, or Inquiry Users, it is vital to allocate licenses wisely and cost-effectively.

Allocating Named, Moderate, or Inquiry licenses to the most active users and leaving Concurrent User licenses for users who log in less often is the most efficient way to ensure compliance.

Ensuring compliance with JD Edwards licensing policies can be complex, but organizations can mitigate the risks by understanding Concurrent User licenses’ significance, advantages, and caveats.

Organizations must allocate licenses wisely and cost-effectively, adhere to proper exit procedures, and be aware of potential risks such as hanging sessions.

Companies can avoid costly surprises and ensure compliance with JD Edwards licensing policies by taking these steps.


  • Fredrik Filipsson

    Fredrik Filipsson possesses 20 years of experience in Oracle license management. Having worked at Oracle for 9 years, he gained an additional 11 years of expertise in Oracle license consulting projects. Fredrik has provided assistance to over 150 organizations worldwide, ranging in size and tackling various Oracle licensing challenges, including Licensing Assessments, Oracle audits, Oracle ULAs, and more.