--- title: "JD Edwards EnterpriseOne Licensing - Understanding and Auditing for On-Premises and in the Cloud: Live Webinar" description: Don't wait until Oracle asks for an audit to discover a usage overage. Discover innovate tools to aid in your JDE EnterpriseOne licensing analysis. image: https://info.syntax.com/hubfs/Landing%20Page%20Hero%20Header%20Images/Hero_Cloud.jpg --- # JD Edwards EnterpriseOne Licensing: Understanding and Auditing for On-Premises and in the Cloud #### On-Demand Webinar Whether you are remaining on-premises or moving to the cloud, the management of your JD Edwards EnterpriseOne licensing is critical and needs to include processes to track usage. You do not want to wait until the Oracle licensing team asks for an audit to discover a usage overage. Staying within the license limits of your contract is one of the regular health checks you should implement to ensure license compliance. Customers must also be aware of the licensing requirements of the operating systems, middleware, database, and other 3rd party products required to run EnterpriseOne. ##### In this On-Demand webinar, we will provide: - An overview of JD Edwards EnterpriseOne Licensing - The basic “gotchas” of Oracle ERP licensing - An understanding of the Oracle License Audit Process - Review a framework for licensing the supporting operating systems, middleware, database and the EnterpriseOne prerequisites - Learn about innovative tools to aid your EnterpriseOne licensing analysis ##### Speakers: - Colin Dawes:  Chief Security Architect, Syntax - Mike Ward:  CEO, Q Software   ![partner-logos-2o](https://info.syntax.com/hs-fs/hubfs/Email%20Headers%20and%20Footers/partner-logos-2o.png?width=598&name=partner-logos-2o.png)   ### Watch It Now [Legal Notices](https://www.syntax.com/legal-notices/) | [Terms](https://www.syntax.com/terms/) | [Privacy Policy](https://www.syntax.com/privacy-policy/) | [Services Privacy Policy](https://www.syntax.com/services-privacy-policy/) | © Syntax 2022 1.877.968.2948 | [info@syntax.com](mailto:info@syntax.com)