JD Edwards indirect usage

19 jul '16 - : Andrei Agavriloaiei & Gabriel Dragoi - share: LinkedIN Mail
jd-edwards-indirect-usage

For JD Edwards applications indirect usage can occur when a web site/shop/application is connected directly to the underlying database, or when applications and 3rd party systems are specifically designed to interact with JDE at application level. A common example of such a system is dcLink.

The issues we see in this area are caused either by end-users being unaware of the fact that all the individuals should be counted at the front end of the 3rd party systems and that this number determines the required number of licenses, or end-users believe there are exceptions for certain infrastructure configurations.

The data transfer between a 3rd party system and JDE can be done in multiple ways. It can happen in real-time when the front end user of a 3rd party system performs an action in that system and his/her action automatically triggers an update or read action in JDE. It can also happen in batches when data is collected in a buffer queue or flat file and then that buffer is emptied in the target system at a predefined moment. In the world of licensing there is some wording around not licensing front end users in the second scenario. However, this type of wording is not applicable to JD Edwards applications sold under Oracle contracts and it is also not applicable to Oracle Applications in general.

Another source of confusion is the wording from certain legacy metrics. For example, the definition for the legacy Named User metric starts with “Is a User with an assigned ‘user id’ on the Customer System(s)...”. This wording is weaker when it comes to enforcing the multiplexing policy because front end users don’t have user id's in the JD Edwards system. As a result, Oracle usually will not pursue an indirect usage claim for a legacy contract and will try to respect the commitment made between the end-user and PeopleSoft or JD Edwards. However, if the end-user does not respect that commitment by exceeding the license grant, they will have to migrate to an Oracle metric.

To conclude: make sure to license all front end users of connected systems. If an end-user wants to migrate from a legacy contract, there is the option to negotiate a custom definition for Application Users or Custom Suite Users in order to cover specific IT architecture configurations.

In our next article, we will talk about licensing JD Edwards Implementation Partners. 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. 

Download Our Free White Paper: 
JD Edwards - License Compliance Risks

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!

Oracle Database and hardware infrastructure

The required number of licenses for Oracle’s Database programs are (almost) at all times related to the hardware infrastructure on which the software is installed. Incorrect interpretation or understanding of whether the software is deemed to be installed and how the installed software should be licensed in a certain specific hardware infrastructure is by far the number 1 license compliance issue. 

Oracle Database and hardware infrastructure

Download

Fill out this form to download our free whitepaper

Please make sure you've filled out the form correctly.

B-lay will use any of the data provided above in accordance with our privacy policy