JD Edwards: Licensing analysis for concurrent users

Although this is only one of the many metrics for JD Edwards users, it is worth focusing on Concurrent User licenses when looking at the most commonly seen compliance issues.

Licensing Analysis for Concurrent User Licenses

A Concurrent User “is a Full Use User that, at any one time, executes an application contained in a Licensed Product or accesses JD Edwards business or data objects associated with a particular Licensed Product. A User performing any Licensed Product by using one user profile from one device is one Concurrent User. However, sessions initiated by one user profile on more than one device, or by more than one user profile on the same device, shall be counted as multiple Concurrent Users. A User will be counted as a Concurrent User until the User exits or closes all business or data objects associated with the specific Licensed Products“.

If used correctly, this metric can be advantageous for end-users because they only pay for active usage as opposed to possible (authorized) usage. However, Concurrent User licenses are no longer sold by Oracle. Organizations who are still on this historical metric would need to migrate to one of the new metrics in case they exceed their entitlements. As a result, they would need to watch out for a few caveats to administer Concurrent User licenses properly.

Historically, both JD Edwards World and EnterpriseOne used to have built-in mechanisms to limit the number of Concurrent Users. Technical developments like the introduction of three- tier architectures made it impractical to keep such tools in place and today the JD Edwards applications do not have any technical restrictions in place to limit a number of users or to limit the use to the licensed functionalities only. Administrators who are familiar with older versions of the applications might expect that this limitation is still there. The mismatch between this expectation and today’s reality generates a licensing risk.

Another risk at a more technical level are the so-called “hanging sessions” that reside on a server when users exit the application incorrectly. In the event of an audit, Oracle will look at server sessions to determine concurrency. There is no way to technically determine if there is an actual person behind a session which results in hanging sessions being counted as a concurrent user that need to be licensed. Determining what the truth is in an environment with many hanging session can be very challenging and can lead to costly surprises.

There are end-users who own a mix of Concurrent and other user based licensing metrics such as Named, Moderate or Inquiry Users. Whenever this is the case, it is important to understand that concurrency is analyzed only for individual users explicitly marked as Concurrent. In other words: user accounts tagged as Named, Moderate, and/or Inquiry are excluded when looking at user session variation. Therefore, it is most efficient to allocate Named, Moderate or Inquiry licenses to the most active users, leaving the Concurrent User licenses for users who log in less often.

The key takeaways are: World and EnterpriseOne no longer automatically limit the number of concurrent users; all users should log out of the application correctly to prevent hanging session, and license types need to be allocated wisely and in the most cost-effective way in case you own a mix of user metrics.

In our next article, we will talk about differences between legacy pricing models for JD Edwards. More information can also be found in our latest white paper “JD Edwards – License Compliance Risks.” Our new white paper format is mobile friendly, so you can easily read it on your tablet or mobile phone.

B-lay helps organizations effectively use and manage their software assets with practical solutions and services. We love helping you avoid costs, so contact us for support on your JD Edwards license issues!

This article was published on 21-06-2016