Note that the Java products supplied with the IBM product can only be used for the purpose of using the IBM product and should not be used for other program or application development. There is no requirement to contact Oracle for licensing or support of Java products in these cases. IBM has a comprehensive agreement with Oracle that gives IBM rights to bundle Java technology with IBM products and Oracle’s commercial pricing for their Java products will have no effect on the IBM customer using Java products under the IBM product license. IBM customers have a continued right to use these Java technology components at no additional cost under the terms of the IBM product license. By installing copying, downloading, accessing or otherwise using this software package, the recipient agrees to be bound by such license terms with regard to such third party software. Such third party software is supplied under such specific license terms and isnot subject to the terms and conditions of license hereunder. This software package may also include third party software as expressly specified in the software package subject tospecific license terms from such third parties. Unless ST can confirm (like IBM below) their customers are covered using CubeProgrammer, the IDE among others, it seems each desktop now needs a $2.50 monthly license. The MP1 incudes Linux, is there a license impact to release products with ST provided boot, kernel and system images to the market ? Personally, until now managed to keep the Oracle JRE off any of the systems until CubeProgrammer required it to develop for the MP1. The question has been posted in several topics lately. Call one of our licensing attorneys for a fee consultation.Could ST please help explain their plans or approach how their customer need to deal with the recent Oracle license requirements now that the JRE not free since ? IDE and CubeProgrammer require the JRE to develop products and bring them to the market and OpenJDK is not an option. Scott & Scott can help you evaluate your Oracle license compliance quickly and discreetly. Because Oracle often increases its audit activities after a license change, it is a good idea to make sure that your organization is compliant with both the Java and non-Java Oracle environments. A company that must buy Java licenses for the first time will have no choice but to use the new licensing model.Ĭompanies can examine their use cases to determine if there is any way to proceed with Java as a bundled product or find an alternative solution. If a company is already licensing Java on the old license metrics, Oracle appears to be willing to allow those licenses to be renewed, but offers no guidance as to what will happen if that company needs to increase its license footprint. More importantly, for companies in the business of consulting, the same group of employees may need duplicative Java licenses for each company for whom it consults, resulting in a windfall to Oracle. Please read that again because it is significant. Initially, it will be incredibly difficult to get an accurate count of another company’s employees for the entirety of the subscription period. It now reads, Customers of the legacy Java SE Subscription may, to the extent permitted in their existing order, renew their legacy Java Subscription, subject to confirmation that current usage is reflective of license counts in such existing order. So any company that wants to use commercial features of Oracle’s Java product must not only calculate all of the employees in its own business, as well as all of the employees of its agents, outsourcers, contractors, or consultants. Oracle defines employee for Java licensing purposes as all of the employees of the organization, regardless of employment status, plus all of the full-time, part-time, and temporary employees of agents, outsourcers, contractors, or consultants that support the business. All organizations using a licensable version of Java must pay between $5.25 – 15.00 per employee for Java licenses. Oracle’s new model gives essentially no consideration to the size of the Java footprint in an organization, and it also exponentially increases the cost affiliated with use of Java in small and large organizations alike. On January 23, 2023, Oracle changed its Java licensing model from processors/named user plus to licensing based on number of employees. Oracle’s latest licensing change for Java is certain to create even more confusion on an already problematic licensing model and give even more ammunition for the Oracle sales and auditing teams to attack Oracle customers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |