JD Edwards EnterpriseOne Licensing Disabling Client Licensing for Various Tools Releases (Prior to 9.1.x)
(Doc ID 2063072.1)
Last updated on FEBRUARY 01, 2019
Applies to:JD Edwards EnterpriseOne Tools - Version 8.97 and Prior to 8.98 [Release 8.97 and Prior to 8.98]
JD Edwards EnterpriseOne Tools - Version SP23 and Prior to SP24 [Release SP23 and Prior to SP24]
Information in this document applies to any platform.
Certain releases of EnterpriseOne, Xe, and ERP 8 will stop working after June 30, 2019 unless preventative measures are taken, as described in this document.
Past releases of the JD Edwards EnterpriseOne and current releases of Xe and ERP 8 required that customer establish licenses before running the product’s client software. The terminology used to describe the JD Edwards EnterpriseOne Development Client includes these alternate terms:
» Development Client
» Web Development Client
» Fat Client
The maximum expiration date of any JD Edwards license for the above client software is June 30, 2019. Past that date, certain releases of EnterpriseOne will stop working. The whitepaper also applies to the Deployment Server.
- Can you implement the solution (change JDE.INI settings and copy over new security files), *before* the SPC expiration date? Yes
- Can you test it by advancing the date past 6/30/2019 to see what is going to happen? Yes
- How do the steps in the white paper stop E1 from using the normal licensing in the E1 fat client and start using DBSEC=ROBIN? If the DBSEC=ROBIN is found, E1 skips the license checks.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document